Privacy policy

Who we are

Inkfinish is run by SAVI CLOUD TECH LLC (“we”). Questions about this policy go through our contact page.

What we keep

• Your images and renders. The image you upload, the description you type, the render we make, and the brief we wrote for the image model, with every version you make by editing a render and an overlay showing which of your sketch’s lines it kept. They are stored so you can see your history, compare, download, and render again. The area you brush for an edit is used once and not kept. If you open a 3D model, it stays on your device: only the view you pick is uploaded, as an image.
• Your listing batches. When you stage or edit a whole listing at once, we keep the listing: the photos exactly as you uploaded them, at full size, the names of their files, which job and style you picked, the label for the edited copies, whether you asked for an email, and which render each photo became, so our servers can render them after you leave and you can download the batch again later. A listing and its uploaded photos stay until you delete the listing; deleting it keeps the renders, and deleting a render leaves it out of the listing.
• Your plan, if you subscribe. The ID Stripe gives you as a customer, which plan you are on, whether it is active, and for each month you pay: the amount, the date, and any refund or dispute. Stripe takes and keeps your payment details; we never see your card number.
• Your credits. Your balance and a history of each change to it: what was added or spent, when, and for which render or month. You can see it on your billing and usage page.
• Your account, if you sign in with Google. Google gives us your name, email address, and an account ID. We keep the account ID and your email address (when Google has verified it), with when you first and last signed in and how many renders you have made. Your name stays in your sign-in cookie and is not stored. We use your email to send renders you ask for, to tell you when a listing batch is ready (only if you ticked that when you started it), to confirm your plan when it starts and when you cancel it, to find your account when you write to us, and to tell you about important changes to the service. We will not send you marketing email unless you choose to receive it.
• A guest ID, if you have not signed in. A random ID in a cookie, so your renders stay yours until you sign in. When you sign in, those renders move to your account.
• A scrambled form of your network address, for one day. To stop the free renders from being taken over and over, we count guest renders and contact messages per network each day. We store a one-way scrambled version of the address, never the address itself, and clear the counts daily.
• Messages you send us through the contact form, with the email address you give and, if you are signed in, your account ID, in our inbox.
• Review requests. When you ask for a free review of a render, we send our inbox your email address, account ID, brief, upload, and the render, so we can look at it and reply.
• Quality reviews of renders. After a render or brush edit, an automated review compares what you asked for with the brief we wrote and the render we made, and notes what we could do better. Only we see it. It is kept with the render and deleted with it.
• Checks of finished renders. Before a new render is shown, an automated check compares your upload and words with it, and if it clearly missed, it is made again at no extra cost. Meanwhile a blurred copy of the first try is kept to show you, and deleted when the render is done. The result (one sentence, and how many tries it took) is kept with the render for us to see, and deleted with it.
• Server logs. Each render’s brief and any errors are logged so we can fix problems. Our host and network provider also keep standard request logs, which include network addresses.

How we use it

• To make, store, and show your renders, and email them to you on request.
• To check whether renders give people what they asked for, and improve how we make them.
• To understand how Inkfinish is used: how many people sign up, render, and come back. These figures are seen only by us and the analytics service listed below.
• To see whether our ads on X bring visitors who go on to render, sign in, or subscribe.
• To check uploads before rendering. Inkfinish refuses photos whose main subject is a person.
• To apply the free render limits and stop abuse.
• To answer you when you write to us, and to fix problems.

We do not sell your data, show you ads on Inkfinish, or use your images, descriptions, or renders to train AI models. We use X’s pixel only to measure our own ads, not to build audiences that target you. We will not show your images or renders publicly, such as on our home page, without asking you first.

Who else receives it

We use these services to run Inkfinish. Each receives only what its job needs and handles it under its own terms and privacy policy.

• OpenAI: Makes renders and brush edits. Your uploaded image and the written brief for the render. For a brush edit, the version being edited, the area you brushed, and what you asked to change.
• Anthropic: Checks uploads before rendering, suggests follow-up questions about your brief, writes the brief for the image model, checks each finished render against what you asked for (and has it made again when it clearly misses), and reviews finished renders so we can improve them. A small copy of your uploaded image, and the description you typed. For the check of a finished render, also a small copy of the render (and, for a brush edit, of the version you edited and the area you marked). For a review, also copies of the render (and, for a brush edit, the version you edited) and the brief we wrote.
• Google: Sign-in. Your sign-in request. Google tells us your name, email address, and account ID.
• Google Analytics: Counts visits and what people do on the site, such as starting a render or signing in, so we can see what works. Advertising features are off. The pages you view, those actions, a random ID in a cookie, your browser and device type, and your approximate location. Not your images, descriptions, name, or email address.
• X (Twitter): Measures our ads on X: whether a visit came from one of our ads, and whether it led to a render, a sign-in, or a subscription. It loads only when Google Analytics would, under the same cookie choice. The page you arrive on, those actions (with the plan price for a subscription), the ID of the ad you clicked, your network address, and your browser and device type. X may connect this to your X account if you are signed in to X. Not your images, descriptions, name, or email address.
• Meta (Facebook and Instagram): Measures our ads on Facebook and Instagram: whether a visit came from one of our ads, and whether it led to a render, a sign-in, a subscription, or a contact message. It loads only when Google Analytics would, under the same cookie choice. The pages you view, those actions (with the price when you start a checkout), a random ID in a cookie, the ID of the ad you clicked, your network address, and your browser and device type. Meta may connect this to your Facebook or Instagram account if you are signed in to one. Not your images, descriptions, name, or email address.
• Stripe (and its Link service): Sells our paid plans as the merchant of record: takes payment, works out and pays sales tax or VAT, sends receipts, and handles billing support. Your email address and account ID when you subscribe, and the name, billing address, and payment details you give at checkout.
• Resend: Sends email. Your email address and the render, when you ask us to email it to you; the email saying a listing batch is ready, when you ask for it; emails about your plan (when it starts, and when you cancel it); contact form messages; and, when you ask for a free review, your email address, account ID, brief, upload, and render, sent to our inbox.
• Railway: Hosts the app and stores renders. Everything the app stores, listed above.
• Cloudflare: Delivers the site, protects it from abuse, runs the contact form's bot check, and counts page visits for us without collecting personal data. Your network address and the pages you request, as for any website.

We share data otherwise only when the law requires it, or to protect the service or its users from fraud or abuse.

Cookies

These cookies are needed for the site to work:

• Your guest ID, kept for up to a year.
• Your sign-in session, and the short-lived cookies sign-in uses for security.
• The contact form’s bot check may set its own cookie.
• Your cookie choice, so we do not ask again, kept for six months.
• While a render is being made, its ID is kept in your browser’s storage, so the studio can pick it up again if you leave and come back. It is removed when the render is done.

We also use Google Analytics cookies (_ga and _ga_ followed by an ID), kept for up to two years, to count visits. Google keeps the analytics data for up to 14 months.

And we use the X (Twitter) Pixel, an advertising cookie from X, to see which of our ads on X brought you here and whether the visit led to a render, a sign-in, or a subscription. On our site it sets _twclid, which holds the ID of the ad you clicked; X may also read its own cookies on its domains, under X’s cookie policy.

And we use the Meta Pixel, an advertising cookie from Meta, to see which of our ads on Facebook or Instagram brought you here and whether the visit led to a render, a sign-in, a subscription, or a message to us. On our site it sets _fbp, a random ID for your browser, and _fbc, which holds the ID of the ad you clicked, kept for three months; Meta may also read its own cookies on its domains, under Meta’s cookie policy. We use it only to measure our ads, not to show you ads based on your visit.

All of them follow one rule. If you are in the European Economic Area, the United Kingdom, or Switzerland, we ask first, and none loads unless you accept. Elsewhere they are on unless your browser sends the Global Privacy Control signal, which we treat as opting out. Wherever you are, you can accept or reject at any time with Cookie settings at the bottom of every page; rejecting deletes the cookies they set on our site. The site works the same either way.

How long we keep it

Your images and renders stay until you delete them, and a listing batch with its uploaded photos until you delete the listing. Your account record stays until you ask us to delete your data. Messages stay in our inbox until we no longer need them to help you. Network counts are cleared daily; daily usage totals contain no personal data. Something you delete can remain in our database backups for about five weeks until they expire; backups are only used to recover from a fault. The services listed above may keep copies for a limited time under their own terms.

Deleting your data

• Delete any render in the studio: open it and choose Delete. Its upload and every copy of the render are removed.
• To delete everything, or to get a copy of what we hold about you, send the request through our contact page from the email on your account, or while signed in. We will do it and confirm.
• You can also remove Inkfinish’s access in your Google account’s security settings.

Where it is processed

Our providers may store and process data in the United States and other countries.

Children

Inkfinish is not for children under 13, and we do not knowingly collect their data. If you believe a child has used it, tell us and we will delete their data.

Changes

We will update this page when what we collect or who receives it changes, and move the date at the top. Significant changes will also be announced on the site before they take effect.