Privacy
Privacy policy
Last updated: 4 October 2026
Quick One B.V. operates AppScreenshots.ai at appscreenshots.ai. This page describes what the product actually collects and where it goes. It is product copy, written to match the service, not a formal legal opinion.
Questions and requests go to support@appscreenshots.ai.
Who we are
The controller of personal data for this service is Quick One B.V.. We do not publish a separate privacy inbox. Use support@appscreenshots.ai.
Account data
You sign in with Google or GitHub. We store the account id, email address, name, and avatar URL that the provider returns, in our database (Supabase). A new account can create an app and generate as soon as it exists.
Uploads of app captures
When you use the product you can upload screen captures, an app icon, and text about the app (name, description, headlines). You can also paste a public App Store or Play Store URL. We then fetch the public listing and may store listing images from Apple or Google's public image hosts. Those files are saved in Supabase Storage, tied to the app on your account.
We receive the files you upload, and listing images we fetch from a public store URL you provide.
Generated images
The service sends your captures, listing text, and the headlines for a frame to an image model, then stores the resulting images so you can preview and download them. Generated files are kept in Supabase Storage with the generation run.
Image and text generation uses Google Gemini. When the deployment is configured for it, some text and image steps use xAI (Grok) instead. Those providers receive the prompts and images needed to do the job. We do not run a separate training pipeline on your uploads inside this product.
Credits and payments
Generation spends credits. Balances and credit-pack purchases are handled by RevenueCat. We do not store your card number. A profile page can open a billing management link from RevenueCat when one exists. A new account receives 60 starter credits once, the first time it is set up. That grant is recorded with an idempotency key so it is not repeated.
Collaborators
If you invite someone to an app, we store their email and send an invitation through Resend. Collaborators can view and edit that app, including uploads and generation. Generation uses the owner's credits.
Cookies
The site uses two kinds of cookies:
- Essential. Supabase session cookies keep you signed in. The product does not work as an account without them.
- Analytics. Google Analytics loads on pages of this site, including the public marketing pages. It sets analytics cookies and records pages opened, along with general browser and device data.
There is no advertising cookie and no cookie banner in the product today. You can block analytics in your browser, or with the Google Analytics opt-out add-on.
How long we keep it
Account data, uploads, and generated images stay while the account exists. If you delete the account from profile settings, we delete the login and the stored files tied to that account: app icons, uploaded captures, style previews, and generated images. Database rows tied to the user are removed with the account.
Who else processes data
- Supabase — accounts, database, and file storage.
- Google — sign-in, Gemini generation, and Analytics.
- GitHub — sign-in, if you choose it.
- xAI — generation, when that provider is configured for the deployment.
- RevenueCat — credit balances and payments.
- Resend — collaborator invitation email.
We do not sell personal information.
Your requests
You can ask for a copy of the personal data we hold, a correction, or deletion. Account deletion in the product is the direct way to remove the account and its files. For anything else, email support@appscreenshots.ai. If you are in the EEA or the UK, you can also complain to your data protection authority. For the Netherlands, that is the Autoriteit Persoonsgegevens.
Changes
If this page changes in a way that matters, we will update the date at the top. Continued use of the service after that is how you see the current version. The terms describe the service rules.
