Privacy Policy

Effective date: 2026-08-01

This Privacy Policy explains how Rolko collects, uses, stores, and protects personal data.

1. Who we are

Rolko (“the Service”) is operated by SimpleStayChina Limited, a Hong Kong limited company.

For privacy questions or requests, contact: privacy@rolko.xyz.

For data protection purposes, SimpleStayChina Limited is the controller of the personal data described in this policy.

2. What we collect and why

Account data

We collect your email address and authentication identifiers through Supabase Auth. We use this to create your account, keep you signed in, and secure access to your data.

Lawful basis: contract.

Learning content

We store learning content you create or save, including vocab items, words, texts, transcripts, review history, and learning progress. We use this to provide learning, review, translation, and progress-tracking features.

Lawful basis: contract.

Uploaded-media transcription roadmap

Uploaded audio and video transcription is currently marked Coming soon. The Reading Workspace does not accept a new media upload, create a transcription job, or send media to a speech-to-text provider while this release state is active.

Historical uploaded-media jobs were processed by AssemblyAI for speech-to-text transcription. Historical completed transcripts remain part of the learning content covered above, and AssemblyAI may retain transcription data or a provider job identifier until deletion or cancellation is confirmed. We retain only the minimum provider cancellation identifier needed to finish an unresolved remote deletion after local account and learning data has been removed.

Lawful basis: contract for historical processing and deletion; no new roadmap upload is currently accepted.

Text processed by the Chrome extension

When the Chrome extension is active, it may process page text, subtitles, captions, or related language content to provide learning features such as tokenization, word lookup, translation, saving, and review.

Text is sent to our server or processing services only as needed to provide the features you use, such as saving content, translating text, looking up words, or syncing your learning data.

Lawful basis: contract and legitimate interests.

Page URLs

When you explicitly save content from a page, we may store the page URL with that saved content so you can identify the source later.

Lawful basis: contract.

Translation and language-processing services

Some text may be processed by translation, language-processing, or infrastructure services to provide app functionality. We use these services only to operate the Service and provide the features requested by users.

Lawful basis: contract.

Billing data

If you subscribe to a paid plan, Stripe processes your payment. We store Stripe customer, subscription, and payment-status identifiers. We do not store your card number.

Lawful basis: contract and legal obligation.

Referral attribution

When you follow a Rolko referral link, we record the referral code, a random anonymous visitor identifier, landing path, referring page where available, visit counts, and any later account attribution or paid conversion. We use this information to measure referrals, prevent abuse, and calculate a one-time commission for the referring partner.

Referral analytics do not store your IP address or full user-agent string.

Lawful basis: legitimate interests and contract.

Member referral rewards

If you use Share-to-Convert, we record the member referral reward ledger linking the referring member and referred account, the configured Pro reward duration, and the Stripe subscription and invoice identifiers needed to confirm the first payment and handle refunds, disputes, and abuse prevention. These records are used only to issue or reverse the promised reward and to maintain an auditable billing record.

Lawful basis: contract, legitimate interests, and legal obligation.

Acquisition analytics

When you follow a campaign-tagged Rolko link, we process limited campaign labels (source, medium, campaign, content ID, and creator ID) and funnel events such as signup, unconfirmed extension-presence observations, extension-runtime-confirmed activation, first stored transcript, first saved word, first review, activation, checkout, and first purchase. We use this to understand which acquisition activity is effective.

Vercel funnel telemetry does not include email addresses, account IDs, referral codes, payment identifiers, raw URLs, authentication tokens, provider error text, or free-form user content. Before sign-in, a private server-side event ledger uses a random cohort identifier to connect allowlisted page, CTA, and authentication stages. After a successful sign-in, those receipts can be associated with your account so first touch, latest meaningful touch, activation, and paid conversion can be measured. Linked receipts are removed through the account-deletion cascade. The ledger stores stable evidence identifiers, not transcript text or saved-word content.

Lawful basis: legitimate interests.

Optional advertising measurement

If you allow optional advertising measurement, we use the Meta Pixel and Meta Conversions API to measure whether visits from our ads result in page views, completed registrations, checkout starts, and first purchases. This helps us assess and improve our advertising.

Depending on the event, we may send Meta the event name and time, a stable event ID, the page path without its query string, product or offer, purchase value and currency, Meta browser or click identifiers, IP address, browser user-agent, and hashed email or account identifiers. Hashing is one-way pseudonymisation; it does not make the data anonymous. We do not send learning content, saved words, transcripts, payment-card details, referral codes, or authentication tokens.

Meta measurement is off by default. The Pixel is not loaded and Meta conversion events are not sent unless you choose Allow. You can decline without losing access to Rolkoand can withdraw or grant consent below at any time.

Lawful basis: consent.

Operational logs

We collect standard technical logs such as IP address, user-agent, timestamp, request metadata, and error logs. We use these for security, debugging, abuse prevention, and service reliability.

Lawful basis: legitimate interests.

3. Chrome Extension Limited Use Disclosure

The Chrome extension only uses page text, subtitles, captions, URLs, and related browsing-context data to provide the learning features requested by the user.

  • ✓We do not sell this data.
  • ✓We do not use it for advertising.
  • ✓We do not use it to build advertising profiles.
  • ✓We do not transfer it to third parties except as necessary to provide the Service, process payments, operate translation or language-processing features, maintain security, comply with law, or run the infrastructure described in this policy.

4. Where data is stored

Application data is stored in Supabase Postgres hosted in an EU region. Row-level security is used so each user can only access their own rows.

The Service is also hosted and operated using infrastructure and service providers listed below. Some providers may process data outside Hong Kong, the UK, or the EEA. Where required, we rely on appropriate safeguards such as contractual protections, standard contractual clauses, or equivalent transfer mechanisms.

5. Third-party service providers

We use the following service providers:

  • Supabase — authentication, database hosting, and storage.
  • Stripe — subscription billing and payment processing.
  • Vercel — application hosting, deployment infrastructure, edge requests, operational logs, and privacy-focused web analytics.
  • Meta Platforms — optional advertising measurement and campaign optimisation, only after you allow it.
  • AssemblyAI — historical uploaded-media speech-to-text processing and deletion or cancellation of historical provider records; no new media upload is accepted while the feature is Coming soon.
  • Translation and language-processing providers — translation, text analysis, language lookup, or related learning functionality.

We do not sell personal data. We share the optional advertising-measurement data described above with Meta only after you consent.

6. Cookies

We use the following strictly necessary cookies and similar technologies:

  • Supabase session/authentication cookies to keep you signed in.
  • Stripe cookies or similar technologies during checkout and billing flows.
  • Security or session-related cookies needed to operate the Service.
  • A first-party referral attribution cookie, retained for up to 90 days, so a valid referral can survive sign-in and checkout.
  • An HttpOnly internal/test traffic marker, retained for up to 90 days only after server-side admin or test-account approval.

Acquisition campaign labels are carried through tagged links and server-side metadata.Rolko does not set a client-readable acquisition analytics cookie or retain those labels in browser storage. A random, HttpOnly first-party cohort cookie may be retained for up to 90 days to join allowlisted acquisition stages; it contains no email, account ID, IP address, user agent, raw path, query, referrer, authentication token, or provider error text. For an untagged organic visit, a short-lived, HttpOnly first-party cookie may retain only an approved search-engine or AI-assistant source label for the auth handoff; it contains no query, path, search-term, or prompt data and is cleared after successful authentication.

If you choose Allow, Meta may set first-party _fbp and _fbc cookies for advertising measurement. We also store your allow or decline choice in the strictly necessary rolko_marketing_consent preference cookie for up to 180 days. Declining prevents the Meta Pixel from loading; withdrawing consent revokes Pixel consent and removes the known Meta browser and click cookies fromRolko's domain. For signed-in users, the current choice is also stored in the existing account settings record so a delayed purchase event can recheck the latest preference instead of relying on an earlier checkout choice.

Current optional advertising measurement choice: loading saved choice

The browser choice lasts up to 180 days. If you are signed in, your account choice stays until you change it or delete your account.

7. Retention

We retain account data and learning content for the lifetime of your account.

You can delete your account from the dashboard. When you delete your account, we delete or anonymise your account and associated learning content within 30 days, unless we need to retain limited information for legal, billing, security, fraud-prevention, or dispute-resolution purposes.

Stripe billing records may be retained for as long as legally required.

Referral conversion and commission records may be retained after account deletion in anonymised form where needed for billing, fraud prevention, partner payouts, and payout disputes.

Acquisition campaign labels stored with an account are deleted or anonymised with that account, except where the same limited labels must remain with billing records.

Your signed-in advertising-measurement choice is retained until you change it or delete your account. The browser preference cookie expires after up to 180 days.

Operational logs are retained only for as long as reasonably necessary for security, debugging, and service reliability.

8. Your rights

Depending on your location, you may have the right to:

  • Access the personal data we hold about you.
  • Request correction of inaccurate data.
  • Request deletion of your data.
  • Export your learning content.
  • Object to certain processing based on legitimate interests.
  • Request restriction of processing.
  • Withdraw consent where processing is based on consent.

You can exercise these rights through the dashboard where available, or by emailing privacy@rolko.xyz.

9. Account deletion

You can delete your account from the dashboard. You may also request deletion by emailing privacy@rolko.xyz.

After deletion, we delete or anonymise your account and associated learning content within 30 days, unless retention is required for legal, billing, security, fraud-prevention, or dispute-resolution reasons.

10. Children

The Service is not intended for children under 13, and we do not knowingly collect personal data from children under 13.

11. Security

We use technical and organisational measures designed to protect personal data, including authentication controls, database access controls, row-level security, HTTPS, and restricted operational access.

No online service can guarantee absolute security.

12. Changes to this policy

We may update this Privacy Policy from time to time. If we make material changes, we will update the effective date and, where appropriate, notify users through the Service or by email.

13. Complaints

If you have concerns, please contact us first at privacy@rolko.xyz.

Depending on your location, you may also have the right to complain to your local data protection authority.

14. Contact

For privacy questions or to exercise your rights, contact:

privacy@rolko.xyz