Privacy Policy
Your private studio stays on your iPhone.
Effective . This policy covers the PourKeeper iPhone app, website, support service, and optional Creator Credits features.
The short version
PourKeeper is a private, local-first acrylic pour journal. Artwork photos, recipes, color selections, titles, outcomes, tags, and notes are stored on your iPhone. They are not uploaded to PourKeeper's servers for normal Studio use. V1 has no public feed.
An account is not required to create or read private pours. Sign in with Apple is used only if you choose Creator Credits. PourKeeper does not track you across apps or websites and does not sell your personal information.
Information stored only on your device
The following information stays in the app's local storage unless you deliberately share it through an iOS share sheet:
- wet and dry artwork photos;
- techniques, colors, recipe fields, titles, tags, outcomes, and notes;
- experiment relationships and progress summaries;
- local notification preferences and pending dry reminders.
You control any copy sent to Photos, Messages, social media, cloud storage, or another app through the system share sheet. The destination's privacy policy applies after you choose to share.
Information sent to our service
First-party product events
PourKeeper sends a random installation signal that is hashed on the server, a random event ID, a timestamp, and one permitted interaction event. A permitted event may indicate app activation, first, second, or later pour save, dry-result completion, Pour Card opening, paywall entry, Creator Credits opening, or a bounded purchase or restore outcome.
These events do not contain artwork, recipes, colors, titles, notes, outcomes, tags, Apple identity tokens, StoreKit transaction bodies, advertising identifiers, or arbitrary metadata. We use them to understand whether core features work and to make product decisions.
Optional Creator Credits account
If you choose Creator Credits, PourKeeper uses Sign in with Apple without requesting your name or email scope. The service receives an Apple-derived account identifier and stores records needed to:
- create and accept expiring invitation links;
- prevent the same account or installation from earning duplicate rewards;
- record the timestamps and minimum facts that an original Wet-to-Dry story was completed;
- maintain the two-sided USD 2 credit ledger, five-credit cap, and earned price tier;
- assign a one-time Apple offer-code redemption URL;
- verify Studio Lifetime purchase, restore, refund, or revocation state;
- retain limited security and idempotency records.
The Creator Credits service does not receive the wet or dry photo, technique, colors, outcome, recipe, title, tags, or notes. Apple processes the purchase. PourKeeper does not receive payment-card or bank details.
Why we use information
We use collected information only to provide app functionality, prevent referral and purchase abuse, answer support requests, measure the private learning loop, maintain service security, and meet legal obligations. We do not use it for third-party advertising or cross-app tracking.
Service providers
- Apple, for App Store distribution, StoreKit purchases, TestFlight, Sign in with Apple, system notifications, and user-directed sharing;
- Supabase, hosted in East US (North Virginia), United States, for optional authentication, Creator Credits, purchase-verification records, and bounded first-party product events. Under its Data Processing Addendum, Supabase acts as a processor or service provider and is contractually limited to processing covered data for the services.
We may disclose information when required by law, to protect users or the service, or during a business transfer subject to appropriate confidentiality and notice. We do not sell or rent it.
Retention
- Local Studio data remains until you delete a pour, delete the app, or erase the device.
- Raw product interaction events are deleted or irreversibly aggregated after 13 months.
- Active Creator Credits account and reward records remain while the account is active.
- Identifiers in account-owned records are deleted when you use in-app account deletion. Limited transaction, anti-fraud, and audit facts may be retained or de-identified for up to 24 months where necessary.
- Account deletion applies to active service data. If a residual copy exists in a provider backup, it is not used for normal product operation and is removed when that backup expires or is deleted under the provider's retention process.
Your choices and deletion
You may use the private Studio without an account. V1 does not provide an in-app switch for the bounded first-party product events described above. Uninstalling the app stops future event delivery but may also remove local Studio data. You may contact us to ask about or object to this processing where that right is available in your location.
To delete an optional Creator Credits account:
- Open Settings > Creator Credits.
- Sign in if needed.
- Choose Delete Creator Credits Account and confirm.
The service deletes the authentication account and account-owned Creator Credits records, removes or de-identifies identifiers in limited historical records, and revokes unused invitations. Private on-device pours and a locally verified App Store entitlement remain because they are not part of the optional server account.
You may contact x819217@gmail.com about access, correction, deletion, objection, or other rights available in your location. We may need to verify the request without asking you to send identity tokens, offer codes, private recipes, or artwork.
Security and international processing
We use access controls, row-level security, signed StoreKit verification, bounded APIs, hashing, and data minimization. No method of storage or transmission is completely secure.
The selected database region is East US (North Virginia), United States. Supabase or its subprocessors may process data where they operate. When applicable, the Supabase Data Processing Addendum incorporates the EU Standard Contractual Clauses and the UK Addendum for covered international transfers.
Children
PourKeeper is not directed to children under 13, or the higher minimum age required in their location. We do not knowingly collect a child's personal information. Contact us if you believe a child has provided information through Creator Credits.
Changes
We may update this policy as the app changes. We will post the revised effective date and provide additional notice when required. Community publishing, cloud photo sync, advertising, or new data collection would require a policy and App Privacy update before release.
Contact
PourKeeper
Privacy requests: x819217@gmail.com