MycOracle Privacy Policy

1. Introduction

MycOracle is an oracle-card and journaling app. It does not require an account. This policy explains what the app stores on your device, what it sends off the device, and the controls available to you.

2. Information MycOracle collects

MycOracle stores the app activity needed for its local features, such as selected cards, favorites, draw history, and journal entries. The current Android release does not ask you for your name or email address and does not provide account creation, sign-in, or authentication.

The app does not request access to:

• contacts, precise or approximate location;
• photos, files, the camera, or the microphone;
• health or payment information; or
• advertising identifiers.

The app contains no advertising, in-app purchases, push notifications, crash-reporting SDK, or general-purpose analytics SDK.

3. Information stored locally on the device

MycOracle uses app storage on your device for:

• favorite card identifiers;
• the last-drawn card identifier;
• up to 200 draw-history records containing card identifier, card title, and draw date and time;
• journal records containing an app-generated entry identifier, card identifier, your journal text, creation date and time, and the selected reflection-question index;
• the next reflection-question position for each card;
• a randomly generated, persistent client session identifier;
• pending card-draw and journal-activity event queues described below.

Sound and draw-mode choices are held only while the app is open; the current release does not save those choices as persistent preferences.

4. Card-draw statistics and app-interaction data

The app creates a pending event after a card draw. Each event can contain an event ID, card ID and title, deck ID, single- or three-card draw mode, batch ID, card position, selected fan slot, draw date and time, the persistent client session ID, the device-reported time-zone name, app version, and whether it was the first draw in that app session.

The source code includes a card_draw_events data format intended to count card draws and understand draw mode, card position, selection slot, time zone, and first-draw activity. However, the current production Android build does not contain a Supabase endpoint configuration. It therefore keeps these events in the on-device pending queue and does not transmit them to Supabase.

The persistent client session ID is not a name, email address, Android advertising ID, or hardware device ID, but it can link locally stored activity over time. For that reason, this policy does not describe the event data as anonymous.

5. Journal entries

Your journal text remains exclusively in MycOracle's local app storage in the current Android release. It is not cloud synchronized or uploaded to a server.

When you save an entry, the app separately creates a pending journal-activity event containing an event ID, card ID and title, deck ID, journal date and time, persistent client session ID, time-zone name, and app version. It does not contain your journal text. As with draw events, the current production build keeps that activity event on the device and does not transmit it.

6. How information is used

Locally stored information lets MycOracle show your journal entries, remember favorites and reflection-question progress, and maintain draw history. The pending event formats exist to support aggregate card-draw and journal-activity statistics, but server upload is not active in the current Android release.

7. When information is shared

The current Android release does not send MycOracle app activity or journal text to Quantum Nonsense, Supabase, advertisers, or other third parties. The app has no advertising integrations.

Your app-store provider may process information when you download or update the app under its own terms. That processing is separate from MycOracle's in-app data handling.

8. Third-party service providers

Vercel hosts this privacy-policy webpage. Like a normal web host, Vercel may process your IP address and request information needed to deliver the page and maintain service security. This page does not add analytics, advertising, cookies, or tracking scripts.

Expo and EAS are used to develop and build MycOracle. The current release does not include an Expo analytics service, and the app does not intentionally send runtime app activity to Expo. Supabase upload code exists in the project but, as explained above, Supabase is not active as a data recipient in the current production Android build.

9. Data retention and deletion

Local records remain on your device until they are overwritten by the app or you clear MycOracle's app storage. Draw history is limited to the 200 most recent records. The app does not set an automatic deletion period for journal entries, favorites, identifiers, reflection progress, or pending event queues.

To remove all locally stored favorites, history, journal content, preferences, and identifiers on Android, open Android Settings, select Apps, select MycOracle, then use the Storage option to clear the app's storage. Android labels vary by device.

There is no MycOracle account to delete and no MycOracle server-side activity profile in the current Android release. You may contact us if you have a deletion question about information associated with a request to this webpage.

10. Data security

MycOracle relies on Android's app-storage protections to separate its local data from other apps. The app does not add separate application-level encryption to its AsyncStorage records. No storage or transmission method can be guaranteed completely secure.

11. Children's privacy

MycOracle does not ask for a user's age and does not request a child's name, contact details, or other personal information. If you are a parent or guardian with a privacy concern about a child's use of the app, contact us at the address below.

12. User choices and controls

You can choose whether to create journal entries. MycOracle does not request optional device permissions for location, contacts, camera, microphone, photos, or files. Use Android's clear-storage control as described above when you want to erase all local MycOracle data at once.

13. Changes to this policy

We may update this policy when MycOracle's data practices change. The updated page will show a new “Last updated” date. Material data-handling changes will be reflected here before they are introduced in a released version of the app.