Privacy policy

Last updated: 10 November 2026

This privacy policy covers the Epic suite: Epic Context and every app that works under it, such as Epic Work, Epic Social and Epic Capture. Epic Context holds the context of an organisation (its brand, strategy, users, product, design and decisions) and the apps of the suite work with it, for people and for the AI tools they use. Here you read which data we process, why, how we protect it and which rights you have. We keep it as short and clear as we can.

1. Who we are

The Epic suite is a product of Epicstories B.V., registered with the Dutch Chamber of Commerce (KvK) under number 75336197, located at Empermolen 10, 7399 AP Empe, the Netherlands. Questions about privacy? Email hallo@epicstories.nl.

Do you use the Epic suite in the organisation of your employer or client? Then that organisation decides which data goes into it. It is responsible for that data, and we process it on its behalf, under a data processing agreement. We are responsible for your account and for how the Epic suite itself works.

2. Which data we process and why

  • Your account: name, email address, the organisations and projects you are a member of, and your role. If you sign in with a passkey, we only store its public part; the secret part stays on your device. If you set a password, we store only a hash of it. Why: so you sign in securely and get the right access.
  • The context of your organisation: what you and your colleagues write in Epic Context, such as blocks, decisions, messages under a page, notes, plans and tasks, and who changed what and why. Why: that is the service.
  • AI connections and conversations: which AI tools you connected (such as Claude or Cursor), the calls they made in a session, and your conversations with the AI chat. Why: so these tools can work with the context, and so your organisation can see what an AI changed and undo it.
  • Connections and data sources, if your organisation switches them on. See sections 3 and 4.
  • Technical data: our servers keep log files, such as the time, the page requested, error messages and IP address. Why: to track down outages and abuse.
  • AI usage: how much AI text an organisation and a person use per month. Why: for the organisation's monthly budget.
  • A demo request: the name, email address, company and message you send with Book a Demo. Why: to contact you about a demo.

We do this because it is necessary for the agreement with you or your organisation (Article 6(1)(b) GDPR). Security and log files fall under our legitimate interest in a secure, working service (Article 6(1)(f)).

3. Connections

An owner or admin of your organisation can connect outside services, such as an image or video service or another AI model provider. Their keys are entered only in the settings, stored encrypted, and never shown again. Epic Context sends data to such a service only when someone asks for one of its actions, with a reason, and keeps a log of it. If a connection is off, nothing is sent to it.

You can also connect your own mailbox (Settings › Mailboxes). Its sign-in (a password or app password) is stored encrypted, only for you, and is used only to send what you ask for and for your mail in the suite.

A research report can be mailed from its maker's own mailbox to the recipients they enter, each with a note of who asked for it. Every such mail has a link to unsubscribe in one click.

4. Data sources: LinkedIn and Microsoft Advertising

An owner or admin of your organisation can connect LinkedIn and Microsoft Advertising once, by signing in at that service. Each project of the organisation then chooses which ad account and company page it reads.

  • What we read: from LinkedIn, the figures of the chosen ad account (cost, impressions, clicks, conversions, leads; per campaign, ad and day; and who saw the ads by job function, seniority, industry, company size, company, title and country), the campaigns, the figures of the chosen company page (followers, page views, followers by group), its recent posts with their figures, its events, and the lead forms with the number of leads. To count leads, LinkedIn sends us the form responses; we only count them. Their answers, such as names and contact details, are never stored, shown or given to an AI. From Microsoft Advertising, the performance figures of the chosen account (cost, impressions, clicks, conversions, revenue; per campaign, keyword, search term and similar) and search volumes for keywords.
  • Only reading: Epic Context does not post, change campaigns, budgets or bids, or send messages. Microsoft only offers a permission that also allows changes; Epic Context uses it to read, through a fixed list of read operations.
  • Who sees it: members of the organisation, in its dashboards (such as Analytics in Epic Work) and in the AI tools they use with Epic Context. Epic Context fetches the figures from the service at the moment someone asks. It keeps the login, not the figures.
  • AI and LinkedIn: following LinkedIn's rules, an AI only gets figures from LinkedIn: never the text of posts, profiles, the name of the page, events, or who saw an ad by job, industry, company or place. Those stay on the dashboards for people.
  • What we store: the sign-in (encrypted), when and by whom it was made, which ad account and page each project reads, and a log of who connected, chose or asked a question (without the figures). Answers are kept in the server's memory for at most 10 minutes, and Microsoft's search volumes, which say nothing about people, for at most 24 hours. Answers in AI chats can contain figures; those are kept like the rest of the organisation's content (section 7).
  • Ending it: an owner or admin chooses Disconnect in Settings › Organisation › Connections. The sign-in and every project's choice are deleted at once. You can also withdraw the permission at the service: at LinkedIn under Settings & Privacy › Data privacy › Permitted services, at Microsoft in the app permissions of your account.

Our use of data from these services also follows their own terms, such as LinkedIn's API Terms of Use and Microsoft Advertising's API terms.

5. Who we share data with

We do not sell data. We work with these service providers, with agreements on security and confidentiality:

  • Hetzner (Germany): our servers, database and backups, in the European Union.
  • Anthropic (United States): runs the AI features, unless your organisation chose another model provider. Only the text needed for an AI request goes to the provider. Anthropic does not use that text to train models.
  • Resend (United States): sends sign-in links and invitations by email.
  • The services and data sources your organisation connects (sections 3 and 4).

If data goes to a country outside the European Union, this happens under the European Commission's standard contractual clauses. Otherwise we only pass data on if the law requires us to.

6. Cookies

The Epic suite only uses cookies it needs to work: to keep you signed in, to secure signing in (also when you connect a data source), and to remember which organisation and project you have open across the apps of the suite. We do not use cookies or scripts to track you, for statistics or for advertising.

7. How long we keep data

  • Your account: as long as you use it.
  • The content of an organisation, including AI conversations and the history of changes: as long as the organisation exists, or as agreed with it.
  • The sign-in of a data source: until it is disconnected. See section 4.
  • A demo request: 12 months, then it is deleted, or sooner if you ask.
  • Backups: we make a backup every night and keep the last 14. Deleted data is therefore gone from the backups too after 14 days at most.
  • Log files: only as long as needed to track down outages and abuse.

8. Security

  • All connections are encrypted (TLS).
  • You sign in with a passkey, an email link or a password we only store as a hash.
  • Keys and sign-ins of connections and data sources are stored encrypted, and are never handed to an app or an AI.
  • Data is separated per organisation and project, and every request is checked against your role.
  • Every change an AI makes is recorded with its reason and can be undone.
  • Only those who need it for administration can access the servers.

9. Your rights

You may view your data, have it corrected or have it deleted. You may also ask us to process less, to take your data to another service, or object. To do so, email hallo@epicstories.nl. We reply within a month.

Do you use the Epic suite through your employer or client? Then we may forward your request to that organisation, because it is in charge of the data in its context.

Do you disagree with how we handle your data? Then you can file a complaint with the Dutch Data Protection Authority, the Autoriteit Persoonsgegevens.

10. Changes

We update this privacy policy when the Epic suite changes. The date at the top shows when that last happened. For major changes we let you know in advance.