Privacy Policy

1. Controller and contact

The controller responsible for Adoracle is:

No Data Protection Officer has been appointed unless required by law. If that changes, this policy will be updated.

2. Scope and current configuration

This privacy policy explains how Adoracle processes personal data through the Adoracle website, Android beta, related support channels, Owlzi NFC companion flows, photo quests, optional verification, and partner quests.

The authenticated family portal stores family profiles, roles, invitations, Journal metadata, CertifiCute wording, and redemption requests in the Adoracle backend. Photo bytes remain on the capturing device; the portal receives only related dates, members, notes, event types, and other metadata. If paid features, public galleries, notifications, analytics, or advertising are added, this policy must be updated before or when they become active.

3. Privacy principles for Adoracle

• Local-first: quest notes and photos should remain on the user's device unless the user explicitly chooses verification, export, backup, or sharing.
• Minimum location: location should be checked only when needed to start, progress, or complete a quest. Adoracle is not intended to continuously track routes in the background.
• No hidden social upload: sharing should be user-initiated through the device share sheet or a clear partner flow.
• No training use by default: photos uploaded for verification should not be used to train AI models unless the user has separately and explicitly consented.
• Short retention: raw verification photos should be deleted after verification unless a longer retention period is strictly necessary and disclosed.

4. Data categories processed

5. Purposes and legal bases

6. Location data

Adoracle may use location data to determine whether a user is near a quest, landmark, partner location, or route point. The intended MVP does not collect background location and does not store continuous route history.

Users can deny or revoke location permission in their browser or device settings. Some quests may not work without location access. Where possible, Adoracle should use coarse location or on-device checks instead of sending precise coordinates to a server.

Adoracle should not ask users to visit unsafe, restricted, private, or inaccessible locations. Users must still judge their surroundings and comply with local laws, traffic rules, property rights, park rules, museum rules, photography rules, and safety instructions.

7. Photos, camera, and metadata

Adoracle uses the camera or photo picker only when the user chooses a photo-related feature. Photos can reveal personal data, location, habits, bystanders, homes, vehicles, health information, religious/political places, or other sensitive context. Users should avoid photographing strangers, children, private interiors, license plates, documents, screens, or sensitive locations unless they have a lawful reason and consent where required.

Before uploading any photo, users should review whether it contains identifiable persons or sensitive information. Adoracle may remove or reject photos that are illegal, unsafe, abusive, privacy-invasive, fraudulent, or unrelated to the quest.

EXIF metadata may include timestamp, device information, and location coordinates. The privacy-friendly implementation should strip unnecessary metadata before upload or sharing where technically feasible.

8. AI verification

Adoracle may offer optional AI verification to check whether a quest photo appears to satisfy a quest condition, for example whether a requested object, color, landmark, or scene appears in the image.

The intended AI verification design is:

• the user actively chooses to verify or submit a goal photo;
• the image and quest rule are sent to [[AI_VERIFICATION_PROVIDER_OR_NONE]];
• the AI returns a verification result, short explanation, and/or confidence signal;
• the raw image is deleted by Adoracle after verification unless the user asks for support review or a legal/security retention reason applies;
• Adoracle stores only the minimum result needed for quest completion, points, abuse prevention, and troubleshooting;
• uploaded images are not used to train Adoracle or provider models unless the user gives separate explicit consent.

AI verification is probabilistic and can be wrong. A failed verification does not determine legal rights, creditworthiness, employment, access to essential services, or similarly significant matters. Users can retry or contact support for review.

Adoracle must not use AI verification for face recognition, biometric identification, emotion recognition, sensitive-trait inference, or surveillance.

9. Special category data and sensitive places

Adoracle does not intentionally ask for special category data such as health data, biometric identification data, political opinions, religious beliefs, trade-union membership, sexual orientation, or ethnicity. Because location and photos can accidentally reveal sensitive information, users should avoid uploading photos from sensitive places such as hospitals, clinics, schools, shelters, places of worship, protests, private homes, or locations where people may have a strong expectation of privacy.

If Adoracle receives sensitive data unexpectedly, it may delete or restrict the data unless retention is required to handle a safety, abuse, legal, or support issue.

10. Age and minors

Adoracle is intended for users aged 16 or older unless a separate child-safety and parental-consent flow is implemented. Users under 16 should not use the app or create an account without parental/guardian involvement where required by law.

Adoracle is not directed at children and should not be marketed as a toy, children's game, or child-directed social app. Owlzi physical objects are art/ritual companions, not toys, unless separately assessed and marketed under toy-safety rules.

11. Social sharing and partner rewards

Adoracle may allow users to share quest photos or completion messages to third-party services such as social networks or messaging apps. Sharing should be user-initiated. Third-party services process shared content under their own terms and privacy policies.

Partner quests, sponsored quests, affiliate links, reward codes, and paid placements must be clearly labeled. If Adoracle receives commission, payment, free products, free services, or another economic benefit, this will be disclosed near the relevant quest or link.

Adoracle should not upload a user's contacts or scrape social accounts for proof of sharing unless a separate, clear consent and privacy assessment is completed.

12. Cookies and local storage

The static Adoracle landing site is intended not to use analytics cookies, ad pixels, retargeting pixels, or external tracking scripts. The optional account portal uses necessary browser storage for the Supabase session, OAuth PKCE state, a stable browser installation ID, and a pending invitation token. The Android app may use local storage, IndexedDB, Room, and device app storage for settings, synced metadata, and device-local photos.

Local storage on the user's device is not the same as Adoracle receiving the data on its server, but it can still contain personal information. Users can delete local data in the app settings or through browser/device storage controls.

If Adoracle later uses non-essential cookies, web analytics, advertising pixels, or similar tracking technologies, it must request consent before using them and update the cookie information.

13. Processors and recipients

Personal data may be processed by carefully selected service providers where necessary. Replace the placeholders below with your real providers before launch.

Where providers process personal data on Adoracle's behalf, Adoracle should conclude data processing agreements. Where personal data is transferred outside the EEA, Adoracle should rely on an adequacy decision, Standard Contractual Clauses, or another valid transfer mechanism, plus supplementary safeguards where needed.

14. Retention periods

Backups may persist for a limited time after deletion until overwritten under normal backup cycles.

15. User rights

Users have the right to request access, rectification, deletion, restriction, portability, objection, and withdrawal of consent where applicable. To exercise rights, contact [[PRIVACY_EMAIL_OR_SAME_AS_SUPPORT]].

Users also have the right to lodge a complaint with a data protection supervisory authority. In Austria, this is the Datenschutzbehörde, Barichgasse 40-42, 1030 Vienna. Use the official authority website rather than links copied from this template.

When a request concerns local-only data stored solely on the user's device, Adoracle may not be able to access it. In that case, users can delete the data using the in-app deletion function or their browser/device storage settings.

16. Security

Adoracle should use HTTPS, access controls, least-privilege permissions, secure authentication where accounts exist, regular software updates, encrypted transport, secure storage for secrets, and deletion routines for temporary verification files. No internet service can be guaranteed completely secure.

If a personal data breach occurs and is likely to create a risk to users' rights and freedoms, Adoracle will assess notification duties and notify the competent authority and/or affected users where required.

17. Changes to this policy

Adoracle may update this policy when the app changes, providers change, legal requirements change, or new features are introduced. Material changes should be communicated in the app or on the website. The current version date is shown at the top of this page.