Privacy Policy

UseSketch is operated by DIGIWEB SOLUTIONS LTD, a company registered in England and Wales under company number 16726411, at Suite 6038, 128 Aldersgate Street, Barbican, London, England, EC1A 4AE.

For the purposes of UK and EU data protection law, DIGIWEB SOLUTIONS LTD is the controller of the personal data described in this policy. That means we decide what data is collected and why, and we are the company you contact about it.

This is the most important thing to understand about UseSketch, so it comes first.

Your photo is sent to Google. We do not run the image model ourselves. When you transform a photo into a style, or ask for a change in the chat editor, we send the image file and the accompanying instruction text to Google's Gemini API, to the model gemini-2.5-flash-image. Google processes the image and returns a new image, which we then store and show you.

Concretely, each request to Google contains:

• the image bytes, in their original JPEG or PNG format,
• the instruction text. For a style transform this is a fixed prompt we wrote for that style, not anything you typed. In the chat editor it is the message you typed.

We do not send your name, your email address, or your account identifier to Google with the image.

Google's processing takes place on Google's infrastructure, which is very likely to include servers outside the United Kingdom and the European Economic Area. Your use of UseSketch involves that transfer. If that is not acceptable to you, do not upload the photo.

Google's own handling of data sent to the Gemini API is governed by Google's terms and privacy documentation, not by this policy.

Do not upload photos you would not want processed by a third party. Passports, identity documents, medical images, and photographs of other people who have not agreed to it do not belong on this service.

Both the photo you upload and the image the model returns are stored in an Amazon S3 bucket in AWS region eu-north-1 (Stockholm, in the European Union). Files are keyed by your user id and the id of the generation or editor project they belong to.

We store the uploaded photo before we call the model. That means that if a generation fails, your uploaded photo has still been saved, and the failed generation stays in your history until you delete it.

Image links are plain bucket URLs and are not signed or time-limited. They are long and unguessable, but anyone you give a link to can open that image without signing in. Treat a generated image link like a shared link, not a private one.

We hold the following, and nothing beyond it.

Your account. Your email address, your name, an optional avatar image URL, a flag recording whether your email has been verified, and the dates the account was created and last updated. If you sign in with a password, we store it only as a hash. We never store or see your password in readable form.

Your sessions. When you sign in we create a session record holding a session token, its expiry, and the IP address and browser user-agent string of the sign-in. Sessions last 7 days.

Your generations. For each style transform: the style you chose, its status, the storage URLs of the input and output images, the credit cost, and, if it failed, the technical error message.

Your editor projects. Each project has a name and a chain of versions. Each version stores the text prompt you typed, its status, the storage URL of the resulting image, any note the model replied with, the credit cost, and the timestamp. Your chat prompts are stored.

Your credits. Your current balance and a transaction record for every grant, purchase and spend, including the amount, the status and a short reason. For a chat edit, that reason contains the first 120 characters of the prompt you typed.

Your payments. See Payment data below.

We do not run analytics, advertising or third-party tracking on this product, so there is no behavioural profile of you, no page-view history, and no advertising identifier.

• To run the service. Your email and password hash sign you in. Your session keeps you signed in. Your images and projects are what the product shows you.
• To produce the images you ask for. This requires sending the image and the prompt to Google, as described above.
• To bill correctly. Your credit balance and transaction history exist so that a generation charges you the right amount, and so that you can check what you were charged for.
• To operate and debug. Failure messages and server logs help us find out why a generation broke.

We do not sell your data. We do not share it with advertisers or data brokers. The only third parties that receive your data are the ones named in this policy: Google, for image processing; Amazon Web Services, for storage; and our payment gateway, for payments.

Card payments are handled entirely by an external payment gateway at checkout.secure-processor.com. You enter your card details on the gateway's page, not ours. Your card number, expiry date and security code never reach our servers and are never stored by us.

For each payment attempt we store:

• the gateway's identifiers for the transaction,
• the amount in cents and the currency,
• the status of the attempt (created, pending, successful, failed, declined),
• the raw response payload the gateway sends us, stored as JSON on the payment record.

That last point is worth being explicit about: we keep the gateway's response as it arrives, so that a payment can be reconciled or a dispute investigated later. The contents of that payload are determined by the gateway. It is not intended to contain full card details, and we do not use it as a source of card data.

UseSketch sets exactly two cookies, both strictly necessary for signing in and staying signed in. There are no analytics, advertising or tracking cookies anywhere in the product.

The names, purposes and lifetimes are listed in the Cookie Policy.

There is currently no automatic deletion of uploaded or generated images. We do not want to quote a retention period we do not enforce, so here is what actually happens: an image you upload, and an image the model produces, stay in storage until you delete the generation or project it belongs to, or until you delete your account.

The same applies to your generation history and your editor projects: they persist until you remove them.

Sessions expire on their own after 7 days. Credit and payment records are kept while your account exists, because they are the record of what you paid for.

If we later introduce automatic deletion, we will say so in this section before it takes effect.

Deleting one generation. This deletes its stored input and output files and removes the generation from your history. The credit transaction for it is kept, with its link to the deleted generation cleared, so your spending history stays complete.

Deleting an editor project. This deletes the stored image for every version in the project and removes the project and its versions. Again, the related credit transactions are kept with their links cleared.

Deleting your account. You can delete your account yourself from your account settings, confirming with your password. Deleting the account removes your user record and everything the database links to it: your sessions, your stored credentials, your credit balance, your credit transaction history, your generations, your editor projects and their versions, and your payment records.

One limitation you should know about. Account deletion removes the database records, but it does not currently sweep the image files out of storage. If you want the image files themselves gone, delete your generations and editor projects first, then delete your account. If you have already deleted your account and want the remaining files removed, contact us and we will remove them.

If you are in the UK or the EU, data protection law gives you the following rights over your personal data. We list them because they apply to you whether or not this page mentions them.

• Access. You can ask what personal data we hold about you and get a copy of it.
• Rectification. You can ask us to correct data that is wrong. Your name is editable in your account settings.
• Erasure. You can ask us to delete your data. In most cases you can do this yourself, as described above.
• Portability. You can ask for a copy of the data you gave us in a machine-readable form.
• Restriction and objection. You can ask us to stop or limit certain processing.
• Complaint. You can complain to a data protection regulator. In the UK that is the Information Commissioner's Office (ICO). In the EU it is the supervisory authority for the country you live in.

To exercise any of these, contact us. We will not charge you for a reasonable request, and we will not make you give a reason.

Two transfers are worth naming as facts. Images are stored with Amazon Web Services in the EU region eu-north-1 (Stockholm). Images and prompts are sent to Google's Gemini API for processing, and that processing is very likely to take place outside the UK and the EEA.

The legal mechanism relied on for the transfer to Google, and the safeguards that accompany it, need to be stated by a lawyer rather than asserted here.

[Pending legal review]

Rather than make broad claims, here is what is actually in place:

• Passwords are stored as hashes, never in readable form.
• Session cookies are HttpOnly and SameSite=Lax, and are marked Secure in production.
• Changing your password signs out your other sessions.
• Storage credentials are held on the server only and are never exposed to the browser.
• Payment callbacks are required to use HTTPS in production.

As noted above, stored image URLs are unguessable but not access-controlled. That is the one place where a leaked link exposes a file.

No system is perfectly secure. If you find a security problem in UseSketch, please tell us before telling anyone else.

If we change what we collect, who we send it to, or how long we keep it, we will update this page and change the effective date at the top. Material changes to how your images are processed will be described here in plain terms rather than summarised away.

For anything in this policy, including a request to access or delete your data, contact support. Our registered address is Suite 6038, 128 Aldersgate Street, Barbican, London, England, EC1A 4AE.