Privacy policy

Last updated

Torsvik Labs (org. no. 937 316 704), Eliasmarken 14, 5164 Laksevåg, Norway, is responsible for the data described here. You can use Stelora without telling me who you are. Contact: hello@stelora.app.

In plain words

You don't have to tell me who you are. Upload without an email and the session is a cookie in this browser — your images hang off that, not off a name. Your IP address, or a scrambled form of it, is kept for up to 24 hours, so that one visitor can't flood the queue or use up the free images for everybody. An email, if you leave one, is how you get back to your uploads from another device and how I'd reach you about a job — leaving one after a finished image is what makes an account, and opening the link I send is what confirms it. I don't share it and I don't run a marketing list.

My server counts the steps people take, such as a file chosen or a download, and the pages it sends out; no statistics script runs in your browser. In my own database, the steps about one of your images are linked to that image. PostHog, which charts the counts for me, gets no ID that links one event to another.

An earlier version of the site kept a random number and a campaign tag in your browser; the site now removes them on your next visit.

What I store, and why

  • Your uploads and finished images — to process them and let you download them. Kept until you delete your account or ask me to delete them. I look at them only to find out why a job failed, when you ask me for help, when you have given me permission, or to check that a change to the processing does not make results worse. If you share a finished image, it is listed in the public gallery only if you tick that box, and unsharing removes it from the gallery too.
  • A session cookie — a random token that ties your uploads and free credits to this browser. Needed for the service to work.
  • Your red-light setting, only if you turn red-light mode on — your browser remembers the choice, so the next page opens red. Turning it off removes it.
  • Sign-in cookies, only if you sign in — they keep you signed in on this browser.
  • Step counts — which step of using Stelora was reached: file chosen, price shown, start pressed, out of credits, result viewed, download, buy pressed, email address left, account link sent, account created, purchase completed, credits used, image failed. My server writes each one when it handles that step; your browser sends nothing extra for it. Shares made and share pages opened are counted the same way. They go to my own database, and a copy goes to PostHog, in the EU, so I can chart them.
    • What a step holds: its name and time; the image's ID, where the step is about one image, so the steps about one image are linked to it and to each other; the price and your balance, where it is a price; the credits used and your balance before and after, when a job is charged; the error type (a fixed word such as "timeout", never a message) when an image fails; the price shown for what you pressed, on a buy press; which upgrade line led to a buy press; which form an email address came from; the email address itself, on that step only. A share step holds the share's ID and, for a share page opened, the name of the site the visitor came from.
    • What account and purchase steps add: your account ID, and for a purchase its product, amount and, for a credit pack, its credits. If you asked to save your images to an account, they can also hold the random key my server gave those images, so the link can claim them on another device. If this browser visited before 2 November 2026, they can hold the campaign tag and the site name of that earlier visit.
    • What is not collected, and what PostHog never gets: no ID for your browser, no IP address and no location. PostHog gets no account ID, no image or share ID, no key, no email address, no page address and no campaign tag. Each copy there has a new random ID of its own and no profile, so PostHog cannot link one event to another.
  • Your IP address — to stop one visitor flooding the queue or using up the free images for everybody. Two records, both deleted on a schedule:
    • When you start a session without an account, ask for a sign-in email, or leave an address on the waitlist form: the address, kept for one day, to limit how many of those one network can send in an hour.
    • For each free image processed without an account: not the address, but a one-way scrambled form of it (a hash made with a random key that changes every day), kept for 24 hours, to limit free images per network per day. This is not anonymous at first: while that day's key exists (until the end of the next day), someone with access to the database could work out the address from it. Once the key is deleted, nobody can.
  • Your email address, only if you give it — to sign you in, and to tell you when an image is ready if you ask. No marketing emails.
  • Error reports — when something breaks on the server, a report of the error (which page or endpoint, and the technical details of the failure) goes to Sentry, in the EU. No IP address, cookie or email address is sent with it. Kept for 30 days.
  • Credits and purchases — a record of every credit given and used, and, for paid plans, your Stripe customer and subscription IDs. Kept while you have an account, and as long as accounting law requires for purchases.
  • Page counts on my server — see the next section.

Page counts on my server

This is a separate count from the step counts above: it counts pages sent, not steps, and goes to PostHog only. My server counts the pages it sends out. No statistics script runs in your browser, and for this count I store nothing on your device and read nothing from it. For each page that is sent, my server sends one event to PostHog, in the EU (Frankfurt), with:

  • the address of the page, without anything after a question mark, except the campaign tags below. The ID in a shared-image address or an image page address is replaced by [id];
  • the campaign tags of the link you followed, if it has them: utm_source, utm_medium and utm_campaign, the words the person who made the link chose, such as “reddit”. A tag that holds anything other than plain words is not sent;
  • the name of the site you came from, if your browser says so (only the name, nothing else);
  • whether the page was opened by one of my own automated checks of the site, so I can leave those out;
  • that it is a page view on Stelora, and whether this is production or a test.

Each event also holds four rough labels that my server works out from what your browser sends with every page request: the kind of device (phone, tablet or computer), the browser family (for example Safari), the operating system (for example iOS) and the country, as my host Vercel works it out from your connection. They hold no version numbers, no device model and no place more exact than the country. Each event gets a new random ID, so I can't tell that two page views come from the same person. I create no profile, and I don't send your IP address, the full description your browser gives of itself, or any place more exact than the country to PostHog. Your IP address reaches my server and my host, Vercel, like it reaches any web server when you ask for a page; it is not part of the event. I count only the addresses of Stelora's pages, and only when your browser opens one as a page. Files and pages loaded ahead of time are skipped. Visits from search engines and other crawlers are counted separately: by crawler type (for example Google), by the crawler's name when it is a known one (for example Googlebot) and, for AI crawlers, by what the visit is for (training, search or a person's question). A visit that looks automated but names no crawler is counted with the reason it looked automated. I send nothing more about you. PostHog keeps the events for one year.

This count is not exact. It is made before the page is sent, so a page that turns out not to exist, or that sends you on to another page (such as your account page when you are not signed in), is still counted. Moving between pages inside the site without loading a new page is not counted. An older browser that doesn't say a page was opened as a page is counted like a crawler, with nothing more about you. The step counts listed above are a separate count, also made by my server.

The legal basis is the contract with you (running the service you asked for) and, for abuse protection and visit counts, a legitimate interest in keeping the service working.

Payments

Stripe processes payments as merchant of record and is responsible for the payment data it collects (card details, billing address, VAT). I never see your card number. See Stripe's privacy policy.

Who else handles the data

  • Supabase — database and file storage, in the EU (Stockholm)
  • Modal — image processing, in the European Economic Area or the United States
  • Vercel — website hosting and the server logs of requests
  • Resend — sending email
  • Stripe — payments
  • PostHog — counts of page views and of the steps, in the EU (Frankfurt)
  • Sentry — error reports from the server, in the EU (Frankfurt)

Vercel, Resend, Stripe, Modal, PostHog and Sentry may process data in the United States, under the EU Standard Contractual Clauses or the EU–US Data Privacy Framework.

Nothing is sold or shared with anyone else, and nothing is used for advertising.

Your rights

You can ask to see, correct, export or delete your data. Deleting your account from the account page deletes your images, your credits and your account. Step counts that carry your email address are deleted when you ask. You can complain to the Datatilsynet, the Norwegian data protection authority.