Privacy Policy

Last updated: 2026-10-20

ASQ AI was formerly called AI Solve Quiz. Only the name has changed: this policy covers the same service and the same accounts.

ASQ AI ("we", "our", "us") is committed to protecting your privacy. This Privacy Policy explains what data we collect, how we use it, and your rights. By using the ASQ AI Chrome extension or website, you agree to this policy.

1. What We Collect

1.1 Account Information

When you sign in with Google, we receive and store your Google account ID, email address, display name, and profile picture URL. We also record the IP address used at sign-up for abuse prevention.

1.2 Usage Data

We log metadata about your AI explanation requests: the question type (e.g., multiple-choice), which AI model was used, token counts, response latency, and whether the request succeeded. Our audit log also retains a short, truncated copy of the answer so a repeated request can be served without charging you twice.

1.3 Saved Questions and Sessions

To provide your question history and the optional sharing feature, we save the questions you solve into sessions tied to your account. For each solved question we store the cropped question image, the answer, the explanation, the confidence score, and related metadata (subject, question type, output language, model, and timestamp). The cropped image is stored as an object in Cloudflare R2; the remaining fields are stored in our database.

These records are private to your account, with two exceptions. The first is a share link: if you create one for a session, anyone who has that link can view that session's questions, images, answers, and explanations without signing in, until you revoke the link. The second is the small, hand-picked set of de-identified question images we publish in our own marketing, described in Promotional Use of Question Images.

You can delete an individual session — or your entire account — at any time; doing so permanently removes the stored images and question content (see Account and Data Deletion). An image we have already published under section 2.1 is the one thing a deletion does not reach, because the published copy is a separate de-identified file that is no longer linked to your account. Section 2.1 explains how to have it taken down.

1.4 Screen Capture — What Leaves Your Device

ASQ AI only captures the screen region you explicitly select. That region is cropped on your device, and only the resulting image is sent to our backend — your full screen, your other tabs, and the rest of the page are never captured or transmitted. The cropped image is forwarded to Google Gemini to generate your answer and is saved to your account as described in section 1.3.

1.5 Image Generation Prompts

When you generate an image, the text prompt you write is sent to our servers and to the model that produces the picture. Prompts are screened for prohibited content before generation. We store the prompt with the resulting image record so you can see your own history and so we can act on a report.

The generated image itself is stored on your device. Our servers keep a copy only long enough to deliver it — about 48 hours — and then delete the file. After that, the copy on your phone is the only one, and deleting the app deletes it.

1.6 Billing Data

We store records of your PayPal subscription and add-on purchase transactions (amounts, dates, PayPal IDs) for billing and credit management. We do not store payment card details; all payment processing is handled by PayPal.

1.7 Credit Ledger

We maintain an audit ledger of credit transactions (grants, consumption, refunds). These records contain no question content.

1.8 Mobile Device & Advertising Identifiers

When you use the ASQ AI mobile application, Google Mobile Ads (AdMob) may collect mobile device identifiers (such as Apple's Identifier for Advertisers — IDFA, or Google's Advertising ID — GAID), IP address, coarse location data, and technical device specifications for ad delivery, frequency capping, anti-fraud, and performance metrics.

1.9 Meeting Recordings

The iPhone and iPad app can record a meeting, a lecture or a voice note; on iPhone, iPad and Android the app can also take an audio file you import (the Android app does not record). Either way it turns the audio into a transcript, a summary, a list of action items and detailed notes. In short: by default, the audio is deleted from our servers as soon as your summary is ready; the transcript and summary are kept for at most 180 days; deleting a meeting or your account deletes its audio, transcript and summary from our servers; and we do not sell any of it or use it to train AI models. The details follow.

What we collect

• The audio file you record or import.
• The meeting's title, its length and its file size.
• Once you ask for a summary: the transcript (the words, with timestamps, and in Detail mode numbered speaker labels such as "Speaker 2", never names), the language it was in, the summary and action items, and the detailed notes (the topics discussed, decisions, open questions and key facts, each with the time it was said).
• The choices made when you asked for the summary: Simple or Detail mode, the language of the summary, and whether the audio is to be kept.

How it is processed, and by whom

• Storage. The app uploads the audio to our Cloudflare R2 storage, which encrypts stored files at rest (AES-256). Nothing is transcribed until you ask for a summary.
• Transcription. When you ask for a summary, the audio is sent, through a short-lived link to our storage, to a speech-to-text provider: Groq in Simple mode, or Deepgram in Detail mode (the mode that labels speakers). It returns the transcript.
• Summary. Only the transcript text, never the audio, is sent to a large language model, which writes the summary, the action items and the detailed notes; a long meeting is read in parts. The request is first handled by our AI gateway, a service we run on our own server. The model that answers is normally Anthropic's Claude; if it is unavailable, a backup model from another provider, which may include OpenAI or Google (Gemini), may answer instead. As a last resort, for example when our own server cannot be reached, the transcript may be sent directly to Anthropic's API.
• Generate document. If you turn a meeting into a document, the document is written from the meeting itself, but never from its audio. With each message of the new document conversation, and when the document is outlined and written, the AI model is sent (in the same way as for the summary) the meeting's title, date and length, its notes (the summary, action items and detailed notes) and its timestamped transcript — as much of it as fits in about 100,000 characters, which for a longer meeting means its beginning and its end. The meeting is read from our database each time rather than copied into the conversation, so if you delete the meeting, the conversation stops reading it. Otherwise the conversation and the document are handled like any other document you write in the app.

These providers process your data to perform the service, under their own terms (see section 3). We do not sell your recordings, transcripts or summaries, and we do not use them to train AI models. Our support tools are built so that staff can see a meeting's status and billing details, but not its title, audio, transcript or summary.

How long we keep it

• By default, the audio is deleted as soon as the summary is ready. We delete the audio from our storage the moment your summary has been delivered, unless you chose to keep it. If our storage is briefly unavailable at that moment, an automatic clean-up that runs every hour finishes the job.
• Keeping the recording. In recent versions of the app you can choose to keep the recording when you ask for the summary, by unticking "Delete the recording once the summary is done". Kept recordings are deleted automatically 30 days after they were uploaded, and so is a recording you never ask us to summarise.
• If a summary attempt fails, the audio is kept so that you can try again, and is deleted on the same terms afterwards. You are not charged for a summary that fails.
• The transcript, the summary and the title are kept until you delete the meeting or your account, and are deleted automatically 180 days after the recording was uploaded in any case.
• On your phone: a recording made in the app (iPhone and iPad) is also saved in the app's own storage on your device. Deleting the app removes it from the device.

Your controls

• Delete a meeting. In recent versions of the app you can delete a meeting from its screen, except while it is still being transcribed or summarised. You can also delete your account (see section 7), or email [email protected] to have meetings deleted. Deleting a meeting deletes its audio from our storage immediately (if our storage cannot confirm the deletion, nothing is deleted and the app tells you, so you can try again), erases its transcript, summary and title, and switches off any share link.
• What is left of a deleted meeting is a record without any of its content (no audio, transcript, summary or title): whether it was recorded or imported, its length, file size and audio format, the mode, language settings and price of its summary, how its processing went (whether the summary succeeded, and how long each step took), and its dates. We keep it until 180 days after the recording was uploaded, so that charges and refunds can be checked.
• Share links. A meeting is shared only if you create a link. Anyone with the link can read its summary and transcript without signing in, and can play the recording only if audio was switched on for the link and the audio still exists. The link stops working 30 days after you last shared the meeting, or as soon as you delete the meeting or your account.
• Deleting your account deletes your meetings too; see section 7.

A recording may contain other people's voices. You are responsible for having whatever consent the law where you are requires before recording a conversation, and that obligation is yours rather than ours — we have no way to ask the other people in the room.

1.10 Document Scans

The mobile app's document scanner uses your phone's built-in scanner (Apple VisionKit on iPhone and iPad, Google's ML Kit document scanner on Android) to find and straighten each page. Scanned pages are processed and saved only on your device, in the app's own storage, together with the PDF the app makes from them. They are not uploaded to our servers, and the scanner is free. You can share, save or delete a scan from the app; deleting the app removes the scans from the device. Like other app data, scans can be included in your phone's own iCloud or Google backup if you have device backups turned on.

The one exception is a page you choose to send with Solve this page. That page goes through the normal solve flow and is handled exactly like any other question photo you solve, as described in section 1.3.

2. How We Use Your Data

• To authenticate you and manage your account.
• To process AI explanation requests and deduct the appropriate credits.
• To manage billing and subscriptions via PayPal.
• To display advertisements and support free service tiers via Google Mobile Ads (AdMob).
• To detect and prevent abuse (e.g., fraudulent credit farming).
• To monitor system health and diagnose errors via Sentry.
• To show what the service can actually handle, by publishing a small set of de-identified question images — see section 2.1.

2.1 Promotional Use of Question Images

We publish a small, hand-picked set of cropped question images on our website and in other marketing materials, to show the kinds of questions the service handles. Some of these appear on our homepage.

We publish the question image only. We never publish your answer, your explanation, your session, your email address, your display name, or any other account data, and we never attribute an image to the person who submitted it.

Before an image is published we review it and reject it if it shows a face, a handwritten name, a signature, a school letterhead, a username, or any other identifying mark. Every published file is re-encoded so that its embedded metadata is stripped, including any GPS coordinates your phone camera recorded.

Because images published this way are de-identified, they are not intended to be personal data. Where the law of your jurisdiction nonetheless treats them as personal data, we rely on our legitimate interest in demonstrating the service, and you may object at any time.

How to have a published image removed: email [email protected] with the image or a description of it. We will remove it within 30 days. You do not need to give a reason, and it will not affect your account, your credits, or your subscription.

3. Sub-Processors

We share data with the following third-party sub-processors to operate the service:

• Google — AdMob / Mobile Ads (USA): serves advertisements within our mobile applications. AdMob may collect and process device identifiers (such as Apple IDFA or Android Advertising ID), IP address, coarse location data, and ad interaction metrics to deliver personalized or non-personalized ads, perform frequency capping, prevent ad fraud, and provide analytics. See Google's Advertising Privacy Policy.
• Google — Gemini API (USA): receives the cropped screenshot image of your selected question region to generate the answer and explanation. The image is sent inline for processing. (ASQ AI separately stores the image and result for your history, as described in section 1.3.) See Google's Privacy Policy.
• Groq — Whisper speech-to-text (USA): receives the audio of a meeting you ask us to summarise in Simple mode, and returns the transcript. See Groq's Privacy Policy.
• Deepgram (USA): receives the audio of a meeting you ask us to summarise in Detail mode — the mode that labels who spoke — and returns the transcript with those labels. See Deepgram's Privacy Policy.
• Anthropic, and other AI model providers, for meeting summaries and documents (USA): receive the transcript of a meeting you summarise — the words, not the audio — to write the summary, action items and detailed notes described in section 1.9, and, if you generate a document from a meeting, its notes and transcript, to write that document. The transcript is first handled by our AI gateway, a service we run on our own server. The model that answers is normally Anthropic's Claude; if it is unavailable, a backup model from another provider, which may include OpenAI or Google (Gemini), may answer instead. As a last resort, for example when our own server cannot be reached, the transcript may be sent directly to Anthropic's API. See Anthropic's Privacy Policy.
• Cloudflare — R2 object storage (USA): stores the cropped question images for your saved sessions and shared links. Images in a shared session are accessible to anyone with the share link until you revoke it; every image we store for you here is deleted when you delete the session or your account. A de-identified copy previously published under section 2.1 is held outside R2 and is taken down on request instead. It also stores the audio of your meetings, for only as long as section 1.9 says. Cloudflare encrypts the files stored in R2 at rest (AES-256).
• Google — Sign-In (USA): provides authentication via Google OAuth 2.0. We receive your Google account ID, email, display name, and picture. See Google's Privacy Policy.
• PayPal (USA): processes all payments (PRO subscriptions and add-on packs). We share your email and transaction amounts with PayPal to initiate and manage payments. See PayPal's Privacy Policy.
• Sentry (USA): receives error and performance events from our backend for error monitoring and diagnostics. We configure Sentry to strip request bodies, question images and text, and any secrets before transmission. Error events contain no question content.

4. Data Retention

• Account data: retained until you delete your account.
• Saved sessions, questions, and their stored images: retained until you delete the session or your account, at which point the images and question content are permanently removed.
• De-identified question images published under section 2.1: retained for as long as the marketing material they appear in is published, or until you ask us to remove the image, whichever comes first. Account deletion does not by itself retract them.
• Credit ledger and payment records: retained in de-identified form even after account deletion for financial record-keeping.
• Image-generation prompts and their records: retained for 180 days, or until you delete the image from your history.
• Meeting audio: by default, deleted as soon as its summary is ready. A recording kept using the option in recent versions of the app, or never summarised, is deleted 30 days after upload. Deleting the meeting or your account deletes it immediately. See section 1.9.
• Meeting transcripts, summaries and titles: retained until you delete the meeting or your account, and in any case no longer than 180 days after upload. A record of a deleted meeting without any of its content is kept until the same 180-day limit.
• Generated image files on our servers: deleted about 48 hours after they are produced. Your device keeps the only remaining copy. The one exception is an image that has been reported: it is kept until a human has reviewed the report, because deleting it would destroy the thing we were asked to look at.
• Session tokens: expire after 30 days (refresh tokens have a 30-day rolling TTL).
• Webhook event records: automatically deleted after approximately 90 days.
• Rate-limit records: automatically deleted after each window expires.

5. Cookies and Storage

The ASQ AI Chrome extension stores your session tokens in Chrome's local extension storage (not browser cookies). The account portal (app.aisolvequiz.com) uses session storage in your browser. We do not use tracking cookies. See our Cookie Policy for more detail.

6. Your Rights and Ad Choice Preferences

Depending on your jurisdiction, you may have rights to access, correct, or delete the personal data we hold about you.

European Economic Area (EEA), UK, and Switzerland: Users in these regions are presented with a Consent Form powered by Google's User Messaging Platform (UMP) upon opening the mobile application. You can manage or revoke your ad personalization consent at any time through the in-app privacy settings.

iOS App Tracking Transparency (ATT): On iOS 14.5 and later, we request your permission before tracking or accessing your device's IDFA for personalized advertising. If you decline, you will continue to see non-personalized contextual ads.

7. Account and Data Deletion

You can delete your ASQ AI account at any time from the account portal (app.aisolvequiz.com → Account → Delete Account).

Deleting your account will automatically cancel any active PayPal PRO subscription before your data is anonymized. This prevents future billing charges. You will not be charged again after deletion. Credits already granted are not refunded; any remaining credits are lost upon deletion.

Upon deletion, we permanently remove your saved sessions, solved questions, and their stored images, and we anonymize your account: your email address, profile picture, sign-up IP, and Google account ID are cleared. A de-identified tombstone record is retained for fraud prevention. Credit ledger and payment records are retained in de-identified form.

Deleting your account deletes your meetings. Their recordings are deleted from our storage immediately (if our storage is briefly unavailable, an automatic clean-up that runs every hour finishes the job), and their transcripts, summaries, titles and share links are erased at the same time. A meeting that was still being transcribed or summarised is not completed: nothing it produces is kept. What remains of each meeting is the record without any of its content described in section 1.9 — whether it was recorded or imported, its length, file size and audio format, the mode, language settings and price of its summary, how its processing went, and its dates — linked only to the anonymized account record, so that charges and refunds can be checked. It is deleted 180 days after the recording was uploaded.

One thing deletion does not reach: a question image we had already published under section 2.1. That copy carries no link back to your account, so an account deletion cannot locate it. Email [email protected] and we will take it down within 30 days — before or after you delete your account.

If you believe your data has not been deleted within a reasonable time after a deletion request, contact us at the address below.

8. Communications

We send two kinds of email, and they follow different rules.

Account email. Sent because of something you or we just did on your account, and part of the service rather than something you opt into: verifying your email address, welcoming you once it is verified, resetting your password, telling the owner of an address that it already has an account, telling you when an administrator has adjusted your credit balance, and replying to a report you sent us about an answer. These cannot be switched off while the account exists — a password reset you are unable to receive is an account you are unable to get back into.

Product news. We may also email you occasionally about the product itself, such as a new feature. Every email of this kind carries an unsubscribe link in its footer, and supports your mail client's own "Unsubscribe" button where it offers one.

How to stop product news. Use the unsubscribe link in any such email — it needs no sign-in and does not expire — or write to [email protected] and we will do it for you. We record the request as soon as we receive it, though a message already on its way out may still arrive.

Unsubscribing from product news does not affect the account email described above, which will continue to arrive for as long as you have an account.

9. Security

All data in transit is encrypted via HTTPS. Our database uses TLS and SCRAM-SHA-256 authentication. Secrets (API keys, JWT signing keys) are managed as environment secrets and never hardcoded or logged. We do not log question text or personal identifiers beyond what is required for abuse prevention.

10. Children's Privacy

ASQ AI is not directed at children under 13. We do not knowingly collect data from children under 13.

11. Changes to This Policy

We may update this Privacy Policy from time to time. Material changes will be reflected in the "Last updated" date above. Continued use of ASQ AI after an update constitutes acceptance of the revised policy.

12. Contact

Questions about this Privacy Policy or data deletion requests may be directed to: [email protected]