Laminary helps your team's AI tools share what's done, what's in progress and where to pick up. To do that, it stores some of your work. This policy explains what we collect, why, who processes it with us, and how you stay in control.
1. Who we are
Laminary (laminary.dev, app.laminary.dev, the Laminary connector and the laminary command-line tool) is operated from Israel by its founder as an individual. Laminary is not yet a registered company; when it becomes one, this section will name it and the change will be announced as described in section 12. Until then, the operator's full identity and postal address are available on request at hello@laminary.dev. "We" and "us" in this policy mean Laminary. We are the controller of the personal data described here, except for content that a team puts into Laminary on behalf of its organisation. For that content, the team's organisation is the controller and we act as its processor, following its instructions; business customers can ask us for a data processing agreement (DPA).
You aren't legally required to give us any personal data. Without an email address, though, we can't create an account, and without the work your AI tools report, Laminary can't do its job.
Contact for anything in this policy: hello@laminary.dev.
2. What we collect
Account and team
- Email address and password (stored hashed by our authentication provider; we never see it). If you choose "Continue with Google", we receive your name, email and profile picture from Google.
- The display name and role you add to your profile, your team, the projects you belong to and your role in them.
- Beta sign-up answers: team size, the AI tools you use, what you want to fix, and how you heard about us.
Work your AI tools send to Laminary
When you connect an AI tool (Claude, ChatGPT, Claude Code, Cursor, Codex and others), it reports work to Laminary so that teammates' AIs don't redo it. Depending on the sharing level you choose for a session (private, announce, summary or full; summary is the default), this can include:
- goals, steps, status, summaries and handoffs of work units;
- decisions, messages, requests, tasks and notifications between teammates;
- file names and paths your AI is working on, and files you choose to save to a task or handoff;
- which tool and session the work came from, and token counts the tool reports.
Before anything leaves your machine, the command-line tool runs a filter that removes things that look like secrets (keys, tokens, passwords), and the server runs a second pass. This lowers the risk; it can't guarantee that nothing sensitive gets through, so don't paste secrets into chats connected to Laminary.
Repository and site context (only if you connect them)
If a project admin installs the Laminary GitHub App or links a website, we store file paths, one-line file summaries, numeric embeddings of code, commit messages and authors, and the text of public site pages. Raw code text is stored only if the project admin turns that on.
Connections and devices
- Keys and sign-in tokens for each AI tool you connect, so we can recognise it. You can revoke each one on its own.
- If you turn on notifications, the push subscription your browser gives us.
Site and app analytics
We run our own analytics, with no cookies and no third-party tracking scripts. They work in one of two ways, depending on your choice in the analytics bar on laminary.dev:
- If you click "Allow": we keep a random ID in your browser's local storage and a visit ID that expires after 30 minutes without activity, so we can count returning visitors and see which pages a visit included and where it came from. The ID is random and contains nothing about you. We ask again after 12 months, and you can change your answer any time with "Analytics choices" in the footer; saying no deletes the IDs.
- If you click "Not now", or don't answer: nothing is stored in your browser for analytics. Our server combines your IP address and browser type with a secret value that changes every day and turns them into a one-way code. The code can't be turned back into your IP address, and because it changes daily, it can't follow you from one day to the next.
In both cases we record the pages and sections you view, buttons you click, time the page was visible, the site that referred you, campaign tags in the link, device type, browser, operating system, language and time zone, and an approximate location (country, region and city) that our hosting provider derives from your IP address. Your IP address is not stored. In the control room, these events are linked to your account so we can see how the product is used.
Our sites and the control room use your browser's storage only for things they need to work or that you chose: keeping you signed in, and remembering settings such as your current project, display and accessibility settings, and an analytics opt-out. These are strictly necessary for the service you asked for and aren't used for tracking.
We respect Global Privacy Control and Do Not Track: if your browser sends either signal, we don't record analytics and don't show the analytics bar. You can also change your analytics choice, or turn analytics off completely (this saves a single "opted out" setting in your browser so we remember it):
Things you send us
Feedback you give in the app, emails you send us, and answers to questions we ask during the beta (for example what you'd be willing to pay).
Technical logs
Our hosting and database providers keep short-lived request logs (including IP address) for security and debugging.
3. How we use it, and on what legal basis
| Purpose | Legal basis (GDPR) |
|---|---|
| Running Laminary: accounts, teams, matching new work against finished work, handoffs, tasks, notifications, emails about your account | Performance of our contract with you (Art. 6(1)(b)) |
| Running the beta: deciding who gets in, inviting teammates, asking for feedback | Contract and our legitimate interest in running a fair beta (Art. 6(1)(f)) |
| Understanding how the site and product are used, and improving them | Legitimate interest (Art. 6(1)(f)); you can opt out at any time |
| Remembering your browser across visits for analytics (only after you click "Allow") | Consent (Art. 6(1)(a) and Art. 5(3) of the ePrivacy Directive), which you can withdraw at any time |
| Keeping Laminary secure, preventing abuse and enforcing our terms | Legitimate interest (Art. 6(1)(f)) |
| Product news and launch emails | Consent, which you can withdraw from any email (Art. 6(1)(a)). We send marketing email only to people who agreed to it, as Israel's Communications Law (section 30A) and EU rules require, and every such email has an unsubscribe link |
| Meeting legal obligations | Legal obligation (Art. 6(1)(c)) |
We don't sell personal data, share it for cross-context behavioural advertising, or use it to make decisions based solely on automated processing that have legal or similarly significant effects on you. Laminary's AI ranks and matches work items; it doesn't make decisions about people.
4. AI processing
Some Laminary features use a large language model: matching a new goal to work that's already done, writing catch-ups and briefs, ranking tasks, and answering questions in the control room. For these, we send the relevant work text to Anthropic's API (Claude models). Under Anthropic's commercial terms, API inputs and outputs are not used to train its models. Code embeddings are computed inside our own backend and not sent to a third party.
The AI tools you connect to Laminary (Claude, ChatGPT, Cursor and others) are run by their own providers under their own terms. What your tool sends to us is covered by this policy; what Laminary returns into your chat is then also processed by your tool's provider under its terms.
5. Who processes data with us
We use these service providers. Each processes data only to provide its service to us.
| Provider | What for | Where |
|---|---|---|
| Supabase | Database, authentication, file storage, backend functions | EU (Frankfurt) |
| Cloudflare | Hosting of laminary.dev and app.laminary.dev, DNS, security, analytics relay | Global network |
| Anthropic | Laminary's AI features (see section 4) | United States |
| Resend | Account and beta emails | United States |
| "Continue with Google" sign-in, only if you use it | United States | |
| GitHub | Repository context, only if a project installs the GitHub App | United States |
| Your browser's push service (Apple, Google, Mozilla, Microsoft) | Delivering notifications, only if you turn them on | Varies |
Inside your team, other members see the work in projects they belong to, according to the sharing level and project access rules. We may also disclose data if the law requires it, or to protect the rights and safety of our users or of Laminary. If Laminary is sold or merged, data would move to the new owner under this policy, and we'd tell you first.
6. International transfers
Your account and work data are stored in the EU. Some providers above are in the United States. Where data goes to a country without an adequacy decision, we rely on the provider's certification under the EU-U.S. Data Privacy Framework or on the European Commission's Standard Contractual Clauses. Israel, where Laminary is operated, has an adequacy decision from the European Commission.
7. How long we keep it
- Account, team and work data: while your account or team exists. When you delete your account or a team owner deletes the team, we delete it within 30 days, and backups roll off within a further 30 days.
- Saved files: 14 days on the Free plan, 90 days on paid plans, then deleted automatically.
- Beta waiting list: until the beta ends or you ask us to remove you.
- Analytics events: up to 26 months, then deleted or reduced to totals that identify no one.
- Technical logs: as set by our providers, usually days to weeks.
8. Your rights
Depending on where you live (including under the GDPR, the UK GDPR, Israel's Protection of Privacy Law, 5741-1981, and U.S. state laws such as the CCPA), you can ask us to:
- give you a copy of your data, in a portable format;
- correct it;
- delete it;
- restrict or object to how we use it, including analytics;
- withdraw consent you gave, without affecting what happened before.
Write to hello@laminary.dev from the email on your account. We'll answer within 30 days. We won't treat you differently for using these rights. If content about you was added by a team, we may pass your request to that team's owner, who decides about their organisation's data.
You can also complain to a data protection authority: in the EU, the one where you live or work; in the UK, the ICO; in Israel, the Privacy Protection Authority. We'd appreciate the chance to fix things first.
9. Security
All traffic is encrypted in transit (HTTPS). Data is encrypted at rest by our database provider. Every table is protected by row-level security, so a team member can only read what their team and projects allow. Each connected tool has its own key that you can revoke. Access to production systems is limited to the founder. We follow the Israeli Protection of Privacy (Data Security) Regulations, 2017 and the GDPR's security requirements in proportion to the data we hold. No system is perfectly secure; if a breach affects your data, we'll tell you and the relevant authorities as the law requires.
10. Notice for California residents
Under the California Consumer Privacy Act (CCPA, as amended by the CPRA): in the last 12 months we collected the categories of personal information described in section 2: identifiers (name, email, a daily analytics code, and a random browser ID if you allowed it), internet and electronic activity (site and app usage), approximate geolocation (city level), professional information (role and team), and the content of your work. We collect them for the purposes in section 3 and disclose them only to the service providers in section 5. We don't sell or share personal information, and we don't use sensitive personal information to infer characteristics about you. You have the rights to know, delete and correct, and not to be discriminated against for using them. You or an authorised agent can use them by writing to hello@laminary.dev; we'll verify the request against the email on the account. We honour Global Privacy Control as an opt-out signal.
11. Children
Laminary is a work tool and isn't meant for anyone under 16. We don't knowingly collect data from children. If you think a child has given us data, write to us and we'll delete it.
12. Changes to this policy
If we change this policy, we'll update the date at the top. If a change is significant, we'll email account holders before it takes effect.
13. Contact
Questions, requests or complaints: hello@laminary.dev.