GK’s Study Centre LLC operates OETify. It is a Delaware (USA) limited liability company. For privacy requests, contact support@oetify.com.
Last updated 12 October 2026
Data we collect and why
OETify uses account and learning data to deliver your study plan, feedback and saved work. It also uses data for authentication, security, purchases, support and legal obligations.
| Data | What it includes | Purpose |
|---|---|---|
| Account and identity | Account ID, account type/status, email, display name, timestamps, linked identity provider and its identifier | Sign-in, recovery, linking and account administration |
| Profile and plan | Profession, locale, timezone, accessibility choices, exam date, skill targets and weekday study minutes | Adapt study work and display it in your timezone |
| Preferences | Session length, download/Wi-Fi choices, reminders and quiet hours | Apply your study and notification choices |
| Learning record | Responses, attempts, timing, completion, evaluations, evidence, readiness estimates, plans and review work | Give feedback, track progress and adapt future work |
| Writing | Typed text, planning, submissions, handwriting photos, transcription, confidence and feedback | Evaluate your response and explain improvements |
| Speaking | Live microphone audio, transcript turns, timing/latency and feedback; optional replay audio | Transcribe and continue role-plays, then give feedback |
| Agency records | Organisation, members/roles, candidate email, invitations, sponsorship, seats and sharing grants | Deliver invitations, manage seats and enforce chosen sharing |
| Billing | Provider/customer/transaction references, amount/currency, subscription periods/status, access and allowance use | Confirm purchases, reconcile refunds and enforce allowances |
| Device and security | Hashed session IP/user-agent, device/installation IDs, push tokens/platform, sync receipts | Protect sessions, sync work and deliver enabled notifications |
| Optional app diagnostics | Session/crash signals, app version, Android/iOS platform, OS major, device class and timestamps | Check reliability when you consent |
| Support | Conversations, issue categories, appeals, content reports and routing history | Handle your request; internal staff notes are separate |
| Optional official results | Test date/mode, scores, verification and evidence reference | Store the result you choose to record |
| Consent record | Purpose, document/effect-policy versions, grant/withdrawal, source, time and evidence | Apply and audit your choices |
An agency may provide your email for an invitation before you have an account. An invitation or payment does not authorise progress sharing.
Legal bases for using your data
We use your data only when we have a legal reason to do so.
| Legal basis | What it covers |
|---|---|
| Contract: providing the service you signed up for | Account and identity, profile and plan, preferences, learning record, Writing and Speaking feedback, purchases and allowances, support, agency seats and invitations |
| Consent, which you can withdraw | Live Speaking transcription, saved-audio replay if switched on, optional app diagnostics, product-news email, push messages and progress sharing with an agency |
| Legitimate interests | Device and security records, preventing fraud and misuse, monitoring service operations and performance, and improving OETify |
| Legal obligation | Payment, tax, accounting, audit and dispute records |
Where we rely on legitimate interests, you can object, as described under Your rights.
Writing, live audio and optional consent
Use fictional or de-identified cases in Writing, photos, Speaking and support messages. Do not submit real patient names, dates of birth, record numbers or confidential case details. Text and transcript checks screen out likely identifiers, but they cannot remove patient information from a handwriting photo. The AI model receives the photo so that it can read your handwriting.
To use your account, you accept the current Terms, Privacy policy and Essential AI Processing documents. Essential AI processing covers your Writing text, Speaking transcripts and task context, used for feedback and role-play. If you decline, you can still read the documents, but you cannot use learning activities. You cannot withdraw these required choices and keep an active account; instead, you can delete your account. Accepting the Privacy policy does not mean you agree to any optional processing.
Live transcription needs your consent, which we record, and your device’s microphone permission. You can withdraw transcription consent without deleting your account. After you withdraw, no new live transcription sessions start, but processing already completed cannot be undone. We do not keep raw microphone audio after the session; completed transcripts and feedback stay in your learning record.
Saved-audio replay is switched off. If we switch it on, your audio is saved only with your separate replay consent, and for no more than 30 days. To replay a session, your current permission must match the permission recorded for that session. You can delete an individual replay or withdraw replay consent to request deletion of saved audio and unfinished uploads. This keeps transcripts and feedback. Any future audio-calibration research needs a separate opt-in; replay consent does not authorise research.
In Settings, open Privacy and data to view consent history. Use its audio, optional analytics and agency-sharing controls to change those permissions. Saved-audio controls appear only when saved-audio replay is switched on. If you withdraw analytics consent, your session and crash events are removed from optional app reliability summaries. Records we need to run and protect the service follow their own retention rules.
Product-news email is off until you turn it on and give consent. To stop it, turn off Product news (optional) in Settings and save. Push messages need your opt-in and your device’s notification permission. You still receive security, subscription and account-access emails when Product news is turned off.
Any future use of official results for research needs separate permission. Storing a result does not give that permission. For other privacy requests, email support@oetify.com.
OETify does not use your submissions to train AI models. If we ever offer a training opt-in, it will be optional and specific, and you will be able to withdraw where the law allows. This covers OETify only; external providers have their own retention and training practices.
Providers and what they receive
OETify uses the providers below for the purposes listed. Some providers support optional features or purchase options, and they receive data only when you use those features.
| Provider | Data received and use |
|---|---|
| DeepSeek | Handwriting image or lesson Writing text, task context and server instructions for evaluation; baseline Writing text or final Speaking transcript. Speaking dialogue uses recent conversation text and role state; feedback uses completed transcript and filtered timing metadata. These requests do not intentionally include account email/name, but your submissions may contain personal data. |
| OpenRouter, routing to inference.net, Inceptron or Baseten | Typed Writing letters, task context and server instructions for evaluation. OpenRouter passes each request to one of these three hosts only, with OpenRouter’s data collection switched off, and records the request for billing. These requests do not intentionally include account email/name, but your letter may contain personal data. |
| Soniox | Live microphone audio for transcription; a temporary-access request includes an opaque session ID, expiry and duration limits. |
| Fish Audio | Generated interlocutor reply text, selected voice and audio settings to create counterpart speech. It does not receive your microphone recording through this integration; reply text may reflect personal data in the conversation. |
| Inworld (backup voice provider) | Interlocutor reply text, voice/model and audio settings for counterpart speech. Content authoring also sends authored text and voice settings, which is separate from learner audio. |
| Mailgun | Recipient, sign-in/recovery link or code and expiry; notification subject/text and invitation links for email delivery. |
| Expo Push Service, Google Firebase Cloud Messaging and Apple Push Notification service | Expo receives the push token, title/body and limited destination ID, then bridges to Google/Apple delivery. Receipt checks use ticket IDs. Support messages use fixed notification text and opaque ticket IDs, without support reply contents. |
| Stripe | Learner/customer references, selected product, checkout/request keys, quantity and return URLs for web purchases. Hosted checkout collects payment/address information. Agency checkout sends organisation/order IDs and seat quantity, and requests billing address/tax ID. Refunds use payment references and amounts; candidate submissions are excluded. |
| RevenueCat | OETify account ID, product/offering purchase and restore operations, and subscriber lookups for native billing. OETify receives store/product/transaction, cancellation and timestamp fields. |
| Apple App Store and Google Play | Native product/package purchase, restore and store-management operations through RevenueCat. |
| Google and Apple, if you sign in with them | Client ID, callback, security state and requested identity scopes. OETify receives the provider identifier and available name/email; learner submissions are not sent for sign-in. |
| Cloudflare R2 | Encrypted private photos, optional replay audio and exports, object keys/sizes and request metadata. OETify controls decryption. Course audio can use direct signed playback; private learner objects cannot. |
| Fly.io | API and background processing in Singapore and operational log output, with request/network information needed for serving. |
| Supabase | Managed PostgreSQL database in Singapore (ap-southeast-1) for account, learning, agencies, privacy and billing. OETify does not use Supabase Auth or Storage as its account or object authority. |
| Cloudflare Pages and DNS | Hosts the website and web app and delivers the oetify.com domain; receives normal request and network information. |
| OETify’s own servers (Helsinki), when in use | Encrypted database backups and lists of stored files (see Retention). Monitoring receives limited operational events, counts and response times from Fly.io logs; learner content is excluded from monitoring. |
Hosted payment pages and in-app billing tools may collect their own diagnostic data. The table covers the data OETify sends and receives, not the diagnostic data those providers collect themselves.
International transfers
Your data may be processed outside your country. Our API runs on Fly.io in Singapore, and our database is hosted by Supabase in Singapore (ap-southeast-1). Backups and OETify’s own monitoring, when in use, run on servers in Helsinki. Cloudflare R2 chooses its storage region automatically, so we cannot promise that stored files stay in a particular country. Typed Writing feedback is processed through OpenRouter (United States) by inference.net (United States), Inceptron (Sweden and Finland) or Baseten (United States), whichever is available. Other providers may process data in other locations. When your data is processed outside your country, we rely on our providers’ contractual safeguards to protect it.
Retention
OETify keeps data for the periods below. Our providers set their own retention periods.
| Record | Retention rule |
|---|---|
| Raw Speaking audio | Transient; no default replay storage |
| Optional replay audio | Up to 30 days |
| Handwriting photos | 30 days in encrypted storage |
| Export bundle | 7 days |
| Writing text, evaluations and learning evidence | Kept for the life of your account; no fixed expiry is set |
| Authentication challenges | 30 days from creation |
| Expired sessions | 30 days after refresh expiry |
| Notification content/provider references | 30 days; records may be anonymised instead of fully deleted |
| Support conversations | 730 days after closure |
| Records of service operations and performance measurements | 30 days |
| Accounting, audit and dispute evidence | May remain after account deletion; no fixed expiry is set |
Scheduled deletion removes expired files and eligible records, and retries any that fail. You may lose access to an expired file before it is deleted. Legal holds can require records to remain instead of being deleted. Learning evidence stays for the account’s lifetime; accounting and audit exceptions can also prevent deletion.
When backups are in use, they keep the newest 14 daily copies and 8 Sunday copies. Database copies and lists of stored files are encrypted. Those lists do not contain copies of the files themselves. Before any restored data becomes available, OETify reapplies the deletions it has recorded. Account deletion does not instantly erase historical backups.
Agency sharing
Paying for or referring you does not give an agency ownership of your account or private work. Sharing requires your active, unexpired grant and the fields you choose. Depending on that grant, the agency can receive:
- Your display name and profession.
- Your declared goal and exam date.
- Plan adherence over 14 days and last activity.
- Readiness band, confidence and evidence count.
- Invitation, sponsorship and consent status.
Answers, Writing/photos, recordings/transcripts, corrections, detailed feedback, model instructions and support records are excluded. You can update or revoke your grant; agency access and revocation are recorded. Agency CSV exports use the same field limits. Revoking access does not erase an export an agency has already downloaded.
Your rights
Depending on where you live, you have the right to:
- access the data we hold about you;
- correct data that is wrong;
- delete your account and data;
- export your data in a structured file you can take elsewhere;
- object to, or ask us to restrict, how we use your data;
- withdraw consent at any time, without affecting processing already done.
Use Settings, then Privacy and data, for exports, deletion and consent choices. For any other request, email support@oetify.com; we reply without undue delay. Some records must be kept by law, as described under Retention.
You can edit your display name, locale, timezone and accessibility choices in your profile. For other corrections or privacy requests, use in-app support or email support@oetify.com.
In Settings, open Privacy and data to request an export. Your export is a JSON file, a structured data file available only through your signed-in account. It includes available profile, goals, responses, feedback, plans, Writing, Speaking and mock records. It also covers consents, billing/allowances, agency relationships, notifications/devices, support and results. The bundle is encrypted, belongs to your account and expires after 7 days. Photos and audio are accessed separately through your signed-in account, only while available and unexpired. Replay also needs the enabled saved-audio feature and your current replay permission. Photos and replay audio from a mock become available only after that mock is complete. Exports exclude sign-in secrets, unrelated users’ records, internal staff notes and detailed provider-operation records.
Account deletion needs fresh email identity confirmation and the typed confirmation DELETE MY ACCOUNT. There is a 24-hour grace period. You can cancel while the request remains scheduled and before its deadline. Work still running can delay deletion; records that must legally be retained can block it and leave the account intact. Completion requires physical removal of the account’s private objects and unfinished uploads. This is not a promise of completion within 24 hours.
Completed deletion removes learner-owned records and removes or replaces learner references in retained accounting, cost and audit records. It does not erase all transaction or audit history. A separate access key lets you check a deletion receipt without account content.
Account deletion cancels linked learner Stripe subscriptions and deletes the Stripe customer record; it does not request a refund. Account deletion does not confirm cancellation of Apple/Google subscriptions or erasure of every provider copy. Manage store subscriptions through the original store; see the refund policy. Device cleanup may leave drafts, downloaded exports or files saved elsewhere.
Complaints
If you are unhappy with how we handle your data, please email support@oetify.com first so we can try to put it right. You can also complain to the data-protection authority where you live. Examples are the Information Commissioner’s Office (UK), the Data Protection Commission (Ireland), the Data Protection Board of India and the National Privacy Commission (Philippines).
Children
OETify is for adult healthcare professionals and is not directed at anyone under 18. Our Terms require learners to be 18 or older; we do not ask for or check your age. If you think someone under 18 is using OETify, tell us at support@oetify.com.
Security and website storage
OETify encrypts website, app, database and email connections using HTTPS and TLS, which protect data during transfer. Sign-in secrets are stored as hashes, values that cannot be used directly as sign-in credentials. Session credentials are replaced or revoked, and access checks limit data to its owner. Private files use AES-256-GCM encryption; OETify checks access before decrypting them. Browser drafts use IndexedDB, the browser’s database for saved study work. They do not use the phone’s protected Keystore or Keychain storage. Production error logs omit request bodies and provider responses; protected learning records still contain your submissions. These controls do not promise that a breach is impossible.
OETify’s own public-site code sets no application cookies or browser storage and adds no analytics or advertising trackers. This excludes automatic data collection by hosting and payment providers. Answers you type in the website’s free practice stay in your browser and are not sent for AI evaluation. The app uses authentication cookies and workflow storage described in the cookie policy.
Changes and corrections
We may update this policy. If we make a material change, we will tell you in the app or by email. If required in-app documents change, learner activities require acceptance of their current versions. Report policy errors to support@oetify.com. We reply within 7 days, and a corrected page shows a dated note explaining the change.