What we see. What we never see.

The business model decides the shape of the product. Ours is subscription, paid by organizations that want their people's context to outlive the workday. That model does not require watching the people using it, and is actively harmed by it.

StandIn does not monitor people. StandIn does not track presence. StandIn does not read private messages, with one exception you control: if you turn on email replies for an away window, it reads the email colleagues send you during that window so your StandIn can answer. These are not marketing choices. They are an architectural constraint we enforce on ourselves.

The categories below describe core service data. Optional analytics, including account-linked product events, are explained in the cookies and analytics section.

1. i
   ✓

   Account information

   Name, work email, organization membership, and role. Used for sign-in, attribution, and access control. Nothing is enriched from third-party data brokers.

2. ii
   ✓

   Published content

   Briefs and handoffs you explicitly write and publish, plus metadata you allowlist from connected systems: issue titles, PR statuses, calendar shapes. If you turn on email replies for an away window, the email colleagues send you during that window.

3. iii
   ✓

   System records

   Audit events (who read whose brief, who changed a setting) and request logs for reliability. These never contain the substance of your content, only the shape of the action.

Video: nothing loads from YouTube until you press play. When you do, the player loads from youtube-nocookie.com and YouTube receives your IP address and browser details.

Within the authenticated Standin product, these are design decisions we turned down, not features waiting to be built. Optional session replay on our public website is described separately below.

• ✕Keystroke logs, mouse-movement, or typing-cadence metrics
• ✕Screen recordings, screenshots, or window focus history
• ✕Content from private DMs or private channels
• ✕"Active" / "idle" / "in a meeting" presence signals
• ✕Inferred sentiment, engagement scores, or productivity rankings

Data is used to answer work-context questions. The LLM retrieves already-published briefs and allowlisted metadata at query time, and generates a grounded response. The question, the answer and its sources are saved so your team can see what your StandIn said, and a copy is kept in Langfuse, the tool we use to check answer quality. We do not use your data to train public AI models, ours or anyone else's, and our LLM vendor contracts forbid it on their side too. Separately, with your consent, website and product analytics help improve StandIn. Product events use opaque identifiers and exclude work content; marketing measurement helps us understand campaigns. Refusing either does not affect product access.

Project data is visible only to members of that project. Published briefs are visible to the team they were published to. Admins can manage membership and audit access. There is no manager dashboard for watching people. Every read of another person's brief is logged and visible in the audit trail.

Briefs, questions, answers and audit events are kept while your organization uses StandIn, and deleted when it leaves. Copies of questions and answers in Langfuse, the tool we use to check answer quality, are kept until they are deleted. You can ask for deletion of your data at any time at [email protected], and we act on it within one month.

TLS 1.3 in transit. AES-256 at rest. Encrypted integration tokens. Logged audit events. Responsible disclosure welcomed at [email protected]. The full technical breakdown lives on the Security page.

We may update this policy. If we make material changes, especially any that affect the Core Promise above, we will notify you via email and in-app banner. Minor clarifications will be versioned here with a changelog entry. You should not need a lawyer to read this page.

StandIn is made by Foundry Systems, Amsterdam, the Netherlands. For the work data in your organization's StandIn (briefs, questions, answers and connected tools), your organization decides how it is used and Foundry Systems processes it on its behalf. For our website, sign-ups, emails you ask us for and optional analytics, Foundry Systems decides and is responsible. Contact us at [email protected].

• Running StandIn for your organization: our contract with your organization, and its instructions to us (GDPR Article 6(1)(b) and Article 28).
• Keeping StandIn secure and working, including error reports and audit events: our legitimate interest in a safe, reliable service (Article 6(1)(f)).
• Website and product analytics and marketing measurement: your consent, which you can withdraw at any time in the cookie settings (Article 6(1)(a)).
• Answering a demo request, contact form or estimate email you send us: the steps you asked us to take (Article 6(1)(b)). Newsletters only with your consent.
• Records the law requires us to keep, such as invoices: legal obligation (Article 6(1)(c)).

We use these providers to run StandIn. Each receives only what its job needs.

• Supabase: database and file storage
• Vercel: hosting
• Anthropic: the language model that writes answers
• Langfuse: keeps prompts and answers so we can check answer quality
• Sentry and New Relic: error reports and service health, without request content
• Nango: connections to your work tools
• Resend: sending email
• PostHog, Google Analytics, Microsoft Clarity, Contentsquare and LinkedIn: analytics and marketing, only with your consent

Some of these providers process data outside the EU, including in the United States. Ask [email protected] for the safeguards that cover each transfer and for the current list.

You can ask for a copy of your data, to correct it, to delete it, to limit how it is used, to object to its use, and to receive it as JSON. Write to [email protected] and we answer within one month. If your data is part of your organization's StandIn, we pass your request to your organization and help it answer. If you are named in a colleague's work or emailed a colleague who was away, your organization is responsible for telling you about it, and we help. You can withdraw consent for analytics at any time; this does not change what happened before. You can complain to a data protection authority: in the Netherlands, the Autoriteit Persoonsgegevens (autoriteitpersoonsgegevens.nl), or the one where you live or work.