Map privacy, consent & security
Spark disclosure version spark-2026-11-06 · Updated November 6, 2026
Recognition should feel good and stay under your control. This map-specific disclosure supplements Sidedoor’s Privacy, Terms, Cookies, Third Party and security incident documents. It describes this feature; it does not replace your legal rights.
Your choices come first
The interactive map loads Google services only after you choose Allow Google services & open map. GPS requires a separate choice and browser permission. Searches are sent to Google only when you type. Each Spark requires a new, unchecked publication approval. No automatic IP-to-location lookup, fixed local shortcuts, background GPS tracking or contributor location pins are used. Reloading clears the tab’s chosen location.
What becomes public
A Spark publishes the business identity and business map position, optional recipient first name, creation time, chosen expiry, and recognition tier. First names are optional: share one only with permission and avoid children’s names, contact information, health, employment or other sensitive details. Do not post a home address or private workplace. Business pages can be indexed by search engines. Search-engine copies may take time to disappear after removal.
What stays private
Contributor account IDs, email addresses, signed visitor tokens, consent records and keyed anti-abuse connection hashes are not included in the public map feed or business pages. GPS coordinates center this tab and can bias Google search; they are not written to a Spark or published. We do not read personal files, computer names or another visitor’s device location. Google and hosting services necessarily receive network/device signals and may keep service logs under their own retention policies. We cannot promise that a network provider keeps no IP logs.
Google services and browser storage
Google Maps, Places, Firebase and reCAPTCHA Enterprise support map rendering, search, optional sign-in and abuse protection. Google receives search text, chosen search bias, IP address and device/security signals as needed for these services. A signed guest session lasts up to 30 days in browser storage so you can manage your anonymous Sparks; optional sign-in uses Firebase’s session storage. Map consent is requested again on reload. No advertising or map analytics are added by this feature.
Expiry and removal
Choose 1, 7 or 14 days. Verified scouts may choose 90 days. A Spark fades during its final 20% of life and is excluded when expired. Someone else’s contribution never extends your choice. “Your sparks” → “Manage your Sparks” → “Remove” withdraws your own Spark; server and edge caches can take up to five minutes to update. Keep the same browser visitor session or signed-in account to prove ownership. If you lose that session, contact Sidedoor for a privacy or removal request. Avoid sending passwords or visitor tokens. Expired records and short-lived security limits are cleaned daily; provider backups/logs follow provider retention. Older lasting Executive Sparks from the first version can still be withdrawn.
How constellations work
The Spark: 1 eligible contributor. The Connection: 2–4. The Glow: 5–14. The Constellation: 15–39. The Golden Moment: 40+. Levels use server-calculated contributor signals for a stable business ID, separate from map zoom, visual clusters and weighted recognition. Repeated active contributions from the same identity count once toward levels. Guest contributions sharing a network connection count conservatively as one signal. These signals are not proof of unique people and can undercount households or shared networks. The bounded feed covers up to 200 recent records; results are lower bounds, not a complete census or a business rating.
Community milestones and honest discovery
A city’s Community Golden Moment requires at least 40 eligible signals across at least three businesses. It stays active until the signal falls below 30 or fewer than three businesses remain, with at least a 24-hour celebration cooldown. Dated milestones retain only business/community counts and achievement dates; they may remain after individual Sparks expire or are removed. “Replay celebration” replays the visual effect for a dated milestone, not a recording of people or their movements. “What’s Glowing” shows businesses at Glow level or higher. Sharing a business sends its public page link only after you choose Share.
Business verification and independence
A Google Place match or many Sparks does not verify a Sidedoor business. A verified anchor appears only after staff approve a link to the business’s public Sidedoor profile and record the checks performed. The card states those checks and links to public profile/reviews. Private workplace reviews, employee lists and company tools are not exposed. Known linked owners cannot Spark their own business. Undeclared relationships and coordinated abuse cannot be eliminated by technical checks; report concerns for review. No business receives a badge merely for paying or collecting recognition.
Security and cost controls
Server-side writes validate business identity, approval version and expiry. App Check/reCAPTCHA, signed visitor sessions, server-assigned account tiers, idempotent submissions, per-identity and connection limits, strict field validation, public-data projection, bounded queries and daily request budgets reduce abuse. One Spark per business per 24 hours and five per scout per hour apply; guests on a shared connection share the business limit. API keys are restricted by service and approved website. HTTPS and browser security headers remain enabled. Google project API limits and CA$25 monthly alerts help monitor costs; alerts do not shut off billing. No protection guarantees a bot-free map or zero charges.
Accessibility and reporting
Responsive controls, keyboard search, text descriptions and reduced-motion support are included. Use your device’s Reduce Motion preference to stop visual animations. You can search a location without GPS and leave the map without approving Google services. For privacy, accessibility, inaccurate business links, abusive recognition or a suspected security incident, use the contact page. Include the public page link and a description, never private account credentials.
