1. Overview
Enshrine is a mobile application. Mobile apps generally do not use browser cookies the same way websites do. Instead, the App and our service providers use local device storage, authentication tokens, permissions, device identifiers, vendor logs, and similar technologies to operate and secure the Service.
This Cookie Policy explains those technologies, why we use them, and what choices you have.
2. Who We Are
Austin Nelson, doing business as Enshrine, operates the App.
Contact: support@enshrine.cc
Privacy and compliance: compliance@enshrine.cc
3. Local Device Storage
The App uses local device storage such as Android SharedPreferences and, if the App is later available on iOS, iOS NSUserDefaults or equivalent storage. This storage is used for app operation and is not the same as a separately encrypted password vault. Your device operating system may provide its own device-level protections.
Local storage may include:
| Data Stored | Purpose | Typical Duration |
|---|---|---|
| Session and authentication state | Keeps you signed in and supports session restoration | Until sign-out, expiry, account deletion, or app data clear |
| App preferences | Stores theme, notification settings, discovery settings, radius settings, and interface choices | Until changed, app uninstall, or app data clear |
| Permission disclosure flags | Tracks whether required permission disclosures have been shown | Until app uninstall or app data clear |
| Location permission state or feature flags | Supports location-based features and permission UX | Until changed, app uninstall, or app data clear |
| Liveness-cache timestamp | Avoids unnecessary liveness checks for a limited period | Currently about 6 hours per user unless cleared earlier |
| Onboarding drafts | Helps preserve profile setup progress during onboarding | Until onboarding completes, app data is cleared, or the draft is removed |
| Image-safety cache entries | Helps avoid repeatedly rescanning the same displayed image | Until app data clear or cache replacement |
| App activity state | Supports session routing, feature state, and app reliability | Until no longer needed, sign-out, or app data clear |
Clearing local app data may sign you out, reset preferences, remove drafts, and require verification or permissions again.
4. Backend and Vendor Technologies
Enshrine and its providers use backend logs, tokens, and service technologies to operate the Service:
- Supabase: Authentication, database, edge functions, realtime features, API logs, and backend operations.
- AWS: Rekognition Face Liveness, Rekognition face or moderation review, and related verification or safety operations.
- Cloudinary: Image upload, storage, transformation, and delivery.
- Resend: Transactional email for account, support, appeal, safety, and privacy-request communications.
- Cloudflare: Edge workers, webhook handling, security, and TURN connectivity support for WebRTC where configured.
- Google Play: Subscription purchase verification, billing status, and app-store purchase records.
- Future app-store providers: If the App is later offered through another app store, that provider may process purchase and platform data under its own policies.
These providers may create their own server logs, security logs, request records, and operational records under their terms and privacy policies.
5. Location Services
When you grant location permission, the App may use device location to support proximity-based matching, map discovery, distance calculations, and related features.
Location data may be sent to Enshrine servers to operate those features. Enshrine does not use a third-party location SDK for advertising. You can revoke location permission in device settings at any time, but location-based features may stop working or become limited.
6. Advertising and Analytics Technologies
Enshrine does not currently use advertising SDKs or advertising identifiers for targeted advertising.
Enshrine does not currently use:
- Google Analytics or Firebase Analytics.
- Facebook Pixel or Meta SDK.
- Mixpanel, Amplitude, or similar third-party analytics SDKs.
- Third-party video provider SDKs for calls.
- Third-party push-notification SDKs.
If Enshrine later introduces non-essential analytics, advertising SDKs, or advertising identifiers, we will update this Policy and provide required notice and consent or opt-out controls before activating those technologies.
7. Your Choices
Clearing Local Storage
You can clear local app data through your device settings. This may sign you out, reset preferences, delete drafts, remove local caches, and require liveness or permissions again.
Android: Settings > Apps > Enshrine > Storage > Clear Data.
If the App is later available on iOS, deleting and reinstalling the App generally clears local app storage.
Permissions
You can manage App permissions through device settings, including location, camera, microphone, and notifications. Some features require certain permissions.
Advertising Identifiers
Even though Enshrine does not currently use advertising identifiers, you may manage them through your device settings.
Android: Settings > Google > Ads > Delete advertising ID or related ad settings.
If the App is later available on iOS: Settings > Privacy & Security > Tracking.
8. Consent
Local storage used for authentication, security, account operation, app preferences, liveness routing, and core functionality is necessary to operate the Service.
Where law requires separate consent for a feature, such as device permissions, marketing, biometric processing, or non-essential tracking, Enshrine will seek consent through the App or another appropriate method.
9. Updates
We will update this Policy when our use of local storage, SDKs, tracking technologies, or vendors changes materially. Material changes will be communicated through the App or another reasonable method where required.
10. Contact
Austin Nelson, doing business as Enshrine
4010 W Okanogan Ave
Kennewick, WA 99336
General: support@enshrine.cc
Privacy and Compliance: compliance@enshrine.cc