Deep Drive private beta ยท Updated 11 October 2026
Privacy & access
This notice describes the Deep Drive memory beta. Other Alongkind services, including companion chat and the username receipt beta, have different data flows.
The beta's client access rules restrict stored memories to their owning approved account. Firebase administrators and service accounts with sufficient permissions may access stored data. This beta does not provide end-to-end encryption that excludes those administrators.
What you choose to store
After you review and confirm both consent choices, the beta uploads your original image and a separate record containing its title, reflection, chosen date, original filename, file type and size, account identifier, storage location, consent version and upload time. Editing changes the title, reflection or date and records an update time; it does not change the original image.
The original image can contain embedded information from your camera, such as location metadata. The beta does not strip that information before uploading.
Sign-in and service providers
The current beta accepts verified @alongkind.com accounts through Google sign-in. It uses Google's Firebase Authentication, Cloud Firestore and Cloud Storage for account access, memory records and image storage. Firebase App Check uses reCAPTCHA Enterprise for application checks. Google receives the data needed to operate these services.
The browser keeps Firebase sign-in state locally so your session can continue. Signing out ends access in that browser; use Sign out on a shared device.
AI analysis and sharing
The memory upload, edit and view flow does not send your image or reflection to an AI model for analysis. It does not automatically publish your memories, share them with another account or transfer them to Legacy. Choosing a file creates a local preview; uploading starts only after your confirmation.
Who can access a memory
Through the beta's client interface, an approved account can read, edit or delete its own memory records and read or delete its own image files. Another client's account is not granted that access. The viewer fetches an authenticated image rather than displaying a public download link.
Privileged infrastructure access is a separate boundary: client access rules do not prevent authorised Firebase administrators or sufficiently privileged service accounts from accessing the underlying data. An independently audited operator-access policy has not been demonstrated for this beta.
Keeping and deleting memories
The current memory flow does not include automatic expiry. You can use Delete to request removal of the stored image and its record. Those are separate operations: if deletion reports an error, do not assume both have been removed; retry or contact Alongkind.
This beta does not give a verified deadline for removal from provider backups or recovery systems. Contact Alongkind if you need confirmation of deletion beyond the active image and record.
Questions or requests
For access, correction, retention or deletion questions, contact Alongkind at bendyson@alongkind.com. Do not send passwords, sign-in tokens or private images by email to explain a problem.