PRIVACY POLICY
Last updated October 13, 2026
This Privacy Notice for Larp2Alt, a sole proprietorship registered in Ontario, Canada that operates OLeetle ("we," "us," or "our"), describes how and why we access, collect, store, use, and share ("process") your personal information when you use our services ("Services"), including when you:
- Visit our website at oleetle.com, or any website of ours that links to this Privacy Notice.
- Use OLeetle, a coding-practice and competitive programming service with daily challenges, friendly duels, points, AI Fluency Interviews, and optional paid subscriptions (Student and Pro).
- Contact us, for example for support or to make a privacy request.
Questions or concerns? Reading this Privacy Notice will help you understand your privacy rights and choices. We are responsible for deciding how your personal information is processed. If you do not agree with our policies and practices, please do not use our Services. If you have any questions or concerns, contact our Privacy Officer at [email protected].
SUMMARY OF KEY POINTS
This summary gives the key points of this Privacy Notice. Each topic is covered in more detail in the section linked below, and the table of contents lists every section.
What personal information do we process? The information you give us when you sign in and play (such as your email address, handle, and the code you submit), records of your games, points, and rewards, and, depending on the features you use, payment, AI Fluency Interview, GitHub, and referral information. Learn more about what information we collect.
Do we process any sensitive personal information? We do not ask for sensitive personal information. If you take an AI Fluency Interview, what you type to its AI agent is sent to AI model providers, so do not include sensitive information in it. Learn more about sensitive information.
Do we collect any information from third parties? Yes. Google shares sign-in information with our authentication provider when you sign in with Google, GitHub shares your GitHub username and account ID if you connect GitHub sync, and Stripe tells us about your subscription and payments if you subscribe.
How do we process your information? To provide, secure, and improve the Services, run duels and rewards, communicate with you, prevent cheating and fraud, and comply with law. Learn more about how we process your information.
Who do we share personal information with? The service providers listed in section 4, the AI model providers that serve interview prompts, GitHub if you connect it, other signed-in players, who can see your public profile, and anyone you send an interview report link to. We do not sell your personal information. Learn more about when and with whom we share your personal information.
Is your information processed outside Canada? Yes, mainly in the United States. Learn more about international transfers.
How do we keep your information safe? We use organizational and technical safeguards, but no system is completely secure. Learn more about how we keep your information safe.
What are your rights, and how do you exercise them? Depending on where you live, you may have rights to access, correct, or delete your personal information. You can delete your account from your settings, email [email protected], or submit a data subject access request. Learn more about your privacy rights.
TABLE OF CONTENTS
- WHAT INFORMATION DO WE COLLECT?
- HOW DO WE PROCESS YOUR INFORMATION?
- WHAT LEGAL BASES DO WE RELY ON TO PROCESS YOUR PERSONAL INFORMATION?
- WHEN AND WITH WHOM DO WE SHARE YOUR PERSONAL INFORMATION?
- IS YOUR INFORMATION PROCESSED OUTSIDE CANADA?
- HOW DO WE HANDLE YOUR GOOGLE AND GITHUB LOGINS?
- HOW LONG DO WE KEEP YOUR INFORMATION?
- HOW DO WE KEEP YOUR INFORMATION SAFE?
- WHAT ARE YOUR PRIVACY RIGHTS?
- CONTROLS FOR DO-NOT-TRACK FEATURES
- DO UNITED STATES RESIDENTS HAVE SPECIFIC PRIVACY RIGHTS?
- DO WE MAKE UPDATES TO THIS NOTICE?
- HOW CAN YOU CONTACT US ABOUT THIS NOTICE?
- HOW CAN YOU REVIEW, UPDATE, OR DELETE THE DATA WE COLLECT FROM YOU?
1. WHAT INFORMATION DO WE COLLECT?
Personal information you disclose to us
In Short: We collect the personal information you provide when you sign in, play, subscribe, use optional features, or contact us.
The personal information we collect depends on how you use the Services and which features you choose. It may include:
- Account and sign-in information: signed account identifiers and email addresses from Google sign-in, as described in section 6.
- Profile information: handles, optional avatars, and the matchmaking region you choose or we select for you.
- Consents and confirmations: your confirmation that you are at least 13, and terms acceptance (which version of our Terms you accepted and when).
- Code and submissions: the source code you submit in matches, daily challenges, and AI Fluency Interviews, a hash of each submission, and its result (verdict, hidden tests passed, and timing).
- Activity and rewards records: your matches and their results in friendly duels; duel invites and challenges; points earned and spent and the reason for each; daily-challenge submissions and solves; and your subscription plan, which affects how many points you earn.
- Support and requests: what you tell us when you contact us or make a privacy request.
Sensitive Information. We do not ask for sensitive personal information, such as information about health, racial or ethnic origin, religious beliefs, or sexual orientation, and we do not use any for any purpose. Anything you type to the AI agent in an AI Fluency Interview, or write into its workspace, is processed as described under AI Fluency Interviews below, so do not include sensitive information in it. OLeetle is not intended for children under 13, and users under 13 may not create accounts.
Payment Data. If you subscribe to a paid plan such as Student or Pro, your payment is handled by our payment processor, Stripe. Stripe collects your card or other payment details, billing name, email address, and billing address directly; we do not receive or store your full card number. We receive and keep a Stripe customer identifier and your subscription's status, plan and price, current billing period, and whether it is set to cancel, which we use to provide your subscription. Your payment history is kept by Stripe, and we can view it in our Stripe account to handle cancellations, refunds, and disputes, calculate taxes, and keep the records that tax and accounting law requires. Stripe and we keep payment records for as long as tax and accounting law requires (generally six years after the end of the tax year to which they relate), even after you delete your account. Stripe's handling of your information is described in its privacy notice at stripe.com/privacy.
AI Fluency Interviews. We do not record your screen, camera, or microphone during an interview. We keep a log of what you do in it, so that it can be scored, replayed, and shown back to you in your report: in round 1, your code as you write it (saved every few seconds) and when you run or submit it, and the test inputs you add; in round 2, the commands you run, the files you open, your edits to them as you make them and when you save, your prompts to the AI agent, the agent's replies, the tools it used and the changes it proposed, how long each proposed change and each command's output was on your screen, and which changes you accepted, rejected, or edited; text you paste into the interview, and, in round 2, whether it appears to have come from outside it; and, in round 1, the size of any paste into your code from outside the code editor, which the editor refuses. Round 2 runs in an isolated workspace with no internet access, hosted by our sandbox provider, E2B; the workspace is deleted within 24 hours after the interview ends, and at once if the interview is abandoned or fails. Your prompts, and the files and command output the agent reads, are sent to third-party AI model providers (currently through OpenRouter) to run the agent and to grade your prompts, under those providers' terms and privacy notices, and may be processed outside Canada. If you buy an interview, Stripe processes the payment (see Payment information above). The log, your scores, and your report are kept as described in section 7.
Sharing an interview report. Your report is private to you unless you make a share link for it. Anyone who has the link can see the report without signing in: your handle, the interview's difficulty and date, your scores, how each part was scored, your round 2 prompts and their grades, and a timeline of what you did, and your code only if you choose to include it. The same applies to the PDF of the report. We store only a fingerprint of the link, not the link itself. A link stops working when you turn sharing off, when you make a new link, or when you delete your account; anyone who already saved or downloaded the report keeps their copy.
GitHub Sync (Student and Pro). If you connect GitHub, we receive your GitHub username and account ID and an access token limited to GitHub's public-repository permission. We store the token encrypted and use it only to create your solutions repository and commit your own finished match solutions to the repository set in your settings. We hold the code to be committed until the commit is made. If you turn on automatic commits, we also keep a copy of each submission's code until the match is over, for no longer than 24 hours. We delete the code we hold once the commit succeeds or finally fails. Code committed to a public repository is public, under GitHub's terms, and stays on GitHub until you delete it there. You can disconnect GitHub at any time, and deleting your account also revokes the token.
Referrals. If you join through a referral link, your browser keeps the referral code until you sign up. We record which account referred you, and we check your activity on OLeetle (daily-challenge solves) to decide whether the referral vests and to pay referral points. Your referrer sees only counts of how many people joined through their link and became active, not who they are.
Information from Google sign-in
We offer sign-in with your Google account. When you use it, Google shares certain profile information with our authentication provider, as described in "HOW DO WE HANDLE YOUR GOOGLE AND GITHUB LOGINS?" below.
What other players can see
Your handle, avatar, win/loss/draw record for friendly duels, and the date you joined are publicly visible to other signed-in players in player lists, profiles, and match history. Players who join through your referral link are never shown to you by name. All personal information that you provide to us must be true, complete, and accurate, and you must tell us of any changes to it.
Information automatically collected
In Short: OLeetle automatically processes limited connection, security, and gameplay-integrity information when you use the Services.
This includes approximate region derived from connection information, short-lived hashed IP-derived security signals, server logs, and gameplay-integrity telemetry. It is used to operate matchmaking, protect the Services, and review integrity concerns. The information we collect includes:
- Log and Usage Data. OLeetle records limited operational and integrity information needed to run and secure the Services, including connection gaps and the focus, fullscreen, paste-metadata, and aggregated editor-activity signals described in this notice. We do not use this application telemetry to collect raw keystrokes. Our server logs record IP addresses, account IDs, and request details for security and troubleshooting; they are deleted automatically when our hosting provider's log retention period ends.
- Device Data. OLeetle does not independently collect hardware model, mobile carrier, device or application identifiers, or precise GPS location through the application. Our service providers may process standard connection data under their own privacy notices.
- Location Data. We infer an approximate country or region from your IP address (using the country our content-delivery network reports, or the ipapi.co lookup service) to select a matchmaking region automatically. We do not collect precise GPS location data.
Cookies and browser storage
We use strictly necessary cookies set by our authentication provider to keep you signed in, and Cloudflare may set security cookies to protect the site and run its anti-abuse checks. We do not use advertising cookies or third-party analytics.
Your browser's local storage keeps, on your device: your code drafts for each match and language, your editor settings, preferred language, and panel sizes, a cached copy of your account summary so pages load faster, any referral code you arrived with, and a copy of the code you submit in each match so it can be committed to GitHub. Your browser's session storage briefly keeps the page to return to after you sign in. This information stays in your browser until you clear it (for example by clearing this site's data in your browser settings); it is sent to us only as part of using the Services, such as when you submit code.
Complexity insights
If you have Student or Pro, complexity insights estimate your solution's time and space complexity. The estimate is worked out entirely in your browser: your code is not sent anywhere for it, and we do not store the estimate.
Google API
Our use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google Authentication is used to create and sign in to OLeetle accounts. OLeetle uses the signed account identifier and email address to authenticate the account; public profiles use the handle and optional avatar chosen in OLeetle.
2. HOW DO WE PROCESS YOUR INFORMATION?
In Short: We process your information to provide, improve, and administer our Services, communicate with you, for security and fraud prevention, and to comply with law. We may also process your information for other purposes only with your prior consent.
We process your personal information for the following purposes, depending on how you use our Services:
- To create and manage your account. We process your information so you can create and sign in to your account, keep it in working order, and show your public profile.
- To run duels and daily challenges. We create friendly duels from invite links and from challenges sent to a handle; send submitted source code for execution and judging; and maintain match records. We also process code hashes, submission outcomes, and integrity telemetry to run coding challenges and competitive play.
- To run points, referrals, and rewards. We record the points you earn and spend, track daily-challenge solves, and decide when referrals vest.
- To provide subscriptions. We provide Student and Pro benefits, handle billing, cancellations, refunds, disputes, and taxes, and keep required records.
- To provide AI Fluency Interviews, and GitHub sync when you choose to use them, as described in section 1.
- To protect the Services and review fair play. We use integrity telemetry, which includes focus and fullscreen changes, paste metadata, connection gaps, and aggregated editor activity (it does not include raw keystrokes), and security signals to prevent abuse and cheating. Moderators may review this information and derived account flags, which support human review and do not automatically ban an account.
- To communicate with you. We answer support and privacy requests, send messages about your account or subscription. We do not currently send marketing email; if we start, we will ask for your consent first and every message will let you unsubscribe.
- To comply with law and to establish, exercise, or defend legal claims.
3. WHAT LEGAL BASES DO WE RELY ON TO PROCESS YOUR INFORMATION?
In Short: We only process your personal information when we believe it is necessary and we have a valid legal reason (legal basis) to do so under applicable law, such as your consent, compliance with law, providing the Services you ask for under our contract with you, protecting your rights, or our legitimate business interests.
If you are located in the EU or UK, this section applies to you. The General Data Protection Regulation (GDPR) and UK GDPR require us to explain the valid legal bases we rely on to process your personal information. We may rely on the following:
- Consent. We may process your information if you have given us permission (consent) to use it for a specific purpose, such as connecting GitHub sync. You can withdraw your consent at any time. Learn more about withdrawing your consent.
- Performance of a Contract. We may process your personal information when it is necessary to provide the Services under our Terms, including subscriptions, and rewards, or at your request before entering into a contract with you.
- Legitimate Interests. We may process your information when it is reasonably necessary for our legitimate interests and those interests do not outweigh your interests and fundamental rights and freedoms, for example to keep the Services secure and fair, prevent fraud and cheating, and fix and improve the Services.
- Legal Obligations. We may process your information where necessary to comply with our legal obligations, such as tax and accounting rules, cooperating with a law enforcement body or regulatory agency, exercising or defending our legal rights, or disclosing information as evidence in litigation in which we are involved.
- Vital Interests. We may process your information where necessary to protect your vital interests or those of a third party, such as situations involving potential threats to the safety of any person.
If you are located in Canada, this section applies to you. We may process your information if you have given us specific permission (express consent) to use it for a specific purpose, or in situations where your permission can be inferred (implied consent). You can withdraw your consent at any time, although some features, such as GitHub sync, cannot be provided without it.
In some exceptional cases, we may be legally permitted under applicable law to process your information without your consent, including, for example:
- If collection is clearly in the interests of an individual and consent cannot be obtained in a timely way
- For investigations and fraud detection and prevention
- For business transactions provided certain conditions are met
- If it is contained in a witness statement and the collection is necessary to assess, process, or settle an insurance claim
- For identifying injured, ill, or deceased persons and communicating with next of kin
- If we have reasonable grounds to believe an individual has been, is, or may be victim of financial abuse
- If it is reasonable to expect collection and use with consent would compromise the availability or the accuracy of the information and the collection is reasonable for purposes related to investigating a breach of an agreement or a contravention of the laws of Canada or a province
- If disclosure is required to comply with a subpoena, warrant, court order, or rules of the court relating to the production of records
- If it was produced by an individual in the course of their employment, business, or profession and the collection is consistent with the purposes for which the information was produced
- If the collection is solely for journalistic, artistic, or literary purposes
- If the information is publicly available and is specified by the regulations
4. WHEN AND WITH WHOM DO WE SHARE YOUR PERSONAL INFORMATION?
In Short: We share information with the service providers that run OLeetle for us, with the third parties you choose to connect, with other players as part of your public profile, and in the specific situations described in this section.
- Service Providers. We disclose personal information to service providers that process information on our behalf as necessary to host, maintain, secure, and operate OLeetle. Depending on configuration and the features you use, these providers include Supabase for authentication, database, and file storage (avatars); Railway for application hosting (our website, API, background worker, and cache); DigitalOcean for the server that runs Piston, our self-hosted code-execution service; Cloudflare for DNS, content delivery, and security filtering of traffic to our websites, and Cloudflare Turnstile for anti-abuse checks; ipapi.co for IP-to-country lookup; Stripe for payment processing, subscription billing, and tax calculation; E2B for the isolated workspaces that run round 2 of AI Fluency Interviews; OpenRouter, which passes AI Fluency Interview prompts to the AI model providers that serve the chosen model; and Termly for our privacy request form. Submitted source code is sent to our Piston execution server for judging.
- Third Parties You Choose to Use. When you connect GitHub sync, GitHub processes your authorization and the commits we make for you. These companies process that information under their own terms and privacy notices.
- Other Players. Other signed-in players can see the information described in "What other players can see" in section 1.
- People You Share a Report With. If you make a share link for an AI Fluency Interview report, anyone who has the link can see that report, as described in "Sharing an interview report" in section 1.
- Business Transfers. We may share or transfer your information in connection with, or during negotiations of, any merger, sale of business assets, financing, or acquisition of all or part of our business.
- Legal Requirements. We may disclose information where required by law or legal process, or where necessary to protect the rights, safety, or property of our users, the public, or OLeetle.
We do not sell your personal information, and we do not share it for targeted advertising.
5. IS YOUR INFORMATION PROCESSED OUTSIDE CANADA?
In Short: Yes. We are based in Ontario, Canada, but most of our service providers store and process information in the United States.
Our service providers store and process personal information outside Canada, mainly in the United States (for example, our database is hosted in Oregon and our code-execution server in Kansas City), and in other countries where they or the AI model providers operate. While your information is outside Canada, it is subject to the laws of those countries and may be accessible to their courts, law enforcement, and national security authorities. We use contracts with our service providers to protect the information they process for us.
6. HOW DO WE HANDLE YOUR GOOGLE AND GITHUB LOGINS?
In Short: If you sign in with Google or connect GitHub, we receive certain information about you from that service.
Google. When you sign in with Google, Google shares your signed account identifier and email address, whether the email is verified, your name, and your profile picture with our authentication provider, Supabase. We use the signed account identifier and email address to authenticate your account. Your Google picture is shown only to you, on your profile page, until you choose an avatar; it is never used on your public profile, and we do not use your Google name.
GitHub. If you connect GitHub sync, GitHub shares your GitHub username and account ID with us and gives us an access token with the permission you approve on GitHub's authorization page, as described in section 1.
We use the information we receive only for the purposes described in this Privacy Notice or otherwise made clear to you in the Services. We do not control, and are not responsible for, other uses of your personal information by Google or GitHub. Please review their privacy notices to understand how they collect, use, and share your personal information and how you can set your privacy preferences with them.
7. HOW LONG DO WE KEEP YOUR INFORMATION?
In Short: We keep your information for as long as necessary for the purposes described in this Privacy Notice, unless the law requires or permits a longer period.
We keep personal information only for as long as it is needed for the purposes in this Privacy Notice, unless a longer retention period is required or permitted by law (such as tax, accounting, or other legal requirements). In particular:
- Submitted source code is cleared by scheduled retention cleanup after completed judging or invalid processing, and daily-challenge code once it has been judged. Public-run source code and results are cleared after the run completes, fails, or expires, and "run examples" output from daily challenges after 24 hours. The exceptions are code held for GitHub sync (described in section 1) and code you submit or write in an AI Fluency Interview, which is kept with that interview's record (below).
- Raw integrity telemetry is deleted after seven days, and operational audit events after 90 days.
- An AI Fluency Interview's round 2 workspace is deleted within 24 hours after the interview ends, and at once if it is abandoned or fails. The interview's log (described in section 1), scores, and report are kept while your account exists so that you can see your report and history and, after you delete your account, for as long as needed for accounting, fraud prevention, and to resolve disputes.
- Legacy balance-adjustment records are retained for accounting and fraud prevention. Personal delivery email addresses are removed when you delete your account.
- Your GitHub token, username, account ID, and repository are kept until you disconnect GitHub or delete your account.
- Account, match, points, daily-challenge, referral, and derived integrity-flag records are retained while the account is retained, subject to deletion requests and legal, security, or fraud-prevention needs; see section 9 for what happens when you delete your account.
- Payment records are kept as described under Payment Data in section 1.
When we have no ongoing legitimate business need to process your personal information, we either delete or anonymize it, or, if this is not possible (for example, because it is stored in backup archives), we securely store it and isolate it from any further processing until deletion is possible.
8. HOW DO WE KEEP YOUR INFORMATION SAFE?
In Short: We aim to protect your personal information through organizational and technical security measures.
We have implemented appropriate and reasonable technical and organizational security measures designed to protect the personal information we process. For example, we redact submitted code, authentication tokens, and cookies from application logs; we store GitHub tokens encrypted; we run AI Fluency Interview workspaces in isolated sandboxes with no internet access. However, no electronic transmission over the Internet or information storage technology can be guaranteed to be 100% secure, so we cannot promise or guarantee that hackers, cybercriminals, or other unauthorized third parties will not be able to defeat our security and improperly collect, access, steal, or modify your information. Transmission of personal information to and from our Services is at your own risk, and you should only access the Services within a secure environment.
9. WHAT ARE YOUR PRIVACY RIGHTS?
In Short: Depending on where you live, including Canada, the European Economic Area (EEA), the United Kingdom (UK), Switzerland, and some US states, you have rights that give you greater access to and control over your personal information. You can review and change your profile, or delete your account, at any time.
Depending on applicable law, you may have the right (i) to request access to and obtain a copy of your personal information, (ii) to request correction or deletion; (iii) to restrict the processing of your personal information; (iv) if applicable, to data portability; and (v) not to be subject to automated decision-making. If a decision that produces legal or similarly significant effects is made solely by automated means, we will inform you, explain the main factors, and offer a simple way to request human review. In certain circumstances, you may also have the right to object to the processing of your personal information. You can make a request by using the contact details in "HOW CAN YOU CONTACT US ABOUT THIS NOTICE?" below. We respond to requests to access or correct your personal information within 30 days, and we will consider and act on every request in accordance with applicable data protection laws.
Complaints. If you are not satisfied with how we have handled your personal information, please contact our Privacy Officer first (section 13). We will acknowledge your complaint within 30 days of receiving it, investigate without unjustifiable or excessive delay, keep you informed of progress, and explain the outcome. You also have the right to complain to a regulator:
- In Canada, the Office of the Privacy Commissioner of Canada (priv.gc.ca), or, if you live in Quebec, the Commission d'accès à l'information du Québec.
- In the UK, the Information Commissioner's Office (ico.org.uk/make-a-complaint, helpline 0303 123 1113).
- In the EEA, your Member State data protection authority.
- In Switzerland, the Federal Data Protection and Information Commissioner.
Withdrawing your consent: If we rely on your consent to process your personal information, which may be express or implied consent depending on the applicable law, you can withdraw it at any time by contacting us using the details in "HOW CAN YOU CONTACT US ABOUT THIS NOTICE?" below. This does not affect the lawfulness of processing before the withdrawal, nor, where applicable law allows, processing that relies on lawful grounds other than consent.
Account Information
You can review and change your handle, avatar, and region in your OLeetle settings, and you can delete your account there at any time using the delete my account option.
Deleting your account deletes your sign-in record (including your email address and Google link) and your avatar; removes your handle, region, your Terms and age confirmations, legacy residence confirmations and delivery email addresses; disconnects GitHub sync and revokes its access; turns off any AI Fluency Interview report links you made; and cancels any subscription. Records of matches, points, and integrity reviews are kept, linked only to an internal account number and shown to other players as an anonymous player, because other players' results depend on them. Legacy balance adjustments and AI Fluency Interview records (such as interview purchases, status, scores, and the interview log) are kept without those email addresses, for accounting and fraud prevention as described in section 7. We and Stripe keep billing records for as long as tax law requires, and we may keep limited records to prevent fraud, troubleshoot problems, assist with investigations, enforce our Terms, or comply with legal requirements. Code you committed to GitHub stays in your GitHub repository until you delete it there.
If you have questions or comments about your privacy rights, you may email us at [email protected].
10. CONTROLS FOR DO-NOT-TRACK FEATURES
Most web browsers and some mobile operating systems and mobile applications include a Do-Not-Track ("DNT") feature or setting you can activate to signal your privacy preference not to have data about your online browsing activities monitored and collected. No uniform technology standard for recognizing and implementing DNT signals has been finalized, so we do not currently respond to DNT browser signals or any other mechanism that automatically communicates your choice not to be tracked online. We do not track you across other websites, and we use no advertising or third-party analytics cookies. If a standard for online tracking is adopted that we must follow in the future, we will describe it in a revised version of this Privacy Notice.
California law requires us to let you know how we respond to web browser DNT signals. Because there currently is not an industry or legal standard for recognizing or honoring DNT signals, we do not respond to them at this time.
11. DO UNITED STATES RESIDENTS HAVE SPECIFIC PRIVACY RIGHTS?
In Short: If you are a resident of California, Colorado, Connecticut, Delaware, Florida, Indiana, Iowa, Kentucky, Maryland, Minnesota, Montana, Nebraska, New Hampshire, New Jersey, Oregon, Rhode Island, Tennessee, Texas, Utah, or Virginia, you may have the right to request access to and receive details about the personal information we maintain about you and how we have processed it, correct inaccuracies, get a copy of, or delete your personal information. You may also have the right to withdraw your consent to our processing of your personal information. These rights may be limited in some circumstances by applicable law. More information is provided below.
Categories of Personal Information We Collect
The table below shows the categories of personal information we have collected in the past twelve (12) months. For a full description of the personal information we process, see "WHAT INFORMATION DO WE COLLECT?"
| Category | Examples | Collected |
|---|---|---|
| A. Identifiers | Email address, signed account identifier, handle, internal account ID, GitHub username and account ID, Stripe customer identifier, IP address | YES |
| B. Personal information as defined in the California Customer Records statute | Name and email address (your name only as shared by Google with our authentication provider) | YES |
| C. Protected classification characteristics under state or federal law | Gender, age, date of birth, race and ethnicity, national origin, marital status, and other demographic data (we record only your confirmation that you are at least 13 ) | NO |
| D. Commercial information | Subscription plan, price, status, and billing period (your payment history is kept by Stripe) | YES (subscribers only; card details are held by Stripe, not by us) |
| E. Biometric information | Fingerprints and voiceprints | NO |
| F. Internet or other similar network activity | Interactions with our Services, including gameplay-integrity telemetry and server logs | YES |
| G. Geolocation data | Approximate country or region derived from your IP address | YES |
| H. Audio, electronic, sensory, or similar information | Avatar images you upload | YES |
| I. Professional or employment-related information | Business contact details, job title, work history, and professional qualifications | NO |
| J. Education Information | Student records and directory information | NO |
| K. Inferences drawn from collected personal information | Integrity flags derived from gameplay and editor telemetry, used for fair-play review | YES |
| L. Sensitive personal information | We do not collect sensitive personal information on purpose | NO |
We may also collect other personal information outside of these categories when you interact with us online or by email or mail in the context of receiving help through our support channels and our responses to your inquiries.
We will use and retain the collected personal information as needed to provide the Services or for:
- Category A, B, D, F, H, K - While the account is retained, subject to deletion requests and legal, security, or fraud-prevention needs, and to the specific periods in section 7.
- Category F - Raw integrity telemetry is deleted after seven days; operational audit events are deleted after 90 days; submitted source code is cleared after completed judging, invalid processing, or public-run completion, failure, or expiry, except code held for GitHub sync or an AI Fluency Interview as described in section 7.
- Category G - Retained only as needed to provide matchmaking and protect the Services, subject to the applicable retention criteria above.
Sources of Personal Information
Learn more about the sources of personal information we collect in "WHAT INFORMATION DO WE COLLECT?"
How We Use and Share Personal Information
Learn more about how we use your personal information in "HOW DO WE PROCESS YOUR INFORMATION?"
Will your information be shared with anyone else? We may disclose your personal information to our service providers under a written contract between us and each service provider. Learn more in "WHEN AND WITH WHOM DO WE SHARE YOUR PERSONAL INFORMATION?"
We may use your personal information for our own business purposes, such as internal research to improve the Services. This is not considered to be "selling" your personal information. We have not sold any personal information to third parties, or shared it for cross-context behavioral advertising, in the preceding twelve (12) months, and we will not sell personal information belonging to website visitors, users, and other consumers in the future.
Your Rights
You have rights under certain US state data protection laws. These rights are not absolute, and in certain cases we may decline your request as permitted by law. These rights include:
- Right to know whether or not we are processing your personal data
- Right to access your personal data
- Right to correct inaccuracies in your personal data
- Right to request the deletion of your personal data
- Right to obtain a copy of the personal data you previously shared with us
- Right to non-discrimination for exercising your rights
- Right to opt out of the processing of your personal data if it is used for targeted advertising (or sharing as defined under California's privacy law), the sale of personal data, or profiling in furtherance of decisions that produce legal or similarly significant effects ("profiling")
Depending on the state where you live, you may also have the following rights:
- Right to access the categories of personal data being processed (as permitted by applicable law, including the privacy law in Minnesota)
- Right to obtain a list of the categories of third parties to which we have disclosed personal data (as permitted by applicable law, including the privacy law in California, Delaware, and Maryland)
- Right to obtain a list of specific third parties to which we have disclosed personal data (as permitted by applicable law, including the privacy law in Minnesota and Oregon)
- Right to obtain a list of third parties to which we have sold personal data (as permitted by applicable law, including the privacy law in Connecticut)
- Right to review, understand, question, and depending on where you live, correct how personal data has been profiled (as permitted by applicable law, including the privacy law in Connecticut and Minnesota)
- Right to limit use and disclosure of sensitive personal data (as permitted by applicable law, including the privacy law in California)
- Right to opt out of the collection of sensitive data and personal data collected through the operation of a voice or facial recognition feature (as permitted by applicable law, including the privacy law in Florida)
How to Exercise Your Rights
To exercise these rights, you can submit a data subject access request, email us at [email protected], or use the other contact details in section 13.
Under certain US state data protection laws, you can designate an authorized agent to make a request on your behalf. We may deny a request from an authorized agent that does not submit proof that they have been validly authorized to act on your behalf in accordance with applicable laws.
Request Verification
When we receive your request, we will need to verify your identity to confirm that you are the person about whom we hold the information. We will only use personal information provided in your request to verify your identity or authority to make the request. If we cannot verify your identity from the information we already hold, we may ask you for additional information for verification and for security or fraud-prevention purposes. If you submit the request through an authorized agent, we may need to collect additional information to verify your identity before processing your request, and the agent will need to provide written and signed permission from you to submit the request on your behalf.
Appeals
Under certain US state data protection laws, if we decline to take action on your request, you may appeal our decision by emailing us at [email protected]. We will inform you in writing of any action taken or not taken in response to the appeal, including a written explanation of the reasons for the decision. If your appeal is denied, you may submit a complaint to your state attorney general.
California "Shine The Light" Law
California Civil Code Section 1798.83, also known as the "Shine The Light" law, permits our users who are California residents to request and obtain from us, once a year and free of charge, information about categories of personal information (if any) we disclosed to third parties for direct marketing purposes and the names and addresses of all third parties with which we shared personal information in the immediately preceding calendar year. We do not disclose personal information to third parties for their direct marketing. If you are a California resident and would like to make such a request, please submit it in writing using the contact details in "HOW CAN YOU CONTACT US ABOUT THIS NOTICE?"
12. DO WE MAKE UPDATES TO THIS NOTICE?
In Short: Yes, we will update this notice as necessary to stay compliant with relevant laws and to describe what OLeetle does.
We may update this Privacy Notice from time to time. The updated version will be indicated by an updated "Last updated" date at the top of this Privacy Notice. If we make material changes, we will notify you either by prominently posting a notice of the changes or by sending you a notification directly. We encourage you to review this Privacy Notice regularly.
13. HOW CAN YOU CONTACT US ABOUT THIS NOTICE?
Our Privacy Officer is accountable for our compliance with this Privacy Notice and receives complaints and inquiries. You can reach the Privacy Officer, Larp2Alt (OLeetle), by email at [email protected], by phone at +1 289-809-6923, or by mail at: Privacy Officer, Larp2Alt (OLeetle), 145 1/2 Church Street, Unit 5, Office 945, Toronto, ON M5B 1Y4, Canada.
14. HOW CAN YOU REVIEW, UPDATE, OR DELETE THE DATA WE COLLECT FROM YOU?
You have the right to request access to the personal information we collect from you, details about how we have processed it, or correction of inaccuracies. You can change your profile in your account settings, and you can delete your personal information by deleting your OLeetle account in your account settings, with the effects described in section 9. You may also have the right to withdraw your consent to our processing of your personal information. These rights may be limited in some circumstances by applicable law. For any other request to review, update, or delete your personal information, email [email protected] or submit a data subject access request.