Ownshop Back to the site

Privacy

Last updated 22 August 2026

What we collect, why we have it, who else sees it, and how long we keep it. Written to be read rather than to be survived.

Who is responsible

Naween Ahsan, of 150 Graydon Hall Drive, Toronto, Ontario M3A 3B1, Canada, is the data controller for the information described here. You can reach us at hello@ownshop.app.

This notice covers the builder — the service at ownshop.app and build.ownshop.app, used by creators to make and publish apps. It does not cover the apps creators publish with it. Each of those has its own privacy notice, written for that app, and the creator is the controller of whatever their app collects. If you are a visitor to somebody's app, theirs is the notice that applies to you.

What we hold about creators

WhatWhy we have it
Email address It is your account name, and it is where a password reset or a receipt has to go.
Password Stored only as a hash. We cannot read it, and a reset link is the only way back into a locked-out account.
Subscription state Your plan, its status, and the Stripe customer and subscription identifiers. This is how the service knows what you are entitled to.
Your apps The descriptions you write, the source generated from them, any reference images you upload, and the published result.
Build records What was built and when, and the model usage a build consumed. This is what your allowance is measured against, so it is also your bill.
Server logs Ordinary operational logs, kept to find faults and to notice abuse.

We never hold your card. Payment details go to Stripe and are never sent to, stored by, or visible to us. We see only that a subscription exists and what state it is in.

Why we are allowed to hold it

  • To perform our contract with you — your account, your apps, your builds, and your subscription. Without these the service cannot work.
  • Our legitimate interests — keeping the service up, finding faults, and stopping abuse of a system that runs code and takes payments.
  • Legal obligation — records we are required to keep, chiefly around tax and payments.

Cookies

One cookie, called builder_session. It keeps you signed in, is marked HttpOnly and SameSite=Lax, is sent only over HTTPS, and lasts seven days. It is strictly necessary, so there is no consent banner — refusing it would simply mean being unable to sign in.

There are no advertising cookies and no third-party trackers on this site.

Analytics on published apps

Apps published with the builder can report how many people visited, so their creator has a number to look at. That counting is deliberately built not to identify anybody:

  • No cookie is set and no identifier is stored on the visitor's device.
  • The visitor's IP address and browser string are combined with a secret salt and the current date, hashed, and truncated. The IP itself is never written down.
  • Because the date is part of the hash, the value changes every day. The same person tomorrow is a different, unlinkable number.
  • Only the page path is recorded, with the query string removed, and the event name must be one of a short fixed list.

The result counts how many people came, not who they were, and cannot be turned back into a person.

Who else processes it

We use other companies to run the service. Each sees only what its job requires.

WhoWhat forWhere
HetznerThe server running the builder, and your account and app files on itHelsinki, Finland (EU)
CloudflareServing the site and published apps, storage and backups, and protection against attackGlobal network; storage in Eastern North America
SupabaseSign-in and entitlements for apps creators publish, and the visitor counts aboveUnited States
E2BThe isolated sandbox each build runs inside. Your description and app source go there for the length of the buildUnited States
OpenRouterRoutes your description and app source to the model that writes the codeUnited States
ResendSending email — receipts, password resetsUnited States
StripeSubscription billing, and payments between creators and their own customersGlobal

What you type goes to a model. Your app description and the source of the app being changed are sent to a model provider through OpenRouter in order to build anything at all. Do not paste secrets, credentials, or other people's personal data into a build description.

We are based in Canada, and several of these providers are in the United States, so data about you crosses borders. For people in the UK or the EU: Canada holds an adequacy decision covering commercial organisations, and the UK recognises it, so data reaching us here needs no further safeguard. Where data goes on to a provider in the United States, that transfer relies on the provider's own data processing terms, which incorporate the European Commission's Standard Contractual Clauses and, for the UK, the International Data Transfer Addendum.

How long we keep it

  • Your account and apps — for as long as your account exists.
  • Backups — taken nightly and held for 30 days. Deleted data survives in backups until they age out.
  • Build and billing records — kept for six years, which is the period tax rules require.
  • Server logs — 90 days.
  • Visitor counts — kept as aggregate counts. There is nothing in them to identify.

Your rights

Wherever you live, you can ask us for a copy of your data, ask us to correct it, and ask us to delete it. If you are in the UK or the EU you can also ask us to restrict or stop a particular use, and ask for your data in a portable form. Write to hello@ownshop.app and we will answer within 30 days.

Deleting your account removes your apps and takes any you have published offline. That cannot be undone.

If you think we have handled your data badly, please tell us first — but you are entitled to complain to a regulator instead. In Canada that is the Office of the Privacy Commissioner of Canada at priv.gc.ca; in the UK, the Information Commissioner's Office at ico.org.uk; and in the EU, the authority for the country you live in.

Security

Passwords are hashed and never stored in a readable form. Traffic is encrypted, and the server that holds account data accepts connections only from Cloudflare rather than from the open internet. Each build runs in its own isolated sandbox that is destroyed when the build ends.

No system is perfect. If you find a security problem, please report it to hello@ownshop.app before disclosing it publicly, and we will work with you.

Children

The service is not for people under 18. We do not knowingly collect their data, and will delete it if we learn we have.

Changes

If we change this notice we will update the date at the top, and tell account holders by email when the change is significant.