SoulLocket Privacy Policy

1. Scope and operator

This policy applies to the SoulLocket app, project websites and related support channels. “We” means the SoulLocket operating team. Contact for data requests: hotroviethoangdev.lo.ve@gmail.com.

Features may vary by platform, release and configuration. Technical data for sign-in, safety, diagnostics or SDKs may be generated while the app runs; not all data collection waits for you to press an upload button.

2. Data and purposes

Account and access protection

Email, account ID (UID), profile name and photo, sign-in method, authentication sessions, device information and notification tokens are used for sign-in, account recovery, notifications and access management. Third-party sign-in such as Google or Facebook applies only when offered and you choose to use it.

The system may process IP addresses, browser/operating system information, app device identifiers, device authentication status and anti-abuse signals. The app's device-protection signal setting does not remove essential server network, authentication or security logs.

Personal and shared spaces (House)

Names, avatars, member roles, pairing dates, anniversaries, presence and settings are stored for display, synchronization and access control. Choosing the “Couple” interface mode does not itself establish that two accounts are paired.

Your content and attachments

Diaries, personal reflections, photos, videos, messages, reactions, community posts, notes, calendars, letters, audio recordings and utility content are processed to store, display, deliver and synchronize them as the feature requires. Content in the private vault may contain sensitive information; a PIN lock does not mean end-to-end encryption.

Photos/files may be stored in Cloudflare R2, Firebase infrastructure or local storage, depending on the flow and upload time. The app uses access URLs, file references and caches to load content again.

Location, health and activity

If you enable location sharing and grant the relevant permissions, the app processes coordinates, location history and places for maps, check-ins or sharing your location with your House partner. With background location permission, updates may continue while the app is not in the foreground. You can stop sharing in the feature or revoke permission in your operating system settings; this does not automatically delete saved history.

Health/cycle utilities or sleep tracking may process information you enter, screen/activity signals and permitted sleep data from the device's health platform. Sleep status or history may be synchronized to the House. This information is for reference, not a medical conclusion.

Camera, microphone and biometrics

The camera/microphone is used for photos, scanning codes, recordings or available communication features. Biometric authentication is performed by the operating system: SoulLocket receives the authentication result, not the operating system's fingerprint or face templates.

Payments, advertising and measurement

Product information, transaction IDs, verification tokens, VIP entitlements and points history are used to grant/restore benefits and prevent fraud. Sensitive payment details are handled by the relevant payment platform; do not send card details to support.

Google Mobile Ads/AdMob may process advertising identifiers, IP addresses, device information, impressions and interactions. Firebase Analytics may record events/navigation; Crashlytics processes errors, technical traces and attached identifiers for diagnostics. In the new integration, “Essential” disables Analytics/Crashlytics collection and blocks ad loading through the app; “All” does not replace Google UMP or operating system permissions. Change this under Settings → Privacy choices. Older app versions may not include these controls. See the Cookie Policy.

Artificial intelligence (AI)

When you use AI, your requests, conversation context and data you choose to include may pass through SoulLocket servers/Workers to the configured AI service. The code integrates Google Gemini and an OpenAI-compatible API route through an intermediary server; “OpenAI-compatible” does not mean every request is processed directly by OpenAI.

Do not send passwords, one-time codes, card details or other people's private data to AI. Reports of responses may include the question, answer and reason for support review. Do not assume all AI content is processed only on your device.

Support and deletion requests

Account email, name/House ID if provided, request details, IP address and browser information may be recorded to verify account ownership, prevent duplicate requests and provide support. You do not need to provide passwords, PINs or one-time codes by email or through the public form.

3. Who may receive or view data

• Your House partner: can view shared data as allowed by each feature. Pairing grants access to a shared space; it is not merely adding an avatar.
• Viewers of content you share: community posts, public profiles, memory links or cards may be viewed within the feature's sharing scope. Anyone holding a shared link may forward it or save copies; do not publish invitation codes or private links.
• Infrastructure providers: Google/Firebase (authentication, databases, notifications, storage, measurement/diagnostics), Cloudflare (R2, Workers and content delivery), and the sign-in, advertising and payment services you use.
• Maps and external content: Google Maps/map tiles, OpenStreetMap/Nominatim and OSRM may receive IP addresses, place queries or coordinates needed for lookup/routing. External files, fonts, players or embedded pages may connect directly to their providers when loaded.
• AI services: receive data needed for AI requests as described in section 2. The actual provider, processing region and retention conditions depend on the service configuration; you may ask the privacy contact before submitting sensitive information.
• Authorized personnel/competent authorities: as necessary for support, handling violations, system protection or valid requests under applicable law.

SoulLocket does not sell personal data. Processing by service providers to operate the service does not authorize them to use data freely beyond the purposes disclosed.

4. Grounds, choices and processing locations

Data is processed to provide the service you request, carry out your sharing choices, protect safety and meet applicable legal obligations. Processing that requires consent or operating system permissions must be preceded by the relevant notice and choice; reading this policy does not replace all separate consents.

Google, Cloudflare and integrated services may process or store data outside Vietnam. Do not assume all data is stored in Vietnam. You may contact us about recipients, processing locations and the data involved in your request.

5. Retention, deletion and remaining data

Accounts, profiles and content are retained to provide the service during use, until deleted through a feature or a processed request. There is no single automatic deletion deadline for every type of data.

• Friendly Chat conversation memory is designed around a window of approximately 3 days. This is not a retention limit for all AI reports, logs or data held by AI providers; cleanup jobs may run after data expires.
• Media may pass through a trash folder or a separate cleanup queue. Signing out, uninstalling the app or revoking permissions does not delete server data.
• Account deletion and Breakup / House data deletion are different processes. Their timelines and scope are explained on the account and data deletion page.
• Shared content, copies saved by others, device exports and caches may not disappear at the same time as an account. Current automatic deletion does not guarantee removal of all R2 media and every House-related record; specify any remaining personal data you want deleted when contacting support.
• Data retained for legal obligations, fraud handling or disputes must be limited to the necessary purpose and period. Contact support for the data types, reasons and periods applicable to your case; this policy does not authorize indefinite retention.

6. Security and limitations

SoulLocket uses authentication, database access controls, server access checks, device management and feature-specific locks. No system is completely secure; this document does not promise end-to-end encryption for all diaries, chats or photos.

Do not share sign-in sessions, PINs, one-time codes or login QR codes. The app lock protects opening the interface on a device; it does not itself change your House partner's permissions or revoke shared copies.

7. Your rights and requests

Depending on applicable law, you may request information about and access to data, corrections, copies/exports, deletion, restrictions or objections to processing, withdrawal of consent and complaint handling. Some actions are available in the app; send other requests to support or use the account deletion form.

State your email/UID and the requested scope. We need to verify your authority before providing or deleting data; passwords or one-time codes are not required. Withdrawing consent may stop the related feature from working and does not invalidate earlier processing performed on a valid basis.

You may revoke camera, microphone, location, notification and health permissions in your operating system. If support cannot resolve the issue, you may contact competent authorities under applicable law.

8. Children and personal safety

SoulLocket is not designed as a service specifically for young children. Users must meet applicable age, capacity and parental/guardian consent requirements. Do not infer a service age limit from an “18+” label describing prohibited content.

Parents/guardians who discover inappropriate processing of children's data may contact the privacy contact to request review and action. Do not use the app for secret tracking or to pressure someone into sharing their location.

9. Updates and related documents

The update date at the top identifies the document version. Changes to processing purposes or scope require notice and renewed consent where required by law; silence or continued use must not be treated as consent to every new purpose.

Read this with the Terms of Use, Cookie Policy and Account Deletion Guide.