Privacy
What ssrs2.net and an SSRS2 purchase keep about you, and where. SSRS2 is published by A.G.O. (Switzerland).
- The website
- ssrs2.net counts visits with Google Analytics, which sets cookies in your browser. The contact form (Tally) sends us what you type into it.
- The SSRS2 library
- SSRS2 runs in your own applications and sends nothing to us: the licence key is checked offline, and your reports and data never leave your servers.
- A purchase
- Stripe handles the payment and keeps what checkout asks for: your name, company, email, billing address, VAT number and the payment method, which never reaches us. We receive the invoice and your company, email and billing address.
- Your licence
- The licence service keeps, for each paid invoice, the company, the email, the invoice number and the licence's content (never the key itself), in Microsoft Azure's West Europe region, and emails the key from Google Workspace. Accounting records are kept as long as Swiss law requires, ten years.
- The online designer
- designer.ssrs2.net has its own privacy page, with what an account keeps: designer.ssrs2.net/privacy.
- The hosted MCP server
- ssrs2.net/mcp receives what an AI agent sends it: a report or Markdown, its rows and pictures, and a licence key or a sign-in token when one is given. Each call runs in a process of its own, which ends with it, and nothing of the call is kept afterwards, except a file it writes, held in memory for ten minutes for one download. We log one line per call: the tool, the format, sizes, how long it took and how it went, never the content; the logs are kept 30 days in Microsoft Azure's West Europe region. The caller's address is held in memory only, to count its calls.
- Signing in to the hosted MCP server
- When an AI application (claude.ai, ChatGPT...) connects to ssrs2.net/mcp/licensed, you paste your licence key on ssrs2.net's sign-in page. It is checked there and not kept: it travels encrypted inside the tokens the application holds, which only SSRS2's servers can read. For each connection we keep the licence's id, the application's name and address, when the connection was made and last renewed, and whether it was ended, in Microsoft Azure's West Europe region; never the key. An AI agent can also register anonymously and be connected by you on ssrs2.net with its code and your licence key: we keep the registration's dates and status and, once connected, the licence's id; your key is kept encrypted only until the agent collects its token, normally seconds later, and erased then (one never collected is erased with the next registrations after an hour).
- Who processes it
- Stripe (payments), Microsoft Azure (hosting), Google (email and analytics), Tally (the contact form), each under its own terms and privacy policy.
- Your rights
- To see, correct or remove what we hold about you, write from the address concerned to [email protected]. Invoices already issued stay in the accounting records.
Last updated: 12 October 2026.