Your presence.
Your information.

Accounts and what you share

MassQee uses account identifiers, sign-in details, profile information and the content you choose to create, such as MassQots, photos, captions, memories, comments and messages, to provide the app. Check-ins and participation records support community features. Account and content services use Supabase.

Content you publish may be visible to other people according to the feature and its access settings. Public MassQot links and share cards can be viewed outside the app. Other people may save or reshare content you make public. Check your photos and location before publishing.

Camera, location and augmented reality

Camera access lets you view and place AR content and take photos. Location and motion information help find nearby MassQots, check arrival and position the AR experience. Some camera and scene processing happens on your device using Apple ARKit or Google ARCore. Turning off camera or location access in your device settings can prevent the related features from working.

MassQee uses Google Cloud Anchors to save and recognize AR locations across devices. To power this session, Google will process sensor data (e.g., camera and location). Learn how Google handles AR data. Google Play Services for AR on Android is governed by the Google Privacy Policy.

When Atlas presence sharing is active, the foreground app sends location and pose updates to MassQee’s backend for the private operator map. This is separate from publishing a photo. Use the app’s presence controls or revoke location permission to stop that feature.

Atlas mapping tests

Development builds can record selected camera frames, measured depth, confidence values and camera poses to study spatial reconstruction. These captures can reveal surroundings, including private rooms or people. The current reconstruction workflow is a controlled development workflow; ordinary app use does not yet run a complete automatic scan-to-map upload service.

The hosted Atlas console is restricted to the founder’s account. It contains selected reconstructed datasets and public geographic source material. Its snapshot date shows when the selected reconstruction data was exported. A background update service and future sharing of reconstructed maps require their own controls before general release.

Website and service providers

The early-access forms prepare an email draft. They do not silently register you or store your form details in browser storage. Your email provider handles delivery when you send the draft. Vercel hosts the website; Supabase provides app account, database and storage services. Their operational records may include network, device and request information used to operate and protect the services. The website does not include audience analytics or advertising trackers.

The account-deletion page uses your existing MassQee email and password to sign in through Supabase. Its sign-in session stays in browser memory, and is separate from the private Atlas console. The private Atlas console uses a secure session cookie for sign-in. This is necessary for its access controls. Infrastructure providers may process data outside the country where you use MassQee; their respective privacy information describes their processing.

Your choices and requests

You can change device permissions, use available content and presence controls, and contact us to request access, correction or deletion of your information. Use the account-deletion page or Profile → Settings → Delete account in the app to review the impact and explicitly confirm deletion. If you cannot sign in, contact support from your associated email address where possible.

A confirmed request stops account changes and presence sharing. A scheduled background process removes owned uploaded media and account data before deleting the sign-in account. This includes owned MassQots and their attached memories, community stories and comments, including other people’s contributions. Independent posts by others and shared geographical places are preserved. Other people’s uploaded files, copies or reshares, and provider backups are not erased by this workflow.

Deletion is not immediate. A request receipt confirms the request was recorded, not that removal has finished. No completion deadline or automatic completion email is promised. Older requests that did not include this scope confirmation need the new confirmation or support review before this automated process can act on them. A minimal completion record retains the request reference, timestamps and impact counts without the account identifier. Provider backup retention follows the provider’s own handling; contact us about a specific concern.

Where applicable, you may object to or request restriction of processing, request a portable copy of your data, withdraw consent for optional processing, or raise a concern with your data-protection authority. Contact us for help exercising these rights.