Privacy policy

Oyster is a business tool for people who configure IT hardware for their customers. This policy covers the people who use Oyster (users) and anyone whose details a user enters.

• Account details: name, work email, company, country, role, and your password (stored hashed).
• What you enter to get a configuration: the customer request, your answers to Oyster's questions, uploaded documents, and the configurations Oyster builds.
• Usage and billing: which features you use, credits used and bought, and purchase records. Card payments are handled by Stripe; we never see or store your card number.
• Connector sign-in: when you connect Claude or ChatGPT, a sign-in token tied to your Oyster account and the company you chose.
• Support: what you send us by email or through feedback in the app.

We ask you not to enter your customers' personal details. Oyster needs the hardware requirements, not names.

• To provide Oyster under our agreement with you: your account, configurations, exports and support (performance of a contract).
• To bill you and keep accounting records (legal obligation).
• To keep Oyster secure and to improve it, for example finding where a configuration went wrong (legitimate interest).
• To send you service messages about your account. We send product news only if you agreed.

Oyster uses AI models to understand requests and build configurations. Different steps use different models, chosen for the job:

• Models from Anthropic process the conversation.
• For some design and build steps we use open-weight models hosted by inference providers through OpenRouter. These receive only the structured hardware requirements and design: no chat history, no uploaded documents, no information about you or your company, and no customer quotes. Names, email addresses, phone numbers and personal ids that Oyster has recorded are removed before any such request is sent.
• Search inside Oyster's own knowledge uses embeddings from OpenAI on the search text.

Anthropic and OpenAI do not use data sent through their APIs to train their models. Open-weight requests go only to hosts that, by the policy they declare to OpenRouter, neither store nor train on them.

If you use the connector, the conversation itself happens in Claude or ChatGPT under your agreement with Anthropic or OpenAI; Oyster receives what the assistant sends to Oyster's tools.

Oyster and its database run in Frankfurt, Germany. We use these processors:

Transfers outside the EU/EEA rely on the EU Commission's standard contractual clauses or the EU–US Data Privacy Framework, as each provider offers.

• Account data: while your account is active, then 3 months after closing.
• Cases, requests and configurations: while your account is active, unless you delete them earlier; deleted within 30 days after you close your account.
• Billing records: 7 years, as Swedish accounting law requires.
• Logs: 90 days.

You can ask for a copy of your data, correction, deletion, restriction, portability, and object to processing based on legitimate interest. Write to support@oyster.tech. You can also complain to the Swedish Authority for Privacy Protection (IMY), www.imy.se.

Oyster uses only the cookies it needs: to keep you signed in, to remember your company, your language and an invitation code you followed. We use no analytics or advertising cookies.

We will post changes here and tell account holders by email when they matter.

Oyster AI AB, Stockholm, Sweden, support@oyster.tech. Our terms of service are at /terms.