Privacy Policy

Section 1 – What We Collect

Your account. When you sign up we store your email address, your password (only as a one-way hash, never in readable form) and, if you give it, your name. For your organisation we store the company name, VAT number and billing address you enter. We also store the IP address and browser user agent each sign-up came from, which is how we recognise abusive sign-ups. Payment details are handled by Stripe (Section 5); we do not store card numbers.

Your API tokens. We store the API tokens we issue to your organisation so that we can recognise your requests. A token identifies your organisation, not a person.

Your use of the API and the MCP server. What each request carries and what we keep of it is described in Section 11 (REST API) and Section 10 (MCP server).

Your visits to this website and the portal. Product analytics are described in Section 7; our hosting provider receives your IP address as part of every connection.

Email. We send the emails the service needs, such as address verification, invitations and account notices. With your permission, we may also send you emails about our product and other updates.

Section 2 – Why We Use It and Your Consent

We use your account data to provide the service you signed up for, to bill it, to protect it from abuse and to answer you when you contact us. If we want to use your personal information for any other reason, such as marketing, we ask you for your consent first or give you the opportunity to say no.

How do I withdraw my consent?

If after you opt-in, you change your mind, you may withdraw your consent for us to contact you, for the continued collection, use or disclosure of your information, at any time, by contacting us at [email protected].

Section 3 – Disclosure

We may disclose your personal information if we are required by law to do so or if you violate our Terms of Service.

Section 4 – Data Storage

Your account, your API tokens, your registered connections and the request records described in Section 11 are stored in our database, hosted by DigitalOcean in its EU region (Frankfurt, Germany; see Section 5). Account data and API tokens are kept for as long as your organisation's account exists and are deleted with it; the periods for request records are stated in Section 11.

Section 5 – Third-Party Services (Processors)

We engage the service providers listed below to operate tounify. Each of them processes personal data only for the purposes described here and on our instructions, and each is bound by its own data protection terms. This list is kept current; we publish it so you can see exactly who is involved before you sign up.

Transfers outside the EU/EEA: where a provider processes data outside the European Economic Area, the transfer is covered by the European Commission's Standard Contractual Clauses together with supplementary technical measures. You can request the relevant documentation from us at any time.

Fonts and assets: all web fonts are self-hosted and served from our own infrastructure. No font, script, or asset request leaves our servers to a third-party content delivery network, so visiting this site transmits no data to font or CDN providers.

Once you follow a link to a third-party website, you are no longer governed by this Privacy Policy or our Terms of Service. We recommend reading the privacy policy of any such provider.

Section 6 – Security

To protect your personal information, we take reasonable precautions and follow industry best practices to make sure it is not inappropriately lost, misused, accessed, disclosed, altered or destroyed.

Section 7 – Cookies

We use cookies to maintain session of your user. It is not used to personally identify you on other websites.

We also use PostHog for product analytics, hosted in the EU (eu.i.posthog.com), to understand which pages are read and where people get stuck. On this website and on our API reference at api.tounify.io it is optional and only runs after you accept our cookie banner. In the signed-in Cockpit portal it forms part of providing and improving the service to account holders, where we record product usage (pages opened, features used, subscription milestones) against your account. We do not use advertising or cross-site tracking, and we never sell this data.

For more information about cookies, please see our Cookie Policy.

Section 8 – Age of Consent

By using this site, you represent that you are at least the age of majority in your state or province of residence, or that you are the age of majority in your state or province of residence and you have given us your consent to allow any of your minor dependents to use this site.

Section 9 – Changes to This Privacy Policy

We reserve the right to modify this privacy policy at any time, so please review it frequently. Changes and clarifications will take effect immediately upon their posting on the website.

If we make material changes to this policy, we will notify you here that it has been updated, so that you are aware of what information we collect, how we use it, and under what circumstances, if any, we use and/or disclose it.

Section 10 – MCP Server

We operate a Model Context Protocol (MCP) server at mcp.tounify.io for use with AI assistants. It returns explanatory information about European electricity markets and about integrating our API; it does not return pricing data or customer records. Using it requires a Tounify account: an assistant connects either with your organisation's API token or through a sign-in to the Tounify portal, where you approve the connection.

When you approve a connection we store which user approved it, for which organisation, the name the assistant registered itself under, and when the connection was made and last renewed. You can see and disconnect your organisation's connections on the AI Assistance page of the portal. We count tool calls per organisation and day, which is how the free allowance and your usage are shown. For each tool call we record in our product analytics (PostHog, see above) the tool name, whether it succeeded, how long it took and, where given, the country or topic it was asked about, attributed to your organisation. We do not record the other text you send to a tool.

A connection is kept until you disconnect it or your account is deleted; if the assistant does not renew it for 90 days it stops working. The daily tool-call counts are kept for as long as your organisation's account exists, because the free allowance includes a total. Both are deleted with the account. The analytics events are held in our PostHog project in the EU (see above) and are not sold or shared. Questions about this data go to [email protected].

To protect the service from abuse we also apply short-lived, in-memory request limits based on the connecting IP address; these are not written to persistent storage. Our hosting provider records standard HTTP access logs as it does for our other services.

Some tools accept text you supply — for example an error message you are trying to diagnose. Do not include credentials, API tokens or personal data in that text.

Section 11 – REST API

Our API at api.tounify.io prices tariffs, not people. A request carries your API token, the country and the tariff ids you ask about and, where you let us select the grid operator from an address, a postal code. It carries no names, meter identifiers, account numbers or consumption history. A postal code on its own does not identify a person.

Request records. For each price request we write a record of the time, the token and your organisation, the country, the tariff ids, the API version and endpoint, any error, and the IP address the request came from. The postal code is not part of it. A record is deleted 31 days after the request, once it has been counted into the daily totals we bill from; records made with a testing token are kept for 90 days. The daily and monthly counts per token and tariff carry no IP address and no postal code, are kept no longer than your organisation's account exists, and are deleted with it.

Connections. When you register a connection we store what you send for it: your own label for it (the reference), its tariffs, its postal code, its customer class and its technical properties such as capacity and meter type. There is no field for a name, an address or contact details, and a field we do not define is rejected rather than kept. The reference is the one value you write freely and it is part of every request about the connection, so use an opaque label, never a name, an address, or a customer or contract number. Deleting a connection removes it, but the monthly record of which connections were registered in which month, from which usage is billed, keeps its reference until your organisation's account is deleted.

Access logs. Each API request is also written to our application access log: its method and path, the status and response time, the IP address, your organisation, the country, the API version and the query parameters, which include the postal code when you send one. On connection routes the log holds the route pattern instead of your reference, and your API token is never written to it.

Request records, the counts and your connections, including the monthly record, are deleted when your organisation's account is deleted. Questions about this data go to [email protected].

Questions and Contact Information

If you would like to access, correct, amend or delete any personal information we have about you, register a complaint, or simply want more information, contact us at [email protected].

Data Protection Compliance

The collection, processing and use of data by tounify always takes place in accordance with the applicable legal provisions, in particular in accordance with:

• General Data Protection Regulation (GDPR)
• Data Protection Act (DSG) 2018
• Data Protection Directive for Electronic Communications (E-Privacy Directive)
• Telecommunications Act (TKG) 2003
• Other applicable EU regulations

All data provided by users is treated confidentially and used for the purpose of providing our services. Any further use of data takes place exclusively on the basis of a separate consent given by the user.