Privacy Policy
How TapsMaps processes account, venue, location and business-verification information.
Operator and scope
The operator identity and mailing address are pending configuration. This is a prelaunch draft and does not establish legal compliance.
Submit a privacy request through our Privacy Requests page. A monitored privacy contact must be configured before launch.
Information you provide
We process account names and email addresses, authentication information through Supabase, optional contact/profile fields, business-claim contact information and authority statements, support/legal requests, corrections, community confirmations, business profiles, promotions and content you submit. Business signup currently requests a phone field, but that field is not saved by the signup handler; a phone supplied with a claim is saved with the claim. Favorites are supported by the database when used by an account. Registered users may suggest new venues; owner submissions include private business contact information and an authority acknowledgment. Suggestions require admin review before publication, and venue approval does not grant ownership. Submitter identity and moderation notes are not included in public business fields. Do not submit unnecessary sensitive information. Email-only factual Happy Hour corrections require a one-time expiring verification link and moderation. No account is automatically created. The application uses the email transiently to send verification and stores a keyed email hash for duplicate control; raw email is not saved in the community evidence store. Approved factual changes may appear in Community Updates, while email, hashes, tokens and raw reviewer notes are never included in that public history.
Information processed automatically
Requests necessarily expose network information such as IP address, user-agent/browser/device details and potentially referrer URLs to hosting and infrastructure providers. The app processes requested routes, authentication/security events and database audit records. Providers may keep their own logs under their settings and policies. The app does not currently integrate PostHog, product-analytics event capture, advertising pixels or Stripe. Resend may be configured to deliver requested community-submission verification and venue-submission status emails; local development can use a private outbox. Venue-suggestion analytics, when analytics consent is enabled, store only fixed event names and daily aggregate counts, with no name, address, query, email, account identifier or submission contents in the analytics record. Optional categories remain off until selected; future analytics must use the consent gate and update this notice and inventory before activation.
Necessary cookies support Supabase sign-in and privacy choices. Location/search filters are held in memory or the page URL as described below. Session and local storage used by Mapbox are enabled only after functional consent. We do not put application auth tokens in localStorage.
Location information
Nearby discovery uses the browser geolocation API with reduced accuracy requested; the browser/device can still return precise coordinates. Location is now requested only after you select the location control and give browser permission. Coordinates remain in page memory while browsing and are sent in a POST body to TapsMaps and Supabase to find nearby venues. The nearby endpoint does not write those coordinates to the application database or an application location-history table. Hosting/database providers may process or log requests according to their settings; their retention still requires operational review.
Registered venue suggestion address search also uses Mapbox after functional permission and an explicit search. The selected formatted business address and coordinates are retained for moderation and, after approval, public listing; unselected address receipts expire after 30 minutes and are removed during subsequent search/notification maintenance. This is business address information, not a new browser-location request. If you consent to the interactive map, Mapbox receives network/device information and map viewport or tile requests that may reveal the area being viewed. Optional community confirmation sends coordinates to a server-side distance calculation; the application saves only a distance band, not those coordinates, for that confirmation. Search filter URLs can be shared or appear in browser history. Disable location in browser site permissions and reload to discard page-memory coordinates; use the default Philadelphia search or choose another area instead.
Purposes and legal bases — ATTORNEY / PRIVACY COUNSEL REVIEW REQUIRED
Account authentication, requested business listings, claims and support: performance of a contract or steps requested before entering one, where applicable. Security, anti-fraud controls, audit trails, correcting listings and proportionate moderation: proposed legitimate interests, subject to a documented balancing assessment and local restrictions. Location features and optional analytics/functional/advertising storage: consent where required; browser permission is separate from cookie consent. Requests for legal rights, legally required retention and lawful authorities’ demands: applicable legal obligations. Counsel must validate these bases, sensitive-data conditions and which laws apply; not every basis applies to every activity.
Business-verification documents
Claim documents may contain sensitive personal or business data. Uploads use the private claim-evidence bucket. Existing access rules restrict retrieval to the submitting account and authorized claim administrators; no public document URL is generated. The download endpoint checks authentication and claim scope, disables caching, forces download and records successful access where available. Do not upload unrelated identity, banking or health information; redact unnecessary fields first.
A document-retention period is not approved/configured yet. Uploads are blocked in production until it is configured; automatic cleanup must be scheduled and verified before launch. No promise of a fixed deletion period is made while this setting is missing.
Retention and deletion
Account/profile and favorites data generally remain while the account is active and needed to provide requested features. Account deletion is a verified request workflow rather than an immediate destructive action: administrators must handle profile/favorites, revoke memberships and resolve sole-owner transfers, evaluate submissions for removal or de-identification, and document records retained for security, disputes or legal obligations. Audit/security records are not automatically erased by an account request. Backups and providers may retain copies according to their own reviewed schedules.
Legal request retention: not yet approved/configured. Audit-log, security-log and public-submission retention require approved schedules and provider configuration. No product analytics is currently collected by an app-level analytics SDK. Consent preferences expire after 180 days in this browser; active session-cookie duration is described in Cookies. Community verification tokens default to 24 hours and are removed when used; expired tokens are cleaned during maintenance/submissions. Unverified community submissions default to seven days. Keyed contributor identifiers default to 90 days before removal/redaction; approved factual records and audit history may remain. These defaults are configurable and need operator review. Local development outbox files contain recipient emails and links until expiry/cleanup and are never served publicly. Operational retention settings must be approved and cleanup scheduled; data is not declared deleted until deletion actually succeeds.
Your rights and requests
Depending on applicable law and eligibility, you may request access/knowledge, correction, deletion, a portable copy, restriction, objection to legitimate-interest processing, consent withdrawal, limits on certain sensitive-data uses, or an appeal of a denied request. Use Privacy Requests; for an account-related request, sign in with the matching confirmed email to help verify identity. Unverified requests require proportionate manual verification before disclosure or deletion. We do not expose another person’s records. Authorized-agent requests may need proof of authority. A request receipt is not proof of identity or a promise that all data can lawfully be erased.
Use Privacy Choices to withdraw optional consent immediately in this browser. You may complain to your local data-protection regulator, including an EU supervisory authority or the UK ICO where applicable. Ask for an appeal through the request form or privacy contact if a response is denied. Applicable response deadlines and exceptions must be reviewed and followed by the operator; using these controls does not reduce statutory rights.
California and other U.S. state rights — review required
Potential categories include identifiers (name, email, phone, IP), account and business-claim information, user submissions, internet/network activity, geolocation and potentially sensitive information voluntarily placed in claim documents. Sources include you, your device, businesses, official websites, open/permitted data providers and community contributors. Uses and recipients are described above. Public business facts are not automatically personal information, but sole-proprietor/contact information can be.
The inspected app has no personal-information sales, advertising pixels, cross-context advertising or ad-targeting integration. This is a code finding, not a legal determination about all provider or operator activities. Mapbox/provider processing and any future analytics or advertising require a California sale/share and sensitive-data analysis. Privacy Choices supports opt-out controls and honors Global Privacy Control by forcing advertising off even if previously accepted. A GPC signal does not delete your account or stop necessary authentication. Eligible users can request access, correction, deletion, sensitive-use limits where applicable, non-discrimination and an appeal through Privacy Requests. Retention depends on the categories and schedules described above.
International processing — legal review required
Providers may process information in countries outside your jurisdiction, with different privacy rules. The operator must verify actual hosting regions, recipients, processor agreements and any required transfer assessment or mechanism before global launch. We do not assert use of Standard Contractual Clauses or Data Privacy Framework participation without verification.
Children and age
TapsMaps is not directed to children under 13 and does not knowingly collect their personal information. The proposed account minimum age is 18; final age and alcohol-related restrictions require legal review. An age acknowledgment is not age verification. If you believe a child submitted information, contact us to request investigation and appropriate deletion.
Security, incidents and communications
We use server-side authorization, role-scoped database policies, private verification storage and protected sessions; no system is completely secure. Report suspected compromise through Contact. We will investigate incidents and make notifications where required by applicable law. Account, recovery and claim messages are transactional. Signup does not subscribe you to marketing; no promotional-email subscription or send workflow exists in this release. A future marketing program must use separate lawful signup and unsubscribe controls.
Policy changes and contact
Version and update information appear on this page. Material changes should be notified through the service/account communications and require renewed acknowledgment or consent when appropriate. Cookie consent is versioned separately and invalidates old choices when its schema version changes.
Use our Contact page to submit a legal inquiry. Operator contact details must be finalized before public launch.
Contact / legal inquiries · Exercise privacy rights · Your Privacy Choices