Privacy Policy
Effective September 27, 2026 · TasLogic
Introduction
This Privacy Policy describes how TasLogic ("we," "us," or "our") collects, uses, and shares information when you use MetroASAP, our multi-tenant municipal software platform. It applies to municipal staff, contractor and partner users, portal account holders, visitors who use public features (including anonymous service requests and the public AI assistant), and other people who receive emails or notifications sent through the platform (including employees, business contacts, customers, and similar recipients).
Each municipality that uses MetroASAP remains responsible for its own public records, citizen notices, and municipal privacy obligations. This policy explains how the platform operator handles information in connection with the service.
Information we collect
We may collect:
• Account and profile information — name, email, phone, role, department, and credentials you provide when registering or signing in.
• Operational data — work orders, permits, inspections, correspondence, FOIA requests, payments, and other records you enter or upload while using the platform.
• UX and preference settings — display, accessibility, navigation, and experience choices stored with your account.
• Communications — support requests, release notes acknowledgements, notification delivery metadata, and email delivery and engagement signals reported by our communication providers (such as delivery, bounce, complaint, open, and click events, related timestamps, and message identifiers).
• Technical data — IP address, browser and device type, session identifiers, authentication events, push notification tokens, and security logs used to operate and protect the service.
• Device permissions (mobile app) — when you grant them: camera and photos for field documentation or barcode scanning; microphone for voice notes or dictation; approximate or precise location when in use for work orders, maps, and time clock; biometrics to unlock a saved sign-in on your device.
• Public submissions — information you provide through anonymous public forms, service requests, surveys, or the public AI assistant (including contact details if you choose to provide them).
• Parent-managed program data — when a parks or recreation parent/guardian portal account is used, information about household members or youth participants that the parent or guardian enters (such as names and dates of birth for program eligibility). That information is provided by the adult account holder, not collected directly from children for marketing.
How we use information
We use collected information to:
• Provide, maintain, and secure the platform.
• Authenticate users and enforce role-based access controls.
• Deliver notifications (email, SMS, push, or in-app) and confirm delivery, measure communication effectiveness, maintain records of required notices and acknowledgements, troubleshoot delivery problems, and provide administrators with communication status and engagement information.
• Diagnose errors, prevent abuse and fraud, and investigate security incidents.
• Improve reliability, performance, product features, and communication services.
• Provide customer support and comply with legal obligations.
We do not sell personal information, including communication tracking information. We do not use communication tracking information for unrelated third-party behavioral advertising. Municipal records entered into the platform may be subject to applicable public records laws; those disclosures are governed by the municipality, not by this policy alone.
Email and communication tracking
When we send emails through the platform, we or our email service providers may use technologies such as tracking pixels (also called web pixels), unique links, message identifiers, and similar technologies. These technologies may allow us or our providers to determine, where reported:
• Whether a message was successfully delivered, bounced, or associated with a complaint.
• Whether an email was opened and the date and time of a reported open.
• Whether a link within a message was clicked and the date and time of a reported click.
• Message identifiers used to correlate delivery and engagement events with a particular communication.
• Whether required platform communications, documents, notices, or acknowledgements were viewed or completed in the product.
• Basic technical information associated with the interaction when made available by the communication provider (such as IP address, device type, browser type, or similar diagnostic information).
We use this information for legitimate operational purposes, including confirming delivery of communications; measuring communication effectiveness and engagement; maintaining records of required notices and acknowledgements; troubleshooting delivery problems; security and fraud prevention; communication engagement, delivery performance, and system analytics; improving our communication services; and providing municipal administrators with communication status and engagement information.
Open and click reports are not guaranteed proof that a person personally viewed or read a message. Email-client privacy features, image caching, security scanners, automated systems, and similar technologies may affect open and click reporting. Tracking information may be incomplete, delayed, or imprecise and should not be treated as conclusive evidence of human review.
These email tracking technologies are not enabled for every communication path. For example, messages sent only through certain SMTP routes may not include open or click tracking, and SMS and push notifications are not open- or click-tracked in the same way as email. Additional consent or disclosures may apply when sensitive personal information is involved.
Artificial intelligence
MetroASAP includes optional AI-assisted features that help users draft correspondence, analyze documents, route requests, build reports, caption field photos, transcribe voice input, and answer questions through chat. AI features are suggestions only — important decisions should be verified by qualified staff.
How AI works on the platform:
• Each municipality configures its own AI provider and encrypted API credentials. When AI is enabled, content you submit may be transmitted over HTTPS to that municipality's chosen large-language-model provider.
• Supported provider families include OpenAI, Anthropic, Google Gemini, xAI Grok, and Azure OpenAI-compatible endpoints. The municipality selects the provider; we transmit prompts on the municipality's behalf.
• Categories of data that may be sent to an AI provider include: chat messages; operational records visible to your login (such as work orders, properties, and contact hints); uploaded documents (letters, forms, FOIA PDFs, import samples); voice audio and transcripts for dictation (processed with Deepgram using a platform API key, then parsed server-side); and images attached to inspections or chat.
• Public AI chat — anonymous visitors may use a public assistant widget. Conversation history is kept in the browser session (not stored server-side as a chat thread). Requests are rate-limited by IP address. If you use guided issue intake, contact information you provide may be used to create a service request.
• Knowledge retrieval — the platform may index city knowledge snippets, crawled public web pages, and help articles to improve answers. Text may be sent to embedding services using the municipality's configured provider.
• Retention — authenticated chat threads may be stored in the platform database. Municipal administrators can configure prompt retention (default 30 days) and usage telemetry (tokens and estimated cost, not full prompt archives in usage tables).
• Controls — municipalities can display required disclaimers, block sensitive topics, enable output PII redaction, disable the assistant, and require user confirmation before AI-suggested changes are applied.
Work-order Dictate on the MetroASAP phone app uses your device’s built-in voice-to-text (the same engine as the keyboard microphone). On desktop browsers without that API, Dictate may record audio and use Deepgram speech-to-text (platform-configured API key). Optional AI parsing may then suggest work-order fields from the transcript.
Subprocessors and hosting
We use cloud infrastructure and service providers to operate the platform, including Microsoft Azure for hosting and data storage. Email, SMS, push notification, payment, mapping, analytics, security, and other integrations may process data on our behalf when necessary to provide those services, including delivery and engagement signals for electronic communications. Processing may also vary according to each municipality's configuration.
When AI is enabled, the municipality's selected AI provider acts as a subprocessor for prompts and related content transmitted for inference. Municipal administrators should maintain an up-to-date subprocessor list for their organization.
Data retention and security
We retain platform logs and account data for as long as needed to provide the service, meet contractual obligations, and comply with law. Municipal records follow each city's approved retention schedule and legal holds.
We use encryption in transit, role-based access controls, tenant isolation by municipality, and industry-standard security practices. No method of transmission or storage is completely secure; report suspected incidents to our security contact.
Your choices
You may update profile and experience settings in your account. You can opt out of proactive AI tips in experience settings where available. SMS opt-in and opt-out follow the consent flow presented at sign-up.
Depending on where you live, you may have privacy rights under applicable state or federal law regarding the collection or processing of your personal information (for example rights to access, correct, or delete certain information, or to opt out of certain processing). Where required by applicable law, you may exercise opt-out rights and we will respond to applicable requests and recognized privacy preference signals (such as Global Privacy Control) as those laws require for our processing. Contact [email protected] or your municipal administrator to exercise applicable rights. We do not treat ordinary email delivery, open, or click tracking used for the operational purposes described in this policy as requiring separate affirmative consent in every case, except where applicable law specifically requires it. Additional consent or disclosures may apply when sensitive personal information is involved.
Delete your account — If you created or use a sign-in for MetroASAP, you can delete your account in the app or website: open Account settings (/account/settings), open the Security tab (staff) or scroll to Delete account (portal), confirm with your password (or type DELETE if you use city SSO without a password). This deactivates your login and removes optional profile details such as phone numbers and profile photo. Municipal operational records (for example work orders and payments) are retained by your city according to applicable retention schedules and public records laws. You can also use the same Account settings path on the web at https://app.metroasap.com/account/settings.
For municipal public records requests about information held by your city, contact the municipality directly.
Children's privacy
The platform is intended for municipal operations and authorized adult users (staff, contractors, and portal account holders). It is not directed to children under 13, and we do not knowingly collect personal information directly from children for marketing or from the App Store / Play Store listing audience.
Parks and recreation or similar programs may allow a parent or guardian to enter information about youth participants for registration and eligibility. That child-related information is provided by the parent or guardian account holder and is processed to deliver municipal program services.
Changes and contact
We may update this policy from time to time. The effective date at the top of this page will change when we do. Material changes may be communicated through the platform or release notes.
Privacy questions: [email protected]
Product support: [email protected] or https://app.metroasap.com/support
You may also contact your municipal administrator.