Privacy Policy

Effective

2026-05-19

Last updated

2026-08-11

This policy describes what data vocapi (operated by Johnathan Jay Oneal) collects, why we collect it, and the choices you have. It applies to the vocapi mobile application and this website.

We are not in the business of selling your data, and we do not show advertising. We collect only what we need to make the product work and understand where the experience is confusing or failing.

The short version

• We collect your sign-in identity (Google or Apple) so we can recognize you across devices.
• If you add a profile photo, we store a normalized private copy and use Google Cloud Vision to check it for safety before it can appear to other members.
• We store your learning progress (which words you have reviewed, how often you got them right, your daily activity) so the spaced-repetition algorithm can schedule your next review.
• We use a small set of third-party services for payments (RevenueCat), error tracking (Sentry), and optional product analytics (PostHog). You can turn off analytics in Settings.
• We do not record routine sessions for product analytics or track you across other apps or websites. If the app reports an error, Sentry may receive a replay of the interactions leading up to it, with all on-screen text and images masked.
• You can delete your account at any time from the app, which removes your account and learning data from our database. Some third-party diagnostic and transaction records follow the retention periods below.

What we collect

Account identity

When you sign in with Google or Apple, we receive a unique identifier issued by that provider (an opaque user ID) and an email address, which Supabase Auth stores with your auth account. With Apple Sign In, that email may be a private relay address. Google or Apple may also provide a profile name; it can initialize your public display name, which you can edit.

Learning data

You create this data by using the app:

• Languages you have enrolled in
• Lessons you have completed
• Spaced-repetition card state (next review time, accumulated stability and difficulty per item, lapse count)
• Review history (which card, whether you answered correctly, how long you took, when)
• Streaks and per-day activity totals
• Reading progress on cultural content
• Optional preferences: daily goal, reminder time, timezone

Profile photos (only if you add one)

You can choose an image from your photo library, take one with your camera, or explicitly choose the photo supplied by Google Sign-In. We access only the image you choose or take. The original is processed in memory: we correct orientation, crop it to a square, resize it, remove embedded metadata, and encode a normalized WebP. We do not store the original file.

We store the normalized image in a private Supabase Storage bucket and send those exact same normalized bytes to Google Cloud Vision SafeSearch solely to check whether the photo is suitable for a social profile. Google returns category likelihoods; it does not decide your account status. Clearly acceptable photos can be approved, clearly unsuitable photos can be rejected, and ambiguous results can be reviewed by an authorized vocapi operator. A pending or rejected photo is not shown to other members. If you already have an approved photo, it remains in place while a replacement is checked.

An approved photo can be seen by you and by another signed-in member only when both of you have joined the community, you have a pending or accepted friend relationship, and neither has blocked the other. The storage bucket itself is not public. If someone reports an offensive profile, we preserve the exact private photo version that was visible when the report was filed so an authorized operator reviews the right evidence, even if the profile owner later changes or removes it.

Subscription state

If you purchase a subscription, the App Store or Google Play handles your payment. We receive — via RevenueCat, our subscription manager — your transaction ID, subscription tier, expiry dates, and billing event timestamps. We never see your card number, billing address, or any other payment information.

Push notification tokens (only if you opt in)

If you allow notifications, we store the Expo push token issued by your device so we can send the daily reminder you chose. The token is opaque (it does not identify you outside of our database).

Product analytics events (only while analytics is on)

We record a small number of named events to understand how onboarding and the first learning session go. These events do not contain anything you typed or any sensitive content. Example events: signup_completed, language_picked,daily_goal_set, first_lesson_completed. Each event is tagged with your opaque account identifier — the same stable ID we use to recognize you across devices, not a fresh per-session value — along with platform metadata (operating system, app version). This is identified product analytics, not anonymous analytics.

Whether analytics starts on or off depends on where you are when you create your account: if you are in the European Economic Area or the United Kingdom, it starts offand only runs if you turn it on; everywhere else it starts on and you can turn it off at any time. Either way, the Product analytics control in Settings takes effect immediately and is honored on both the client and our servers.

Diagnostic and crash data

To find and fix bugs we use Sentry, which captures unhandled errors with a stack trace, the screen or endpoint where the error occurred, navigation breadcrumbs, and your account identifier. When an error occurs, the mobile app is also configured to send Sentry a replay of the interactions leading up to that error, with all on-screen text and images masked so it cannot capture what you typed or your answers. Routine sessions are not sampled for replay.

Authentication metadata

Supabase Auth (our authentication provider) stores the IP address and user-agent of your most recent sign-in, used to detect compromised sessions. We do not log or store IP addresses elsewhere in the application.

Approximate country (at sign-up)

When you first sign in, our network provider (Cloudflare) derives an approximate country from your IP address. We use this country code once, solely to set your analytics consent default correctly for your region (see above), and we do not store your IP address or use this for any other purpose.

What we do not collect

• Precise location data (we derive only an approximate country from your IP, as described above)
• Contacts, photo-library content other than the one image you explicitly choose, video, audio, or microphone content
• Advertising identifiers (we do not have advertising)
• Browsing history outside the vocapi app
• The content of free-response exercises in our product-analytics events (we record the outcome, not the answer text)

Third parties we share data with

We only share data with the providers we need to run the service. Each is listed below with what it receives and why.

All of these services are bound by their own privacy policies and may process data in the United States or other countries where they operate. We do not use any of them to advertise to you.

How long we keep your data

• Account and learning data: until you delete your account, at which point your auth account and every learning record tied to it are removed from our database.
• Profile photos: while the approved photo is in use or a new version is being checked. Rejected, replaced, removed, and abandoned objects are deleted through the upload/removal workflow and a storage audit. If a report captured a particular version, that private object is kept as evidence while the report and reported account exist. All profile-photo objects, versions, reports, and moderation events tied to the account are removed when the account is deleted.
• Diagnostic data (Sentry): 30 days by default at Sentry's end.
• Analytics events (PostHog): 90 days by default at PostHog's end.
• Subscription records (RevenueCat / Apple / Google): retained per the payment provider's policy, typically for audit and tax purposes.

Your rights and choices

Access, export, and deletion

You can delete your account at any time from the app's Settings screen. Deletion is immediate and first removes every private profile-photo object, then removes your auth account and every database record tied to your user ID, including reports and retained photo evidence. If private-object cleanup cannot complete, deletion stops and reports an error rather than leaving photos behind without their ownership records. Some diagnostic and payment-provider records follow the separate retention periods above. If you would like a copy of your data before deletion, contact us at the email below and we will export it for you.

Turn analytics on or off

In Settings, use the Product analytics toggle. Enabled events are associated with your opaque account identifier, so this is identified product analytics rather than anonymous analytics. The control takes effect immediately on your device and is honored by our servers. If you are in the EEA or UK it starts off until you turn it on; everywhere else you can turn it off at any time.

Notifications

You can change your reminder time, turn notifications off, or revoke the OS-level permission at any time from your device's settings or from the app.

Photos and camera

You can deny or revoke photo-library or camera permission in your device settings. The app will continue to work with initials instead of a profile photo. Removing a profile photo stops displaying it; a reported version may remain private as evidence until the report or account is deleted, as described above.

If you live in the European Economic Area, the United Kingdom, Switzerland, or California

You have additional rights under GDPR, UK GDPR, and CCPA, including the right to access, correct, restrict, or port your personal data, and the right to object to certain processing. Email us at privacy@vocapi.app and we will respond within the legally required window (30 days for GDPR, 45 days for CCPA).

Children

vocapi is not directed at children under 13 (under 16 in the EU). We do not knowingly collect personal data from children. If you believe a child has provided us with their information, please contact us and we will delete it.

Security

Authentication tokens are encrypted at rest on your device using your platform's secure storage (Keychain on iOS, EncryptedSharedPreferences on Android). All network traffic between the app and our backend uses HTTPS. Our database enforces row-level security so one user cannot read another's data, even in the event of a bug in our application code. Profile-photo objects are private and are served only after the backend rechecks the viewer, relationship, community-consent, block, version, and approval state.

Changes to this policy

If we materially change how we handle your data, we will update this page, change the "Last updated" date at the top, and notify you in-app before the change takes effect.

Contact

Johnathan Jay Oneal
Privacy questions: privacy@vocapi.app
General support: vocapi.app/support