What we keep, why, and who else sees it.

MonkeySee Inc. (“we”, “us”), based in San Francisco, California, owns and operates Unsure, including the marketing site at unsure.dev, the application at app.unsure.dev, the public API, and the unsure_client and @unsure.dev/client SDKs. We are the data controller for the personal data described here. You can reach us at hello@unsure.dev.

We collect three kinds of data: what you tell us about yourself, what you send through the product, and what your device sends along the way.

We do not run advertising trackers or third-party analytics on unsure.dev or app.unsure.dev.

Content is the product. Unsure exists to record every decision with what the model was and was not sure about, so the least certain ones can be reviewed and a new prompt can be replayed against the corrected set. We store prompts, outputs, answers and corrections because the review queue and replay read them. We use your data to:

• Provide the service: make decisions, run pipelines, queue and record reviews, replay prompts, and show you the history.
• Bill you: meter usage, apply purchases and starter credit, and stop requests when the balance is exhausted.
• Keep accounts safe: authenticate sessions and keys, throttle sign-in attempts, and investigate abuse.
• Support you: answer questions and diagnose problems, which may mean looking at the specific decisions you ask about.
• Operate the service: monitor errors, capacity and latency in aggregate.

We do not use your content to train models. We do not sell personal data, and we do not share it with anyone for their own marketing.

Providing Unsure means sending some of your data to a small number of companies that do a specific job for us. Each receives only what its job needs.

Each provider is bound by its own terms and privacy policy. We choose the encoder and decoder catalog, but you choose which model a pipeline step uses, and that model's provider sees the content routed to it.

The application sets one cookie, access_key, when you sign in with a password. It holds a signed session token, is marked HttpOnly and SameSite=Lax, and is Secure in production. It exists so you stay signed in; it is not used to track you across sites. API clients authenticate with a Bearer key and receive no cookie. The marketing site sets no cookies.

• Content is kept for as long as your workspace exists. Decisions, corrections and replay results are the history that replay scores against, so we do not expire them on a schedule.
• Account data is kept while the account is open and deleted when the account is deleted, except for records we must keep for tax or accounting.
• Billing records are kept for as long as the law requires, typically seven years.
• Server logs are rotated within 30 days.
• Backups may hold deleted data for up to 30 days after deletion before they are overwritten.

You can see and change your name, password and API keys on the Account page. For anything else, email us and we will:

• Give you a copy of the personal data and content we hold for your account.
• Correct anything that is wrong.
• Delete your account and its content, subject to the retention rules above.
• Tell you which providers have received your data.

We answer within 30 days. If you are in the European Economic Area, the United Kingdom or another jurisdiction with data protection law, you also have the right to object to or restrict certain processing and to complain to your supervisory authority. Our legal basis for processing is performance of our contract with you, our legitimate interest in running a secure and reliable service, and where required, your consent.

Passwords are stored as bcrypt hashes. API key secrets are shown once and stored as keyed hashes; a lost key is replaced, not recovered. All traffic to app.unsure.dev is over TLS. Sessions are signed and cookie-authenticated writes require a same-origin request or a CSRF header. Provider credentials live in a secrets manager and are never sent to browsers. No system is perfect; if we learn of a breach affecting your data we will tell you without undue delay.

Our servers are in the United States. If you use Unsure from elsewhere, your data is transferred to and processed in the United States, and by the providers above wherever they operate. Where data protection law requires safeguards for those transfers, we rely on standard contractual clauses or an equivalent mechanism.

Unsure is a developer tool and is not directed at children. We do not knowingly collect personal data from anyone under 13, or under the age at which your jurisdiction allows an online service to be used without parental consent. If you believe a child has created an account, tell us and we will delete it.

When we change this policy we update the date at the top. For changes that materially affect how we use your data, we email the address on your account before they take effect. Continuing to use Unsure after that date means you accept the updated policy.

Questions, requests and complaints go to hello@unsure.dev. Put “Privacy” in the subject and we will route it to the right person.