Legal
Privacy Policy
How InMyCity handles personal data when you browse, sign up, subscribe, or use our API.
Last updated July 1, 2026 · Terms of Use · GDPR & EU rights
Who we are
InMyCity™ is operated by Rumble Built, Inc. (“we,” “us,” or “our”). This Privacy Policy describes how we process personal data when you use our website, applications, and APIs.
Questions about privacy: legal@rumblebuilt.com.
What we collect
- Account data — email address, authentication identifiers, subscription tier, and profile settings you provide at signup or in your dashboard.
- Billing data — subscription status, plan, and trial dates. Payment card details are collected and stored by Stripe; we do not store full card numbers on our servers.
- Product usage — saved places, alerts, agents, API keys, API request metadata (timestamps, endpoints, rate-limit counters), and Copilot or Ask Your City prompts needed to deliver the service.
- Technical data — browser type, device information, IP address, and session cookies required for sign-in and security.
- Support & sales correspondence — messages you send to our team.
Civic incident records displayed in InMyCity come from public agency sources. Those records are not collected from you; we ingest, normalize, and aggregate them under our published methodology. We apply privacy floors (for example, withholding breakdowns when counts fall below five) so small-N aggregates cannot be used to identify individuals.
How we use data
- Provide, secure, and improve the service — including Explore, Story Mode, agents, forecasts, and API delivery.
- Authenticate accounts, enforce tier entitlements, and process subscriptions.
- Respond to support requests and sales inquiries.
- Detect abuse, fraud, and violations of our Acceptable Use policy.
- Comply with legal obligations and enforce our Terms of Use.
We do not sell your personal data.
Legal bases (EEA & UK)
- Contract — processing needed to provide the service you signed up for.
- Legitimate interests — security, product improvement, and fraud prevention, balanced against your rights.
- Legal obligation — records we must retain for tax, accounting, or regulatory purposes.
- Consent — where required for optional communications; you may withdraw consent at any time.
See our GDPR & EU rights page for how to exercise your rights in the European Economic Area and United Kingdom.
Cookies & similar technologies
We use essential cookies and local storage to keep you signed in (via Supabase Auth) and to remember session preferences such as your selected pricing persona. These are required for the service to function. We do not use third-party advertising cookies on the consumer app today.
You can clear cookies in your browser settings; doing so will sign you out and may reset local preferences.
Service providers
- Supabase — authentication, database, and hosting infrastructure.
- Stripe — payment processing and subscription billing.
- OAuth providers — if you choose social sign-in, the provider processes your identity according to its own policy.
Processors act on our instructions and under agreements that require appropriate safeguards for personal data.
Retention
We retain account and billing records for as long as your account is active and for a reasonable period afterward to resolve disputes, enforce agreements, and meet legal obligations. API logs and security records are retained on a rolling basis appropriate for operations and abuse detection. You may request deletion as described on our GDPR page.
Security
We use industry-standard measures including encrypted transport (TLS), access controls, and tier-based API authentication. No method of transmission or storage is completely secure; please use a strong, unique password and protect your API keys.
Children
InMyCity is not directed to children under 16, and we do not knowingly collect personal data from them. Contact us at legal@rumblebuilt.com if you believe a child has provided us personal data.
Changes
We may update this policy from time to time. Material changes will be posted on this page with an updated “Last updated” date. Continued use after changes take effect constitutes acceptance of the revised policy.