Privacy Policy

Effective October 19, 2026. This policy describes the Archives mobile app and our website at sharearchives.com. Contact the Archives team at team@sharearchives.com about your information.

Information we use

When you sign in with Apple or Google, we receive a provider identifier and the name and email you choose to share, including an Apple relay address. We store your chosen profile name and username, account identifiers, friendships, blocks, invitations, and account settings.

We store photos you choose to upload, their captions and dates, conversation messages, voice recordings, votes, reports, and saved or hidden memory references and albums. Other participants can see content according to the audience and membership you select. Public posts are submitted for moderation before appearing publicly.

Your device and permissions

Photo-library access supports browsing the photos you permit and finding past memories by capture date. Library suggestions and photo color analysis run on your device. Current direct-Photos app versions browse device photo references without uploading or copying your whole library. Keep in My Archive and supported photo or ZIP imports save optimized encrypted copies on that device. Browsing and these private saves do not upload those photos. You separately choose whether to post a photo or add it to a shared conversation; those actions upload the selected content. Your original photos and exports remain untouched, and memories are not used to train an AI model.

Private device copies are not full-resolution backups or a synced cloud library. Keep your originals and exports; uninstalling Archives removes its local copies. Older app versions uploaded selected private imports to owner-only server storage. Previously saved server copies remain subject to the server export, deletion and backup practices below; updating does not automatically migrate them. Microphone access is used when you record a voice memo. You can change permissions in iPhone or iPad Settings; limited photo access is supported. Declining permission may prevent the related feature from working.

If you enable Device lock, iOS checks Face ID, Touch ID or your device passcode. Archives receives the authentication result and does not receive or store biometric templates. The lock preference is stored securely on that device for your account.

Why we use information

We use it to authenticate you, deliver and synchronize memories and conversations, manage sharing, provide support, prevent abuse, and investigate reports. Service providers process network information such as IP addresses, request times and error logs to operate and protect the service. We do not sell your personal information or use your memories for advertising or AI training.

Guest invitations

A post owner can explicitly create a guest invitation. Anyone receiving or forwarding that link can read the selected post and its permitted conversation, including contributed photos and voice recordings, without an account. Links expire after 30 days or can be turned off by the owner. Account blocking cannot identify anonymous visitors. Already delivered message previews and recipient copies cannot be recalled. New replies show a guest-sharing disclosure before sending; earlier replies without that permission prevent enabling a guest invitation for that conversation. Private archive imports are never included merely because you create an invitation.

On supported app versions, Prepare Messages preview places the selected shared photo and invitation in a protected device container shared only with the Archives Messages extension. The preparation expires after ten minutes and is cleared on sign-out. It does not give the extension your login token or private-library index. You choose the recipient and press Send in Messages. Recipient copies remain outside Archives' control.

Service providers and sharing

Our managed app environment uses Supabase for accounts, database and private file storage. Cloudflare hosts our website and supporting infrastructure. Apple and Google process sign-in under their own privacy policies. Google sign-in software declares collection of account information (including name, email and, where available, phone number), user and device identifiers, general location inferred from network information, and usage data for authentication, fraud prevention and service analytics. Bundled Firebase authentication software declares diagnostic analytics. These provider activities do not mean Archives accesses your GPS location or uploads your address book. We do not use these services to target advertising. Older app builds may still use the previous Archives backend hosted through ChatGPT Sites; updating the app does not automatically move content between environments. Our website waitlist uses Supabase and Resend for registration and email. Optional phone verification in older builds uses Google Firebase; it is not enabled in the current owned production app environment.

Providers process data as needed to operate these services under their applicable terms and safeguards. Data may be processed outside your country, including in the United States. Authorized operators can access information for support, safety and maintenance. We may disclose information when legally required or necessary to address threats to safety. Recipients may save or share content they can view; revoking access cannot recall copies they already made.

Retention and deletion

We keep account data and content while needed to provide the service. You can delete your posts and use Settings → Delete account in the app to request permanent deletion of your account and contributed content. Confirmation through your sign-in provider protects this action. Deletion can require retries during an outage. Contact team@sharearchives.com if you cannot access your account or need help with deletion, access, correction or a copy of your information.

Updated managed app builds include Export your data in Settings. Server exports contain your own published contributions and media, verified private archive copies previously uploaded to the server, profile, relationship references and settings. They do not include photos stored only on your device, other participants' private contributions or restricted safety/provider records. Keep your original device photos and import exports separately. Download results expire after 24 hours and are removed by routine cleanup. Export request records are kept for up to eight days for retries and request limits; encrypted backup retention is described below. Size and daily request limits apply. Copies you save or share remain at the destination you choose. Deleting your account cancels exports and removes their stored results.

Limited safety reports, support records or information required by law may be retained when necessary. Encrypted backups of the owned production app environment are scheduled daily and expire after seven days. A restricted recovery record containing an account identifier and deletion-request date is retained for up to thirty days to prevent restored backups from reactivating deleted accounts. Any recovery must reapply deletion requests before service resumes. Provider logs may have separate retention periods; deletion does not immediately erase every provider log or backup.

Website and children

The website waitlist stores the registration information you submit. Photo-print events use the photo you explicitly submit to provide your requested print. Contact us to request removal. Archives is not intended for children under 13. If you believe a child has provided information, contact us so we can investigate and remove it where appropriate.

Changes and contact

We will update this page when our practices change and provide additional notice for material changes where required. Privacy questions and requests: team@sharearchives.com. Please do not email passwords, verification codes or identity documents unless we arrange a secure verification method.