Privacy Policy
Last updated: October 19, 2026
Policy version 3.1
Who we are and how to contact us
Which laws this policy follows
What data we collect and why
Only data that the Service actually needs is collected. In practice this means:
- Account data: your email address and display name, your interface language, and the date and version of your acceptance of the Terms of Service and this policy. If you sign in with Google, the Operator receives your name and email address from Google. Purpose: creating and operating your account, signing you in, and proving acceptance of the terms.
- Uploaded screenshots and captured addresses: images you upload and web addresses you ask the Service to capture. Purpose: producing the mockups you request.
- Generated mockups: the images the Service produces for you, together with the generation settings used, so a series can be reviewed and re-run. Purpose: delivering and storing your results.
- Credit records: credit balance and movements, and each batch of credits with the date it was added and the date it expires. Purpose: running the credit model and reminding you before credits expire.
- Payment records: purchases, invoice records, and the buyer country resolved from the IP address of the request together with how it was resolved. From the payment provider's notification only the tax document reference, the amount, the currency and the internal payment reference are kept. Full card details never reach the Operator; they are entered directly with the payment provider. Records of subscriptions bought before credit packs were introduced are kept for the same purposes. Purpose: charging you correctly, issuing lawful tax documents and applying the right VAT treatment.
- Coupon redemptions: which coupon was used, by which account, and when. Purpose: honouring the discount and preventing abuse.
- Capture history: the address captured, the time, the outcome and the usage counted against your plan. Purpose: enforcing capture limits and preventing abuse.
- Support conversations and contact messages: the messages and attachments you send, and for contact-form and guest messages a hashed form of the IP address. Purpose: answering you and preventing spam.
- Marketing consent state and timestamps: whether you opted in, when, and when you withdrew. Purpose: proving that consent was given as the law requires.
- Technical logs: the application stores error records, timestamps, requested actions, hashed IP addresses and the browser user-agent; the hosting provider may process IP addresses in its own logs. Purpose: keeping the Service available, diagnosing faults, and detecting abuse and fraud.
The Operator does not intentionally collect special categories of data, and you should not upload screenshots containing them.
Legal bases under the GDPR
Each purpose rests on a specific legal basis under Article 6 of the GDPR:
- Performance of a contract, Article 6(1)(b): creating and running your account, generating mockups, capturing websites, storing your projects, and billing you for what you buy.
- Compliance with a legal obligation, Article 6(1)(c): keeping accounting and tax records, issuing invoices, retaining evidence of consent, and responding to lawful requests from authorities.
- Consent, Article 6(1)(a): marketing email and any non-essential cookie or similar storage. Consent is optional, and you can withdraw it at any time without affecting the lawfulness of processing carried out before you withdrew it.
- Legitimate interests, Article 6(1)(f): securing the Service, enforcing usage limits, preventing fraud and abuse of credits and coupons, and maintaining technical logs. The Operator balances these interests against your rights and keeps the data involved to a minimum.
Under Israeli law, the corresponding basis is your informed consent to the terms of this policy when you register and use the Service, together with the Operator's legal duties.
Cookies and local storage
The Service keeps a small amount of information in your browser. This is the full inventory of what it sets:
- Authentication session: keeps you signed in between pages and reloads. Strictly necessary.
- Theme preference: remembers light or dark mode. Strictly necessary for the interface to render as you chose.
- Language preference: remembers the locale you selected, in local storage and in a first-party cookie so the page is served in your language. Strictly necessary.
- Region cache: stores, for the browser session only, the region resolved for pricing and tax display, so it is not looked up on every page. Strictly necessary.
- Accessibility settings: stores the adjustments you make in the accessibility widget. Strictly necessary.
- Cookie consent record: stores your consent choice, the time it was given and the policy version it applies to. Strictly necessary, and required so we do not ask you again.
- Interface state: the time of your last activity, used to sign you out automatically after a period of inactivity, notices you dismissed, a coupon code you entered before checkout and the project to reopen. Strictly necessary.
Fonts are served from the Service itself, so no request is made to a third-party font service. No analytics storage and no advertising or marketing storage are in use today. If that ever changes, the categories described in the next section will be activated, the policy version will be raised, and you will be asked again before anything non-essential is set.
Your consent choice and how to change it
Sub-processors: who receives your data
Data is never sold. It is shared only with sub-processors acting on the Operator's documented instructions. This is the full list, with the purpose, the data and the processing location of each:
- OpenAI L.L.C., United States. Purpose: image generation from the screenshots you upload or capture, together with the prompt describing the scene. A data processing agreement with Standard Contractual Clauses is signed, organisation-level API call logging is disabled and every data-sharing option is switched off. Your material is not used to train OpenAI's models.
- ScreenshotOne. Purpose: rendering and capturing the websites you ask the Service to capture. Receives the address to capture and the device settings. It processes data under its data processing terms.
- Supabase, hosted on Amazon Web Services in the eu-west-2 region, London, United Kingdom. Purpose: database, authentication and file storage. Holds account data, projects, screenshots, mockups, credits and payment records.
- Morning (Green Invoice), Israel, together with its clearing partner. Purpose: payment processing and issuing tax documents and credit notes. Receives your name, email address, the amount, the currency, your country and the transaction data needed to take payment. Card details are entered directly on its secure payment page and never reach the Operator.
- Tranzila, Israel. Purpose: only payments made before the move to Morning, and refunds of those payments. Holds the transaction data of those payments. Card details were entered with it directly and never reached the Operator.
- Lovable, transactional email. Purpose: sending account, purchase, credit, reminder and support email from the notify.snapset.io address. Receives your email address and the content of the message.
- Resend, United States. Purpose: marketing email, sent only with your consent. Receives your email address, your name and the content of the message.
- Google, where you choose Google sign-in. Purpose: authentication. The Operator receives your name and email address.
- Lovable, application hosting on the Cloudflare global edge network, with points of presence in Europe and the United States. Purpose: serving the application and processing requests in transit.
- Cloudflare, global edge network. Purpose: supplying the country code derived from the IP address of your request, used only to show the correct currency and apply the correct VAT. Snapset uses no separate IP geolocation vendor.
Data may also be disclosed where the law requires it, for example to a competent authority or a court, and to professional advisers bound by confidentiality.
International transfers
How long data is kept
Retention has two parts: what the AI provider keeps, and what Snapset itself keeps.
- OpenAI: the inputs and outputs of image generation are retained by OpenAI for up to 30 days for abuse monitoring and are then deleted. Zero Data Retention is not enabled on the account, organisation-level API call logging is disabled, and the material is not used for model training.
- Source screenshots you uploaded or captured: 60 days from creation, then deleted together with the stored file.
- Generated mockups: 12 months from creation for an account that has bought a credit pack, and 90 days for an account that has not.
- Credits: purchased credits expire 12 months after purchase; free signup credits and credits granted by the Operator expire at the end of their validity, by default 3 months after they are added.
- Capture history: 12 months.
- Email delivery logs: 24 months.
- Contact-form messages: 24 months.
- Support conversations and their attachments: 24 months after the last message in the conversation.
- Error logs: 30 days.
- Accounting and tax records, including payments, invoices, credit notes and the buyer country with the basis on which it was resolved: 7 years, as required by Israeli tax and bookkeeping rules, retained detached from the account after deletion.
- Consent records, both marketing and cookie consent: for as long as the consent is relied on, and for a reasonable period afterwards as evidence that it was properly obtained.
These periods are the current settings and may be updated; this policy is amended when they change. You are emailed 30 days, 7 days and 1 day before any of your screenshots or mockups are deleted, so you can download them first. You can delete your account from the profile page at any time: your account, profile, projects, screenshots, mockups, credits, support conversations and attachments are deleted. Payment and tax records are retained for 7 years with the link to your account removed, keeping only what tax law requires.
Your rights
Under the GDPR and, in their Israeli equivalents, under sections 13 and 14 of the Privacy Protection Law as expanded by Amendment No. 13, you have the right to:
- Access the personal data held about you and receive a copy of it.
- Have inaccurate, incomplete or outdated data corrected.
- Have your data erased where there is no lawful reason to keep it.
- Restrict processing while a dispute about accuracy or lawfulness is resolved.
- Receive the data you provided in a structured, commonly used, machine-readable format, and have it transmitted to another controller where technically feasible.
- Object to processing based on legitimate interests, including profiling, and to object to direct marketing at any time.
- Withdraw any consent at any time, through the unsubscribe link in every marketing email, the cookie settings link in the footer, or by writing to us.
To exercise any of these rights, write to ejarmon.design@gmail.com. The Operator answers within one month, and will say so if that period needs to be extended for a complex request. You may also complain to the Israeli Privacy Protection Authority, or, if you are in the EU, to the supervisory authority of your country of residence, place of work, or the place where you believe an infringement occurred.
Security
Data breaches
Automated decision-making
Children
Marketing communications
Changes to this policy
This document is provided for general information and was prepared with automated assistance; it does not constitute legal advice.