FrontDoor LivingFrontDoor Living · Pilot policies
Privacy policy
Clear directions should not require unnecessary personal information.
Draft for review · Updated September 26, 2026. Business identity, mailing address, service jurisdiction, retention schedule, and production-provider settings must be finalized before commercial launch.
Who operates this service
FrontDoor Living (DBA) operates this pilot. Contact lgonzalez@nexuswatchers.com about privacy, access, correction, export, or deletion. The legal entity behind the DBA and business mailing address must be confirmed before public commercial launch.
What we need
Visitors can search the property map without an account. Apartment searches are handled in the browser and are not included in usage-event payloads. Account holders provide an email for authentication. Personal destination coordinates, labels, and approach notes are collected only when you submit them. Do not include resident names, gate codes, medical information, or other sensitive details in labels or notes.
Location and sharing
We do not request a visitor’s live location. Entrance coordinates describe a destination, not your current location. A shared destination link can be forwarded to anyone; it is not a private access control. Personal destinations are private until you explicitly share them. An entrance-sign link identifies the sign, not the physical position of the person opening it.
How information is used
Account information supports sign-in and permissions. Destination records support arrival guidance and manager review. Verification records identify the reviewer and revision reviewed. These records are not used for advertising, resident profiling, or AI training by this application.
Optional analytics
Optional usage counts require an affirmative choice. We do not put raw apartment queries, visitor GPS, email addresses, or full shared URLs in analytics. Counts describe actions, not unique visitors or proven successful arrivals. We honor Global Privacy Control and Do Not Track by disabling optional analytics. When enabled, daily action totals are stored for up to 90 days and then automatically deleted. Short-lived global counters limit automated submissions; totals are approximate.
Service providers and external links
The production design uses Vercel for hosting and Supabase for authentication and database storage. Infrastructure providers necessarily process requests and may retain security logs, including IP addresses, under their own terms. The existing prototype host has its own infrastructure policies. Our public pages do not embed live Google Maps, advertising pixels, or social feeds. Choosing Google Maps, Apple Maps, or Waze opens that provider and sends the destination coordinate; that provider’s privacy policy then applies.
Retention and your choices
Privacy choices expire after 180 days. Authentication is stored in this browser until sign-out, session revocation, or clearing site data. Sign out on shared devices. Theme and explicitly saved demo records remain until cleared; Privacy settings provides a clearing control. Account and verification retention periods, backup deletion windows, and provider log retention must be finalized before launch. Contact us for an account export or deletion request; identity verification may be necessary and applicable legal obligations may require limited retention.
Security and limitations
The production backend is designed to restrict edits by account and community, preserve review history, and keep secret keys off the client. No system guarantees absolute security. Do not use this pilot to publish confidential access instructions.
Children and changes
This service is not directed to children under 13. If you believe a child submitted personal data, contact us. We will update this notice when processing changes and request a fresh choice before introducing new optional tracking purposes.