Skip to content

LEGAL · PRIVACY

Privacy Policy

Effective 15 November 2026

1. Provider and contact

“OperatorRank”, “we” and “us” mean the operator of the service identified in these Terms and this notice or, after a transfer, in the operator-transfer notice described below. The current operator and data controller is สุพจน์ ประทุมชาติ (Suphot Prathumchat), operating OperatorRank as an individual sole proprietor. The operator is not currently registered as a company and has no business registration number. We determine how account administration, service operation and security data are used. Legal contact address: 81 Soi Ekkachai 66, Ekkachai Road, Khlong Bang Phran, Bang Bon, Bangkok 10150, Thailand. Contact support@operatorrank.com for privacy questions or requests. Messages to that address are forwarded through Cloudflare Email Routing to the owner’s Gmail mailbox. Do not send passwords, sign-in codes, session credentials or system keys.

2. Information and purposes

We process account and profile information you provide, such as email, name, date of birth, avatar, language, time zone, CV and education/work details; identity-provider identifiers when you use a connected sign-in method; organization membership and assessment information; and credits, usage and support records. The fields collected depend on the feature you use. Google sign-in requests openid, email and profile; GitHub sign-in, where offered, requests read:user.

Mission records can include your AI messages and replies, code and attachments, edited/submitted files, tool actions, terminal commands and output, timestamps, Defense conversations, evaluation results and evidence of what happened in the workspace. We use these to provide the mission, evaluate work, show results and investigate technical problems. Support staff and authorized support AI may inspect relevant account, company, mission, timeline, log and ticket information when investigating a case.

We also process IP address, browser/device information, selected request headers, a first-party device identifier, a derived fingerprint, security events and service/error logs to protect accounts, prevent credit/referral abuse and investigate incidents. Fingerprint signals are investigative evidence, not an assessment of employability; security controls can automatically rate-limit or refuse requests. Cloudflare Web Analytics is supported on authentication pages for site performance measurement. This is separate from our security fingerprinting.

We also process human-confirmed integrity records: account and, where applicable, attempt identifiers; category, occurrence count, first and last occurrence and confirmation dates, status and expiry; the organisation, if any, allowed to see it; staff decision details, restricted evidence references and approval references. These support investigation, review and proportionate enforcement of mission rules. Security signals alone do not create an integrity record.

Your GA4 choice controls GA4 only. Sign-in security processing, the device security identifier and Turnstile can operate before that choice. Where enabled by our edge configuration, Cloudflare Web Analytics on authentication pages also operates separately from the GA4 choice. We use these for the security or performance purposes described here; their applicable basis and retention are separate.

The purposes and intended lawful bases under Thailand’s PDPA are set out below. A basis applies only where its legal requirements are met; acknowledging this notice is not blanket consent. Required information is marked or explained in the relevant flow. Without account, security or mission information needed to provide a requested feature, that feature may not work. Optional profile details, optional sharing and optional analytics are choices; refusing them does not itself stop ordinary account access.

Purpose Information used Lawful basis
Create, verify, secure and administer your account Email, provider identifier and verification status, age/DOB, account preferences, terms acceptance; password hash where password registration is used Contract or steps you request before entering it; legitimate interests in account security and eligibility checks
Run a mission and provide AI assistance, checks, Defense and results Conversation and tool context, commands/output, files, timestamps, submission, Defense answers and evaluation evidence Contract for the requested service; for staff/participants invited by an organisation who are not party to its contract, the relevant service relationship and legitimate interests in delivering the disclosed assessment, subject to their rights
Evaluate submitted work, improve the service and develop missions and checks Submitted work Contract and legitimate interests, subject to the person’s rights
Profile, CV assistance and selected result sharing Profile/CV and chosen result/contact fields; invitation/application and sharing choices Contract for requested features; consent where the particular optional disclosure requires it. CV transfer to AI requires the separate confirmation shown in that flow
Prevent abuse, investigate faults and maintain integrity IP/browser/device data, keyed fingerprint, access/security logs, relevant workspace and credit-effect records Legitimate interests in protecting people, service reliability and integrity, balanced against their rights; legal obligation only where a specific duty applies
Record and review human-confirmed mission-rule breaches Integrity record, restricted evidence references and human confirmation and review decisions Legitimate interests in fair assessments and preventing abuse, balanced against the person’s rights; the applicable disclosed application, assessment or organisation learning sharing basis governs disclosure to its organisation
Respond to support, appeals and rights requests Request/contact information, proportionate identity proof, relevant account/mission records and decisions Contract or legitimate interests in resolving service issues; applicable legal obligations for rights requests, claims and required records
Optional website analytics Consented public page views, restricted campaign/language fields, random analytics IDs and connection metadata Consent, withdrawable through Cookie settings
Future billing, only when offered Billing/tax contact, order and payment references/status, invoice records Contract for an actual purchase; applicable tax/accounting obligations and legitimate interests in fraud prevention

We receive data from you and your browser, the sign-in provider you choose, your use of the workspace, and organisations or people inviting you or sharing authorised information with us. We do not ask for sensitive traits to score general employability. Do not submit unnecessary health, biometric, political, religious, criminal-record or other sensitive data. If such data is genuinely necessary for a separate purpose, it needs a separate lawful arrangement; accepting these Terms does not supply it. Passwords are stored as hashes rather than readable passwords.

3. AI processing

AI features send the relevant conversation, task context, code, tool output or files through OpenRouter to the endpoint serving the selected model. The catalog includes model families from OpenAI, Anthropic, Z.ai/GLM and DeepSeek; models available in a mission depend on that mission’s selection. The model developer and the company actually serving an endpoint may differ, and fallback routing may change the serving provider. Support AI may receive the case information described above under the applicable staff access permissions.

If you choose CV autofill and confirm sending the file, the supported CV is sent through the AI gateway; review the proposed profile fields before saving. Do not put secrets or unnecessary sensitive personal information in AI messages, files or support requests. Staff are instructed not to send passwords, session credentials, keys, full payment data or national ID numbers to support AI.

We do not promise zero data retention or that every provider route prohibits model training. Ordinary routes request restricted collection, while supported exception/fallback routes can allow provider data collection. Actual retention and any training use depend on the endpoint’s terms, the route and account settings. You can ask support for the recipient information available for a particular case. Provider information: OpenRouter privacy and provider data policies. AI output and automated evaluation may be wrong; you may ask support to investigate. Human employers and schools make their own selection decisions.

4. Recipients, sharing and countries

Our control services, database and cloud sandbox hosts are hosted through OneProvider in Lille, France. Cloudflare provides the public edge, DNS, bot protection through Turnstile, R2 object storage and email forwarding. Resend processes transactional email. Google provides optional sign-in and the Gmail destination for support; GitHub receives sign-in traffic if you choose its available integration. OpenRouter and the providers serving the requested AI models process AI inputs. Ask support for the recipient and retention information available for your request. This notice does not claim that a complete vendor register or every account-specific contract has been verified. Turnstile is also covered by Cloudflare’s Turnstile Privacy Addendum.

While your account is active, you can see your own unexpired integrity records in your account and request review through Help; if it is suspended, banned or closed, ask support@operatorrank.com for them or for a review. An authorised organisation can see an active, unexpired record only for its own application, assessment or organisation learning attempt where you accepted the relevant sharing. Its projection includes the record and attempt identifiers, category, occurrence count, dates, status and expiry, but not internal evidence references, hidden checks or detection methods. Companies cannot see reversed or expired records or records from public missions completed using your own credits.

Private Practice is not automatically disclosed to recruiters. Company/school invitations, group assessments, selected job applications and voluntary public mission-link shares have their own disclosed scopes. A public mission-link share gives the selected result summary and separately chosen contact details, not blanket private file, Defense or other-result access; separately authorised hiring evidence access can still apply. Public profiles and links can be read/copied by their permitted audience. Withdrawal stops the relevant future grant, not another valid grant or copies already received. Companies/schools are responsible for their own decisions and independent copies. Staff and authorised support AI access relevant records for support/security under their permissions; that is not public or recruiter access. We may also disclose necessary information to professional advisers, authorities or courts when lawfully required or necessary to establish or defend a legal claim. Your data may be processed outside your country, including outside Thailand and outside the EU. Hosting in France does not mean every Cloudflare, email, sign-in or AI operation stays in France or Europe. Transfers requiring safeguards must use the applicable PDPA mechanism, such as an adequate destination or an applicable contractual/other lawful safeguard or exception, and the separate requirements of other law where it applies; you can request information about the safeguards applying to your data. This notice does not itself establish that a vendor contract or transfer safeguard has been executed.

4A. Optional Google Analytics 4 — when enabled

On pages where analytics is configured, we offer Google Analytics 4, with Google as an analytics processor/recipient, to understand broad acquisition, navigation and product performance and improve the website. GA4 is optional. Before Accept all, we do not load the Google analytics tag or send GA4 requests, including cookieless pings. Necessary only is equally accessible and keeps GA4 off. Accept all enables analytics only; advertising storage, advertising user data and ad personalization remain denied, and Google signals are off.

The current event helper sends only page_view on allowlisted public routes, with the language and enumerated campaign source/medium, a fixed page title, the public route template without query/fragment, and the external referrer’s origin only. It drops unknown custom parameters and does not measure private workspace, account, organisation, individual profile or token-bearing share routes. Analytics cookies use random identifiers separate from your OperatorRank account. Google also receives ordinary connection/browser metadata. We do not send names, email, account/tenant/attempt IDs, prompts, code, commands, Defense, individual scores or security fingerprints to GA4. This is not a claim that no personal data reaches Google.

Processing may take place internationally, including outside your country or the EU, under the applicable Google Analytics terms and required transfer safeguards. See Google’s data-processing terms and privacy policy; a published link is not evidence that an account-specific safeguard has been completed. The production configuration displays 2 months for GA4 user/event-level retention in Cookie settings, unless a different valid setting is configured. The actual Google property setting must match that display; this notice is not a live readback of that property. This differs from cookie lifetime; identifier retention may reset on activity if that property option is enabled, and the setting does not govern standard aggregate reports.

You can withdraw or change consent at any time through Cookie settings on the website. Withdrawal takes effect on that page, stops further GA4 collection and removes the GA4 cookies controlled by this site. It does not undo processing already lawfully performed or automatically delete Google’s existing records; contact support for the applicable supported data request. We save your choice, purpose, policy revision, time and choice source in first-party browser storage; that necessary choice record is separate from optional analytics and contains no account identifier. We use your saved choice for up to 180 days and ask again after expiry or a policy revision change. The browser record can remain until you replace it or clear site data; expiry does not itself delete the record.

4B. Payment data — only if paid plans launch

If you purchase a paid offering, we and our payment provider process the billing contact, organization and tax details required for the transaction, the order, payment status, invoice information and payment references to fulfil the purchase, administer renewal/cancellation, prevent fraud and comply with applicable tax/accounting duties. When purchases open, card payments are processed by the payment processor shown at checkout. We receive payment status, amount, the last four digits and card brand, and billing details needed for receipts and tax, but not the full card number. Applicable billing and tax records are kept for the period required by the law applying to the transaction and necessary claim handling; cancellation does not automatically erase records that must lawfully be kept. Privacy requests use the same support channel; provider-held copies require separate handling.

4C. Transfer of the service to a new operator

If we incorporate or transfer the service to a company we own or control or another successor of the service, we may transfer the related personal data and service agreements so the new operator can continue providing the service. Before the transfer, we will notify you by email or in the product, naming the new operator and its contact details; the notice will remain available in the product. The new operator will become the controller for the transferred data and the service provider. Your rights and these Terms continue unchanged, subject to mandatory law. If you do not agree, you may request account closure through Account → Data & privacy or support. We will take any additional steps required by applicable law, including obtaining consent where required and applying any required international-transfer safeguards, before the relevant transfer. Account closure and data handling remain subject to your applicable rights and lawful retention duties.

5. Retention

The following schedules distinguish live records, retained files, browser sessions and backups. Cleanup runs in batches; a period is not a guarantee of deletion at an exact second. A specific lawful hold or unresolved operation can delay eligible cleanup.

Information Schedule and limits
Account/profile and support-case information Kept while needed for the account, requested support and lawful obligations. There is no single automatic expiry for every account or support record; request deletion or review through the channels below.
Removed or rejected CV content Removed CV content becomes eligible for cleanup 30 days after removal, and rejected CV content after 7 days, subject to holds, shared references and pending privacy work. Older records without a reliable removal time receive that grace period from the recorded maintenance observation.
Temporary export files Personal-data export files become eligible for cleanup 7 days after accepted email delivery, and company export files 30 days after completion, subject to holds and unresolved dependent work. Save an authorised copy when it is available.
Rejected or abandoned upload quarantine Policy-rejected uploads and unused upload reservations may remain in restricted quarantine. Eligible bytes are cleaned up after 7 days from rejection completion or reservation expiry; unresolved outcomes and lawful holds can delay cleanup.
Server authentication material and session records Browser expiry does not immediately delete server authentication records. Eligible completed or expired authentication material is cleaned up after its 7-day grace period; expired/revoked session records have a 30-day grace period. Unresolved work, dependencies and lawful holds may require longer retention.
Raw server/browser/broker operational logs and exported log copies 90-day policy. Local storage limits may remove local journal entries earlier; daily exports provide the longer log record.
Security event/fraud signals 12 calendar months from recording, except a lawful hold. After account deletion, residual device/fingerprint or security references may remain for this period without direct account identity fields; they are not necessarily fully anonymous.
Human-confirmed integrity records Two years from confirmation, including reversed records visible to the person until expiry. Reversal removes a record from company views; expiry removes it from ordinary views and makes it eligible for periodic cleanup. Completed account erasure deletes all integrity rows, including expired rows; a copy of your data, including the copy provided before erasure, includes unexpired records confirmed by the request time. Staff approval audit records are kept separately as accountability records, and access events follow the security-event row above; neither extends the integrity record or company visibility, and after completed account erasure neither keeps a direct account identity or the decision reason.
Submission content retained for re-evaluation, including retained file/archive copies 365 elapsed days from submission, or approved privacy deletion earlier, subject to shared references, holds and completion of required cleanup. Re-evaluation cannot use expired/deleted submission content. This is not a 365-day expiry of every result or audit record.
Completed AI gateway content eligible for routine cleanup Eligible after 365 days from recording; unresolved dispatch/recovery and holds are excluded. Other workspace/attempt records have their own lifecycle and privacy-deletion handling.
Settled notification presentation and delivery content Eligible notification content after 30 days from the later relevant creation/delivery update; accepted delivery payloads generally 30 days, other settled mail payloads 90 days. Unresolved deliveries and holds remain until resolved. Minimal effect/deduplication records remain separately.
Unverified public intake Eligible after 30 days from receipt, unless the mailbox has been proved or a hold applies.
Browser sign-in sessions Expire after 30 days without use, with an absolute limit of 90 days from issue; use can refresh the idle period within the absolute limit. Earlier revocation is possible. Browser cookie lifetimes are described in the Cookie Policy.
Database backups 14-day point-in-time recovery window. An older full backup and required recovery data may remain longer to support that window; this is not a promise that every deleted row disappears from every backup on day 14.
Provider email/AI and recipient copies Their own applicable terms and lawful retention apply. We track requests and outstanding copies separately; app deletion is not proof that all provider or inbox copies have been erased.

For approved account deletion, the service exports data first and removes or blanks personal fields and deletes applicable personal content through the supported process. Some result, integrity, financial-effect and audit records can remain without direct identity fields, as needed for integrity or legal reasons. Human-confirmed integrity records are not among them: completed erasure deletes them as shown in the table above. We will identify material exceptions or outstanding external copies when responding to your request. We must preserve or reapply the request when recovering from backup; restoration is not permission to resume use of deleted data.

6. Your rights and how to use them

Depending on applicable law, you may request access or a copy, correction, portability, deletion, restriction, objection, or withdrawal of consent for processing that relies on consent, and may complain to the competent data-protection authority. Withdrawal does not invalidate earlier lawful processing. For a PDPA access/copy request we will act without delay and within 30 days where that statutory deadline applies. Other requests follow their applicable legal periods. For EU/EEA readers, GDPR rights and time limits apply only where that law applies; this notice does not claim EU representation, an EU-only processing location or universal GDPR compliance. We will verify identity proportionately, respond within the applicable legal period, and explain a lawful exception, delay or refusal.

  • To request a copy: sign in → Account → Data & privacy → A copy of your data → New request. This opens a Help request for staff to process; it is not an instant download.
  • To request account deletion: on the same page choose Request deletion, complete the email-code verification and type DELETE or ลบบัญชี. Keep the request ID. The receipt confirms submission of a request, not completed deletion. Ask Help about progress, a hold, refusal or cancellation; do not assume a self-service cancellation deadline.
  • For corrections, objections, restriction, withdrawal or a request without account access: use Help or email support@operatorrank.com, identify the account and the right you want to exercise, and include any existing request ID. Do not email a password or login code.
  • To manage sharing: use the profile/result sharing controls; contact support about recipient copies or sharing you cannot change. A company or school may need to handle its own independent copy.

7. Age, security and changes

The service is intended for people aged 18 or above. If you believe an under-18 person has supplied data, contact support for review and appropriate handling. An 18+ product rule does not replace legal-capacity requirements in your country. We use access controls, sandbox isolation and controlled storage to protect data, but cannot guarantee absolute security. Contact support about suspected misuse. We will publish changes to this policy with the effective date and provide any notice required by law.

8. Complaints, cookies and service closure

The operator at the address and support email in section 1 is the privacy contact. This notice does not assert that a statutory data protection officer has been appointed. Ask support to route a privacy concern to the responsible person. You may complain directly to Thailand’s Personal Data Protection Committee through the Office of the PDPC, or the competent authority in your jurisdiction where applicable; you do not have to finish our support process first. See the Office of the PDPC for current official complaint channels.

The Cookie Notice lists necessary sign-in/security storage, referral and preference storage, and optional GA4. Use Cookie settings to choose or withdraw optional analytics. Security/device processing is separate from analytics and has its own legitimate-interest assessment and rights; clicking Accept all is not permission for unlimited tracking.

If we plan to end the service, the Terms describe the notice and the normally 30-day pre-closure period for requesting available exports through Help or support. Closure is not an automatic transfer to public access or an immediate purge of every record. We will delete, de-identify or retain/restrict records as needed for their lawful purposes and applicable duties, explain material exceptions and outstanding processor/recipient copies, and retain a means to receive legally required rights requests. A shutdown notice does not shorten statutory rights. Corrections and results may remain only in the permitted, identity-reduced form; removing direct identity fields does not always make a record anonymous.

We publish a new revision and effective date for changes and give material-change notice as required by law. A new optional purpose requiring consent needs a separate valid choice; changing this notice alone cannot supply it. This notice describes privacy practices and rights and does not limit statutory remedies through the Terms’ liability clause.

Contact us

For questions, personal-data requests or to report a problem, email support at support@operatorrank.com