Skip to content

Privacy Policy

Effective October 11, 2026. Also read our Terms of Service.

The short version. We collect what we need to design your projects and prepare and ship your orders: your account details, your prompts and designs, and your shipping address when you order. Prompts are sent to AI providers to generate designs. Stripe handles card payments, so we never see card numbers. We do not sell your data, we do not use advertising trackers, and you can export or delete your data at any time.

1Who we are

Tinkerly (“we”, “us”) runs Tinkerly: a service that designs physical things from a description, shows them working in a behavior simulation, and prepares and ships orders to the people who place them. This policy covers the website, the app and every order placed through them.

Questions about this policy or your data go to hello@tinkerly.dev. A person reads every message.

2What we collect

Your account

When you sign in with Google or GitHub, we receive your name, email address and profile picture from that service. If you sign in with an emailed link instead, we receive only your email address. We do not receive or store your Google or GitHub password.

Your projects and prompts

Everything you type to design or change a project, the designs we generate in return, every saved version, and anything you add, such as uploaded documents and images, a project name, a description or comments on public projects. This includes your Build, Plan and Chat messages and the content extracted from attachments.

Your orders

The project version you ordered, the finish you chose, the price, the name and shipping address you give us, and the history of the order as we prepare and ship it.

Parts you submit

We store the specifications, product links, photos and datasheets you submit, along with revisions and review results. We preserve private copies of submitted files so reviewers can examine the same evidence. Parts are private by default. If you ask to share a part and a reviewer approves it, the reviewed catalog definition becomes public and can remain in the shared library after your account is deleted. Your uploaded review files are not published with it.

Feedback you send us

When you send feedback, we store your message and chosen category, your account identifier, the page path where you opened the form, the submission time and a request identifier used to avoid duplicate submissions. The page path excludes query parameters and URL fragments. Feedback does not automatically include screenshots or project content. Authorized staff can read it in our private feedback inbox to investigate problems and improve the service.

Payments

Payments are processed by Stripe. Your card details go straight from your browser to Stripe and we never see or store your card number. Stripe tells us whether a payment succeeded, the card brand and last four digits, and your billing details, so we can show you receipts and manage your subscription.

Your own AI key

If you add an OpenAI or Anthropic API key, we store it encrypted. See section 6.

How you use Tinkerly

We record product events in our own database, such as “project generated”, “simulation started” or “order paid”, with the time and a few details about the event. We use them to understand which parts of the product work and to fix the ones that do not. We do not use third-party advertising or tracking scripts.

Analytics and session replay

In the European Union, the European Economic Area, the United Kingdom and Switzerland, and whenever we cannot tell where you are, we ask first and collect nothing unless you choose Allow. Elsewhere this is on by default and you can turn it off on the Cookie Notice. When it is on, your browser also sends us the pages you open, what you click and type, errors it hits, page-load speed, and a replay of your visit: what appeared on screen and how the pointer moved. Passwords are always hidden, card fields are never recorded, and sign-in, checkout, billing, API key and staff pages are never recorded. Web addresses are kept without their query strings, except campaign tags. We do not store your IP address, only the country it comes from, and your browser, operating system and device type. If you are signed in, this is linked to your account. A Global Privacy Control or Do Not Track signal always counts as No thanks. This data stays with us: it is stored in our own Supabase database and storage and is not sent to PostHog or any other analytics company, even though we use their open-source library to collect it. Read the Cookie Notice for details and to change your choice.

Where you came from

We count how many visits arrive from each campaign tag (such as utm_source or ref) or referring site per day, with nothing that identifies anyone. When analytics is on, a tk_src cookie also remembers the first and the most recent source you arrived from, and if you create an account we keep those two sources with it, so we can see which channels bring people who go on to design and order things. The same rules apply as for analytics: in the EU, EEA, UK and Switzerland only after you allow it, and never with Global Privacy Control or Do Not Track.

Technical data

Like any website, our servers and hosting providers log IP addresses, browser type and request times to keep the service running and to stop abuse, such as too many requests from one place.

3How we use it

  • To sign you in and keep your projects, versions and orders attached to your account.
  • To generate and change designs when you ask us to.
  • To prepare, check and ship what you order, and to tell you how the order is going.
  • To take payment, run your subscription and keep the financial records the law requires.
  • To answer you when you write to us.
  • To keep the service safe, including rate limits, fraud checks and reviewing designs that could be dangerous.
  • To improve the product and find and fix errors, using the events, analytics and replays described above.

4AI providers

To answer questions, plan, design or change a project, we send relevant messages, the current design and attachment content to an AI model. By default we use Google and OpenAI models through the Vercel AI Gateway. If you use your own key on Pro, the request goes to OpenAI or Anthropic on that key instead.

If you request an AI draft of a part, we send the supplied details to an AI provider. Reviewers may also use AI to help read submitted specifications and file content, even when you did not request an AI draft. Staff-requested review assistance uses our platform provider. A person makes the approval decision.

We use these providers through their business APIs, whose terms say they do not train their models on that data by default. We do not use your prompts or designs to train AI models. Please do not put information in a prompt that you would not want sent to these providers.

5Who we share it with

We do not sell your personal information and we do not share it for advertising. We share only what each of these needs to do its job:

  • Supabase hosts our database, sign-in and file storage.
  • Vercel hosts the website and app and routes AI requests through its AI Gateway.
  • Google and OpenAI receive prompts, designs and part information for platform AI features. Anthropic receives that information when you choose to use your own Anthropic key on Pro.
  • Stripe processes payments and subscriptions.
  • Google and GitHub also handle sign-in if you choose those sign-in options.
  • Shipping carriers receive the name and address on an order so they can deliver it.
  • Resend delivers service emails and handles messages sent to our support inbox.

We buy parts from suppliers in our own name and do not send them your personal details. We may disclose information if the law requires it, to protect someone from harm, or as part of a sale or merger of our business, in which case this policy continues to apply to your data.

6Your own AI keys

A key you add is encrypted before it is stored, is only ever decrypted on our servers to make a request you asked for, and is never sent to your browser. After you save it, we never show it again, not even to you; we show only its last few characters so you can tell keys apart. You can delete it at any time in settings, and it is deleted with your account. If you move to Free, the encrypted key remains stored but inactive until you remove it or return to Pro.

7Public projects

New generated projects are saved privately when your plan has room. If your private-project limit is full, a generated project is saved as unlisted and the app tells you. Check its visibility before sharing sensitive content. A public project, including its name, description, design, version history and the prompts that shaped it, along with your display name and profile picture, can be seen by anyone on the internet and remixed by other Tinkerly users. An unlisted project can be seen by anyone who has its link. Making a project private again hides it from then on, but we cannot recall copies others already remixed or saved.

8Cookies

We use cookies for sign-in, security, counting community project views and remembering your analytics choice and whether your region needs it, and browser storage to keep your in-progress conversations and attachment references when you reload a tab and, when analytics is on, to hold random analytics identifiers. Stripe may use its own cookies on payment forms to prevent fraud. Read our Cookie Notice for the purposes, durations and browser controls.

9How long we keep it

  • Your account, projects and versions: for as long as your account exists.
  • Your AI key: until you delete it or your account.
  • Feedback submissions: until your account is deleted, unless we remove them sooner.
  • Private part submissions, revisions and review files: retained for review and use of your parts, and deleted when you delete your account as described below. Approved definitions you chose to share may remain in the public library without their account attribution.
  • Orders, payments and invoices: for as long as tax and accounting law requires, even after you delete your account. They are no longer linked to an account once it is deleted.
  • Product events recorded by our servers: up to 24 months, then deleted. Events stop being linked to you when you delete your account.
  • Browser analytics: events, visit summaries and error reports for 90 days, session replays for 30 days, then deleted automatically.
  • Where you came from: daily visit counts (which identify no one) for 24 months; the source kept with your account until the account is deleted.
  • Server logs: a short period, usually under 30 days, set by our hosting providers.

10Your choices and rights

Wherever you live, you can:

  • Export any of your projects as a file from the app at any time, or ask us for a copy of all the personal data we hold about you.
  • Correct your name, picture or shipping details in settings, or ask us to.
  • Delete your account in account settings, or write to hello@tinkerly.dev from the email on your account. Self-service deletion waits until any open order is delivered or cancelled. We delete it within 30 days, apart from the order records we must keep by law.
  • Object to how we use your data, or ask us to limit it.

We reply to every request within 30 days. Depending on where you live, you may also have the right to complain to your data protection authority.

Depending on the law that applies to you, you may ask for information about the categories, sources and recipients of your personal information, authorize someone to submit a request for you, or appeal a denied request by writing to hello@tinkerly.dev. We may ask you to verify your identity and an agent's authority before disclosing or deleting account data. We do not penalize you for exercising applicable privacy rights.

11Security

Data is encrypted in transit and at rest. Access to your projects is enforced in the database itself, so one account cannot read another account's private data. Only a small number of staff can see order and account details, and only to run the service. No system is perfectly secure; if a breach affects your data, we will tell you promptly.

12Children

Tinkerly is not for children under 13, and we do not knowingly collect their data. People under 18 need a parent or guardian to place orders or subscribe. Many things on Tinkerly are made for children to use; in that case the account belongs to the adult. If you believe a child under 13 has an account, write to hello@tinkerly.dev and we will delete it.

13Where data is stored

Our providers store and process data in the United States and other countries where they operate. Instant orders ship to US addresses. When data moves between countries, we rely on our providers' contractual safeguards.

14Changes to this policy

If we change this policy, we will update the date at the top. If a change materially affects how we use your data, we will tell you by email or in the app before it takes effect. The Terms of Service explain the rest of our agreement with you.

15Contact

Write to hello@tinkerly.dev with any question or request about your data.