Privacy Policy

#1. Information we process

• Account. With Google sign-in we receive an account identifier, email address and basic profile details such as name and picture. We get no Google password and no access to Gmail, Drive, Classroom files or Google browsing history. You can also register with an email and password; Supabase processes those credentials and sends confirmation and password-reset emails. Passwords are not stored in browser storage or sent to AI services.
• Study content. When you request analysis, GrindMate reads the relevant visible question text, answer choices, instructions and illustrations, including accessible embedded activities. A question may itself contain personal information, so avoid submitting anything sensitive or confidential.
• Images. Chrome may capture the active tab locally to read a question illustration. GrindMate crops it to the question area, and only that crop is uploaded; the full capture never is. Your initial consent to AI question sharing also covers image questions, so no separate approval is asked during scans.
• Service records. Account and subscription details, plan status, usage counts, questions and AI responses, request identifiers, timestamps and errors. Providers may process IP addresses and connection data for delivery and security.
• Browser data. Local preferences, sign-in tokens, cached answers and plan status.
• Withdrawal form. Name, contact email, contract description, request identifier and receipt time (see section 6).
• Support. Whatever you choose to send us.

#2. When the extension reads a page

Content scripts load on permitted pages to add GrindMate's controls and track page state. Turning GrindMate ON does not send pages to AI services; analysis starts only when you request it. Turning it OFF stops page assistance and cancels active analysis, although a request already submitted may finish. Sign-in, session refresh and plan checks are separate and may continue. You can also sign out, restrict site access in Chrome or uninstall the extension.

#3. Browser permissions

The extension requests storage, alarms, identity, scripting, activeTab and host access to <all_urls>. Host access and scripting let it help with questions and embedded activities on the sites you use. Host access and activeTab identify the active study tab, capture question images locally and show results on the right page. Storage keeps preferences and service state, identity enables Google sign-in, and alarms run periodic plan checks. Permissions are not used for unrelated collection; restricting site access in Chrome may limit features.

#4. Why we use it and on what legal basis

• Providing the service (performance of our contract with you): sign-in, Free or Pro access, analyzing the content you request, showing answers, recovering interrupted requests, usage limits, subscription administration and support.
• Security and abuse prevention (legitimate interests): fraud and abuse detection and diagnosing failures.
• Legal obligations: tax, accounting and consumer-law records.
• Consent, where we ask for it, such as AI question sharing. You can withdraw consent at any time without affecting earlier processing.

We do not sell user data, share it for advertising, build advertising profiles or use it for creditworthiness or lending decisions.

#5. Who processes your data

• Google and Supabase: sign-in; Supabase also hosts account data and the AI service. Google · Supabase
• Cloudflare Workers AI, Groq and OpenRouter: answer requested study content. OpenRouter may forward it to downstream providers, including Chutes, and the company running a model can differ from its developer (such as NVIDIA or Google). Cloudflare · Groq · OpenRouter · OpenRouter provider logging
• Stripe: Pro payments and billing details. Stripe
• Resend: account and withdrawal emails (recipient address, message content and delivery records). Resend
• Cloudflare Turnstile: spam protection on the withdrawal form.

AI requests contain the study content and technical identifiers, not your profile, email or credentials. AI providers may retain or use content under their own terms and settings; our promise not to train our own models does not mean every provider works the same way. We may also disclose information where the law requires, or to prevent fraud or protect security. A transfer as part of a business sale requires the prior consent required by Chrome Web Store rules.

#6. How long we keep it

• In your browser. Page-assistance data is cleared when its page context is reset, disabled or closed. Preferences stay until you change them. Sign-in tokens are kept in the extension's own local storage (IndexedDB) so you stay signed in after a browser restart; signing out removes them. Prepared answers stay usable for up to 15 minutes, and request identifiers for up to 24 hours to recover interrupted requests. Server-verified Pro access lasts at most one hour per browser session, or less at subscription end or sign-out; a local plan-display hint may remain for up to seven days but cannot grant Pro access. Uninstalling removes browser data but not server records.
• Answer recovery on our server. Available for 24 hours after a request. Older saved answers are cleared when a later request is made, so an answer can remain longer if you make no further requests. Request identifiers, fingerprints and usage metadata are kept separately to prevent duplicate processing, reconcile usage and investigate failures.
• Accounts and subscriptions. Kept while in use. After a verified deletion request we delete or anonymize account, usage and request records, except those needed for a pending refund, dispute or documented abuse case, which are kept until it is resolved and the claim period has ended.
• Payments. Kept for the statutory tax and accounting period, even if you delete your account.
• Support and withdrawal notices. Kept while the matter is open and while needed for a related legal claim. Withdrawal notices are never used for marketing.
• Provider copies. Hosting logs, delivery records, backups and AI-provider logs follow each provider's own retention; our 24-hour recovery window does not set theirs.

There is no automatic server-wide deletion schedule beyond what is described here. Ask us for the retention basis of a particular record.

#7. Security and transfers outside the EU

We use HTTPS, access controls and restricted authentication storage, but no system is completely secure. Our providers may process data outside the European Economic Area under contractual and other legal safeguards; contact us for details. Do not submit passwords, payment details, health information or confidential school records for analysis.

#8. Your rights

You can request access to, correction, export, deletion or restriction of your data, and object to processing based on legitimate interests. Email us; we may verify your identity first and will respond within the legal time limit. Some records must be kept for legal, security or dispute reasons. Account deletion does not cancel a subscription: tell us if you want both. You may also complain to a data-protection authority; in Finland this is the Data Protection Ombudsman.

#9. Children

GrindMate is not directed to children under 13 or below the age at which they can consent on their own where they live. Contact us if you believe a child has given us personal data.

#10. Chrome Web Store Limited Use

GrindMate's use of user data complies with the Chrome Web Store User Data Policy, including its Limited Use requirements, and information received from Google APIs is subject to the same restrictions. Data is used only to provide or improve the disclosed study-assistance features and for necessary account, reliability and security operations. We do not sell it or transfer it to advertisers or data brokers. People read user data only with your explicit consent, in aggregated and anonymized form for internal operations, for security investigations or to comply with the law.

#11. Changes

We update the date above when this policy changes. Material changes that require notice or consent are presented before the new processing starts.

#12. Data controller and contact

Use this address for privacy questions, data requests and support.