PokieYou Privacy Policy
Last updated: 2026-11-08
This policy explains how PokieYou handles information when you use the PokieYou mobile app, website, and launch waitlist.
PokieYou is designed as a private, local-first care-memory and reminder app. The main app experience works without an account, without contacts access, and without uploading your saved care cards or reminders to PokieYou.
PokieYou is a general-audience app for people aged 13 and over. It is not designed for children under 13.
Who We Are
PokieYou is the app and product name. PokieYou is operated by Pasindu Ekanayake. In this policy, "PokieYou", "we", "us", and "our" mean Pasindu Ekanayake as the operator of the PokieYou app.
Privacy contact: support@pokieyou.com.
What PokieYou Does Not Do
PokieYou does not:
- require an account before you can create useful local cards or reminders
- ask for contacts permission
- import your address book
- read SMS, email, WhatsApp, or messages from other apps
- auto-send messages to anyone
- sell personal information
- use care content for advertising
- run session replay or screen recording analytics
- include care text, reminder text, names, notes, dates, messages, prompts, or AI outputs in product analytics
- back up saved care cards or local reminders to the cloud by default
Information You Provide
Care sentences, cards, reminders, and notes
When you type a sentence such as a care moment or reminder, PokieYou uses it to create a suggested private card, message draft, timing suggestion, or local reminder.
Saved cards and reminders may include names, relationships, event summaries, dates, reminder times, follow-up schedules, message drafts, and reminder state. This information can be sensitive because it may describe your life or someone else's life.
By default, saved care cards and reminders stay on your device. They are stored in an encrypted local care-record file. The encryption key is stored through the device secure storage system.
PokieYou does not upload saved care cards, reminder bodies, message drafts, local notification IDs, raw capture text, AI prompts, or AI provider responses as cloud backup data.
Account information
You can use the app without an account. If you choose to create or use an account, PokieYou may process:
- email address
- password authentication data handled by Supabase Auth
- email verification and password recovery codes
- internal Supabase account ID
- Google sign-in token exchange data if Google sign-in is configured and you choose it
- Apple sign-in token exchange data if Apple sign-in is configured and you choose it
- active-device state
- account service state, such as quota, subscription, billing, or entitlement status
Accounts are for app services such as account access, Smart Read quotas, beta or paid-service state, and account deletion. Creating an account does not automatically back up or restore your local care cards or reminders.
Website launch waitlist
Before an app-store release is available, the PokieYou website may link you to a MailerLite-hosted signup form for the Android or iOS launch list. If you choose to join, the form collects your email address and records the platform list you selected. MailerLite may also process ordinary form-delivery information, such as submission time, IP address, browser or device information, and consent or confirmation status, under its own service terms and privacy practices.
The waitlist is optional and separate from a PokieYou app account. PokieYou uses this information to confirm your subscription, send relevant launch or availability updates, maintain the Android and iOS audience groups, prevent signup abuse, and manage unsubscribes. PokieYou does not ask you to provide care-card or reminder content through the waitlist.
Smart reading
Smart reading is optional. When Smart reading is available and enabled, PokieYou sends the sentence you submit, capped at 200 characters, to PokieYou's server interpretation service so it can help turn the sentence into a structured result. The request also includes the local date, device timezone and offset, a random request identifier, schema information, authentication context when signed in, and a hashed installation identity for guest quota enforcement.
The server may send the submitted sentence, local date, timezone information, a system instruction, and a structured-output schema to OpenAI for interpretation. PokieYou currently uses OpenAI's Responses API with application-state storage disabled for these requests. This does not mean that all provider-side processing has zero retention: OpenAI may retain API abuse-monitoring data for up to 30 days by default, unless different account-level data controls or legally required exceptions apply.
PokieYou's service is designed not to store raw care sentences, full prompts, provider responses, reminder content, names, message bodies, or local notification IDs in its operational records. It stores limited service metadata such as request identifiers, hashed quota subjects, model and route names, fixed status or failure codes, request-size buckets, token totals, latency information, and timestamps.
If Smart reading is unavailable, disabled, or fails, the app can use local reading or local templates instead. Turning Smart reading off keeps free-text interpretation on the local-template path.
Optional product analytics
PokieYou asks before collecting product analytics. You can choose Share usage data or Use without analytics, and you can change the choice in Profile.
If you opt in, PokieYou uses PostHog EU Cloud for content-blind product analytics. Analytics may include:
- screen names such as Home, Capture, Cards, Profile, or Account
- feature usage events
- fixed success, failure, or outcome labels
- coarse latency, token, and count buckets
- app version, build version, platform, OS name, and OS major version
- PostHog anonymous identifier while signed out
- internal account identifier prefixed with
acct:while signed in
Analytics does not include names, relationships, care details, notes, messages, reminder text, notification text, typed sentences, AI prompts, AI outputs, dates, times, record IDs, notification IDs, email addresses, URLs, route parameters, raw errors, stack traces, screenshots, or content-derived hashes.
PostHog is configured for EU ingestion, GeoIP disabled, autocapture disabled, app lifecycle capture disabled, exception autocapture disabled, and session replay disabled. As of 8 November 2026, the PokieYou project inherits its organization's Free-plan setting and retains Product Analytics events for one year. Session recordings, logs, person profiles, and other PostHog data types can have separate retention rules; PokieYou does not enable session replay.
When you turn analytics off, the app opts out, clears queued analytics, and resets the local analytics identity. This does not necessarily delete events that PostHog already received. Signed-out analytics history is not deliberately joined to a later account.
Subscriptions and RevenueCat
PokieYou uses RevenueCat and the applicable app store to operate subscriptions and paid entitlements. RevenueCat uses the internal Supabase account ID as the PokieYou App User ID. PokieYou does not deliberately attach your email address, name, or advertising attribution to RevenueCat, and automatic device-identifier collection is disabled in the RevenueCat SDK.
RevenueCat and the app stores may process transaction and subscription information needed to operate billing. PokieYou's server keeps a limited entitlement projection that may include the account ID, hashed billing subject, product and entitlement identifiers, store and environment, subscription status, access state, renewal or cancellation state, billing-retry or pending-payment state, relevant timestamps, and a one-way hash of the store subscription identifier.
PokieYou does not retain raw store receipts, purchase tokens, store order references, payment-card details, or raw RevenueCat webhook bodies. Webhook records are reduced to operational event, subject, processing-state, and timestamp information.
Beta feedback
In beta builds, Profile may include optional feedback and rating forms. Feedback is submitted separately from accounts, care cards, reminders, and analytics.
Feedback submissions may include:
- selected feedback category
- feedback message you type
- rating answers
- platform
- app version
- build version
- server timestamp
The app does not attach account ID, email, plan, card or reminder counts, care records, capture text, notification IDs, device model, or profile state to beta feedback.
PokieYou sends a random installation hash for abuse control. The server hashes it again with a server-only pepper and stores it separately from the feedback response. Feedback and rating responses are retained for 90 days in the current beta design. Rate-limit buckets are retained for about two days.
Local notifications
If you choose to set a reminder, PokieYou may ask for notification permission. The app shows a soft permission screen before the native prompt.
Local reminders are scheduled on your device. Notification copy is designed to be discreet and to avoid exposing sensitive care details on the lock screen. PokieYou does not currently use server push notification delivery for the local reminder flow.
Device and configuration information
The app may use basic app, platform, installation, and configuration information to run local features, check usage limits, submit beta feedback, or operate optional analytics. Server-side quota systems may store hashed installation or account subjects for abuse prevention and usage limits.
How We Use Information
PokieYou uses information to:
- create local care cards, message drafts, and reminders
- save and display your local cards and reminder history
- schedule local notifications you choose
- provide optional Smart reading
- manage account creation, login, verification, password recovery, logout, and account deletion
- enforce Smart Read quotas and service limits
- support optional beta feedback
- understand content-blind product usage when analytics is enabled
- protect app services from abuse, fraud, and excessive automated use
- maintain security and troubleshoot service availability without logging private care content
- manage the optional Android and iOS launch email lists and send requested launch updates
Where Information Is Stored
On your device
The main care-record data is stored locally on your device. This includes saved care records, reminder metadata, message drafts, and local scheduling state.
PokieYou stores the care-record bundle as an encrypted local JSON payload. The encryption key is stored with Expo SecureStore. Some app preferences, usage cache data, or non-care operational state may use local device storage.
If you delete the app, reset local data, lose the device, or replace the device, local care cards and reminders may be lost. An account alone does not restore local cards.
With Supabase
PokieYou uses Supabase for account services, email/password authentication, optional Google and Apple sign-in exchange, active-device enforcement, account deletion, Smart Read quota controls, AI interpretation service functions, beta feedback, subscription and entitlement projections, RevenueCat webhook processing, and sanitized service, billing, and health records.
The active app does not use Supabase as cloud backup for saved care cards or local reminders. Historical backup tables are dormant and locked down in the current app direction.
With PostHog EU Cloud
If analytics is enabled, content-blind product analytics is sent to PostHog EU Cloud.
With RevenueCat and app stores
If you use a subscription or paid entitlement, subscription and transaction information is processed by RevenueCat and the applicable app store. Payment-card details are handled by the store or payment provider, not by PokieYou.
With AI providers
When Smart reading is enabled and a sentence is submitted, PokieYou's server may send that sentence to an AI provider for interpretation. This is optional and is handled through PokieYou's service, not by placing AI provider credentials in the mobile app.
With MailerLite
If you choose a website launch list, your email address, selected platform group, consent or confirmation state, and related signup metadata are processed in MailerLite. PokieYou links to MailerLite-hosted forms rather than loading MailerLite's universal form-tracking script on the PokieYou website.
Sharing
PokieYou may share information with service providers that help operate the app:
- Supabase for authentication, server functions, database services, account deletion, beta feedback, and quota controls
- PostHog EU Cloud for optional product analytics when enabled
- RevenueCat and the applicable app store for subscriptions, transaction state, entitlement access, restoration, and billing support
- Google only when you choose Google sign-in and the provider is configured
- Apple only when you choose Apple sign-in and the provider is configured
- AI providers only for optional Smart reading requests submitted through PokieYou's server
- email delivery providers configured through Supabase Auth for account verification and password recovery
- MailerLite for the optional Android and iOS launch email lists, double opt-in confirmation, launch emails, and unsubscribe handling
Service providers are used to provide the app. PokieYou does not sell personal information or share care content for advertising.
We may also disclose information if required by law, to protect the app or users, or to respond to valid legal process. Because local care cards are not backed up to PokieYou by default, PokieYou generally does not hold server copies of those local card details.
Retention
Different information has different retention:
- Local care cards and reminders stay on your device until you delete them, reset local data, uninstall the app, or device storage removes them.
- Local notification data stays on your device as needed to schedule and route reminders.
- Pending account verification data is stored on the device only as needed to finish account setup or recovery.
- Supabase Auth account data is kept while your account exists.
- Account-owned service data is deleted or cleaned up through the account deletion flow where supported.
- PostHog Product Analytics events are currently retained for one year under the project's inherited organization setting. Other PostHog data types may follow separate rules.
- Optional beta feedback responses are retained for 90 days in the current beta design.
- Beta feedback rate-limit buckets are retained for about two days.
- Smart Read request-operation records are generally retained for about seven days, monthly usage records for about three months, abuse events for 90 days, and aggregate usage metrics for up to 13 months.
- Processed billing webhook records and billing support audit records may be retained for up to 12 months.
- Expired subscription projections may remain for about 60 days after access ends. A hashed purchase-binding record may remain until about 60 days after the verified subscription end date.
- Some encrypted Supabase backup copies may continue to contain server-side account or service records after active records are deleted. Backups are kept for recovery and integrity purposes, are not used as active app data, and may not be removed immediately when an account is deleted.
- Waitlist subscription data is retained in MailerLite while you remain subscribed or while reasonably needed to maintain consent, suppression, security, or legal records. You can unsubscribe using the link in a waitlist email or contact PokieYou to request access or deletion.
Your Choices
You can:
- use the app without creating an account
- use the app without analytics
- turn analytics on or off in Profile
- turn Smart reading on or off in Profile
- use local templates when Smart reading is off
- decline notification permission
- save a card without notifications
- delete individual local cards
- reset local data on your device
- create, log out of, or delete an account if account services are configured
- choose whether to join an Android or iOS launch list, decline the list entirely, unsubscribe through any waitlist email, or contact PokieYou about waitlist data
Deleting an account is separate from resetting local data. Account deletion removes account-owned service data where supported, but it does not automatically erase local cards stored on the device. Resetting local data is the device-local action for removing local cards and reminders.
Account Deletion
If you have a linked and verified account, you can request account deletion through the app Account screen or by emailing support@pokieyou.com from the email address linked to your PokieYou account. In-app deletion requires a valid session, recent reauthentication, safe billing verification, and any renewing subscription to be set not to renew.
The account deletion process requests deletion of account-linked PostHog person and event data where supported, deletes the Supabase Auth user, removes account-owned entitlement and active-device records, and removes authenticated Smart Read quota rows on a best-effort basis.
Account deletion does not upload, delete from the server, or recover local care cards because those cards are not stored in PokieYou cloud backup by default. Use the app's local reset option if you also want to remove local cards and reminders from the device.
Account deletion does not cancel or refund an app-store subscription, automatically erase the RevenueCat customer, immediately remove all pseudonymous billing or operational records, remove anonymous PostHog events that were never linked to the account, or guarantee immediate removal from encrypted backups. You may contact support@pokieyou.com to request the separate RevenueCat customer-erasure workflow. Restoring a purchase later may send the transaction to RevenueCat again and recreate a provider record.
We aim to respond to account deletion requests within 30 days.
Regional Privacy Rights
Depending on where you live, you may have rights to request access, deletion, correction, portability, restriction, objection, or information about how personal information is used. You may also have the right to withdraw consent where processing is based on consent.
Because many PokieYou records are local-only, PokieYou may not be able to access or export local care cards from its servers. Local deletion and reset controls are handled on the device.
For account, analytics, beta feedback, waitlist, or server-side service data, contact PokieYou at support@pokieyou.com.
California residents may have rights under California privacy laws. PokieYou does not sell personal information and does not use care content for cross-context behavioral advertising.
Children
PokieYou is not designed for children under 13. Do not use PokieYou if you are under 13. If a parent or guardian believes a child has provided account information to PokieYou, contact us so we can review and delete account-side information if any exists.
Security
PokieYou uses privacy-by-design controls intended for a sensitive personal reminder app:
- local-first saved care records
- encrypted local care-record storage
- device secure storage for encryption keys and account sessions
- no contacts permission
- no message scraping
- no auto-send behavior
- server-side handling for services that need private credentials
- no AI provider secrets in the mobile app
- content-blind analytics controls
- discreet notification copy
- server-side quota and abuse controls that avoid storing care text
No app or system can guarantee perfect security. Keep your device protected, use a strong device passcode, and be careful when typing sensitive information.
International Processing
PokieYou's service providers may process information in countries other than where you live. PostHog analytics is configured for EU ingestion. Supabase, MailerLite, and other providers may use their own infrastructure and subprocessors.
Changes To This Policy
PokieYou may update this policy as the app changes. The Last updated date will show when the policy changed. Material changes should be reflected in the app or on the published policy page before or when they take effect.