Privacy Policy
This Privacy Policy describes how Stilops ("Stilops", "we") processes personal data through the customer portal. Controller: Stilops, Eenmanszaak · Pierre Monteuxstraat 18, 7558EA Hengelo · Chamber of Commerce (KvK) no. 42120645 · VAT no. NL005510332B81 · [email protected].
1. What we collect
Your organization profile and onboarding answers, chat messages with your agents, connection metadata (never the secret value itself — that is encrypted at rest and only decrypted at the moment an agent run needs it), and audit/run records (prompts, responses, cost, timing, approval status). Cookies: two strictly-necessary session cookies (to keep you logged in) and one preference cookie (to remember your chosen language). None are used for tracking, profiling, or advertising, so no consent banner is required or shown. The public marketing site also shows a cookie banner; your choice there (necessary-only or accept) is stored in one additional preference cookie. If you joined our pre-launch waitlist, we also store the email address you provided until you either register or ask us to delete it. When you register your organization, you can tell us how you heard of Stilops (one choice from a fixed list, optional). If you arrived through a link with campaign labels (utm_source, utm_medium, utm_campaign), we store those labels with your organization. Both stay with your organization for as long as it exists; we process them on the basis of our legitimate interest in knowing which channels work, and you can object to that. On the public marketing site we count visits without a cookie, without storing your IP address, and without the count storing anything on your device: per day only the page visited and the domain of the referring site, as a number. That count contains no personal data and cannot be linked to you or your organization; we keep it for 400 days. The demo without an account: you get your own temporary environment with made-up sample data. Anything you type there is processed by Anthropic's AI model so the demo works, and is deleted completely after one hour (if a task is still running then, within a quarter of an hour after that), together with the environment and its session cookie; only token and cost figures remain in our usage log, without any link to you. Please do not enter personal or confidential data in the demo. Legal basis: our legitimate interest in letting you try the service before you sign up. If you plan a free test run on our website, we store your name, email address, the name of your firm, any note you add and the chosen time, to keep the appointment and contact you about it; legal basis: steps at your request before entering into a contract. We also create a business contact from it, on the basis of our legitimate interest, which you can object to. The appointment is deleted one year after its date, or earlier if you ask us to delete your data. The personal link to your appointment is stored only in encrypted form (as a hash).
2. Why we are allowed to process this (legal basis)
Performance of the contract (Art. 6(1)(b) GDPR): your organisation profile and users, your chat messages with your agents, connection metadata, and the audit/run data. Without processing these we cannot provide the portal or the agents. This also covers the transactional email that comes with it: password reset, confirmation of your sign-up, invitations, a reminder shortly before a free trial ends, a confirmation of a test run you planned, replies to your tickets, and the notice that a decision is needed. Legal obligation (Art. 6(1)(c)): invoices and the financial ledger. We keep those for seven years because Dutch tax law requires it (Art. 52 AWR), which is why they fall outside an erasure request. Legitimate interests (Art. 6(1)(f)): the security and system logs and the audit trail, our interest being to keep the platform secure and traceable — exactly what you should expect from a service built on AI agents. And contacting business contacts at companies that could use our service, our interest being to make it known; every such message carries an unsubscribe link. You can object to any processing on this basis — see 'Your rights' below. Consent (Art. 6(1)(a)): only your choice in the cookie banner on our public marketing site. Inside the portal we use strictly necessary cookies and one preference cookie only, so nothing there depends on consent and you will not see a banner.
3. Retention
Data is retained according to the retention period configured in your organization's Settings page (minimum 183 days, in line with the EU AI Act's logging baseline for high-risk AI systems). We do not state a separate number here so this policy can never drift out of sync with that setting.
4. Sub-processors
Anthropic, via the Claude CLI or, if that is temporarily unavailable, via Anthropic's API, to actually run your agents' tasks. Hetzner Online GmbH (Germany, EU) hosts the servers on which Stilops and your data run. Cloudflare, Inc. handles DNS and traffic protection for our domains. Stripe processes payments and billing data if you have a paid plan. Kadaster (PDOK Locatieserver, the Netherlands, a public service of the Dutch government) converts Dutch addresses into coordinates when an agent with route planning (Planner, Secretary, Sales assistant) calculates a route. Only the address line (street, house number, postcode, town) is sent, never a name or other details; if you give coordinates yourself, nothing is sent. Hetzner Online GmbH (Germany, EU) also hosts Stilops' own email: the sender account from which we send you transactional mail (password reset, confirmation of your waitlist sign-up or early access, invitations, a reminder shortly before a free trial ends, a confirmation of a test run you planned, replies to your tickets, notices that a decision is needed) and the mailboxes of Stilops' internal agents. Your email address and the content of those messages are therefore processed on servers in Germany, within the EU, under a data processing agreement with Hetzner (Art. 28 GDPR). Your own agents have no mailbox and do not send mail, and you cannot connect your own mail provider yet. Do not put special-category personal data (health, biometrics, and the other Art. 9 categories) in tickets or other mail to us. If you use a voice feature (dictation, or a Secretary agent's meeting recorder), your browser vendor — Google (Chrome) or Microsoft (Edge) — processes the audio through its own speech-recognition service to produce text. That audio never reaches Stilops; only the resulting text does. This applies only while you're actively using a voice feature, and only for the browser you're using at that moment.
5. Your rights (GDPR)
You have six rights: access to your data (Art. 15), rectification of inaccurate data (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), portability in a commonly used format (Art. 20), and objection to processing that rests on our legitimate interests (Art. 21) — including being contacted as a prospect, which we then stop without weighing it up. You exercise them through [email protected], or yourself in the portal under Settings → Account → Your data: download your data, or request erasure. We respond within one month; if your request is complex we may extend that by two months, and we will tell you so within the first month, with the reason. We may ask for additional details if we are not certain who is making the request. It costs you nothing, unless a request is manifestly unfounded or excessively repeated. On an erasure request of the whole organisation, the organisation profile, the users, the agents, the runs, the conversations, the connections, the knowledge base and the tickets are removed; on a request for one account, that account and its sessions. We also have the customer record at Stripe and any files on our servers removed, and inform recipients (Art. 19). Restriction (Art. 18) and objection (Art. 21) we handle by hand: write to [email protected] and we stop the processing concerned. What stays are your acceptances of this statement and the terms, and the invoices — those have their own legal or evidential basis, and 'Retention' above says for how long. If you are unhappy with how we handle your data, you can lodge a complaint with the Dutch Data Protection Authority (autoriteitpersoonsgegevens.nl) or with the supervisory authority of the EU country where you live or work. We would rather hear it from you first, but that right stands regardless of us. Note: if your employer uses Stilops, that organisation is the controller for the content the agents handle and we are its processor. Address a request about that data to them; we help them carry it out.
6. AI transparency
You are always working with AI agents when using Stilops. This is disclosed on first login and recorded against your account — see the banner shown when you first sign in.
7. Security
Passwords are stored using scrypt hashing, and two-factor authentication (MFA) is available to every user and can be enabled per account; session cookies are http-only and transmitted only over encrypted (https) connections. Connection secrets are encrypted at rest and decrypted only at the moment an agent run needs them (see Section 1). Every proposal, test run, and decision is recorded in an append-only audit trail. On top of that, no consequential action executes without explicit human approval, so an agent cannot act on your data silently or irreversibly. Payments are handled by Stripe; we do not store card details on our servers. No system is perfectly secure — this describes current measures, not an absolute guarantee.
8. Stilops on LinkedIn
We publish our own posts on LinkedIn through the interface LinkedIn offers for that. In doing so we do not process data about you as a reader: we do not retrieve or store profiles, comments or reactions of other LinkedIn members. For each post we keep only aggregated numbers (views, clicks, and the number of reactions, comments and shares), without names, for at most one year. There is no LinkedIn pixel or Insight Tag on stilops.com. If you follow a link from a LinkedIn post to our website, the link may carry a campaign code (UTM); we count that without cookies and without recognising you. What you do on LinkedIn itself is LinkedIn's responsibility, and LinkedIn's own privacy policy applies to it.
9. Changes to this policy
This policy carries a version number and a date, shown at the bottom of this page. We keep every version, and you can read earlier versions here. If we change this policy materially (for example because we start using data for a new purpose, engage a new recipient or sub-processor, or keep data longer), we tell account holders with a notice in the portal before the change takes effect. A clarification, a typo fix, or an updated contact detail may take effect immediately without notice. For data we process as a processor on behalf of your organisation, the terms of the data processing agreement apply as well: we announce a new sub-processor at least 30 days in advance, and you can object to it.
Version 1.7 — in effect since 22 October 2026