← Hephus

Privacy policy

Draft. This describes accurately what the software does, because it was written alongside the code. It has not been checked by a solicitor, and the company details below are placeholders. Both need fixing before this is relied on.

Who we are

Hephus is operated by [COMPANY NAME], a company registered in England and Wales ([COMPANY NUMBER]), at [REGISTERED ADDRESS]. For anything about your data, write to privacy@hephus.com.

Two different roles

This matters, because Hephus sits in the middle of other people's businesses.

When you sign up as a seller, we are the data controller for your account.

When you buy something from a seller's store, that seller is the controller of your data and Hephus is their processor. We hold it on their behalf, under their instructions. Requests about a purchase go to the seller in the first instance, though we will help.

What we hold about sellers

  • Your email address, name, store name and branding.
  • Your Stripe account identifier. We never see or store your card details, your bank details, or your Stripe secret keys. Money goes directly to your own Stripe account and never passes through ours.
  • If you connect Instagram: an access token for your account, your Instagram user id and username, the keywords you configure, and a log of the comments and messages that triggered them.
  • Records of products, orders, customers, leads, expenses, agents and agent runs that belong to your business.
  • If you use the Hephus phone app and turn notifications on, a push token for that device. It is what lets Apple or Google deliver a notification to that phone, and it does nothing else. It is written when you turn notifications on and removed when you sign out, when you turn them off, or when we are told the app has been deleted. The app collects nothing else from your phone: no analytics, no crash reporting, no advertising identifier and no third-party components.

What we hold about buyers

  • Email address, and name when Stripe passes one on.
  • What was bought, when, for how much, and whether it was refunded.
  • A referral code, if the seller offers a share link.
  • If a buyer reached the seller through an Instagram keyword: their Instagram username, the comment or message text that matched, and the time.

Card details are handled entirely by Stripe and never reach Hephus.

Instagram data specifically

When a seller connects their Instagram professional account, Meta sends us the comments and messages on that account so the seller's keyword automations can work. We read the text to look for the seller's keywords, send the reply the seller wrote, and record what happened so the seller has a log. We do not use this content to train anything, and we do not share it with other sellers or with anyone else.

If you remove Hephus from your Instagram settings, Meta tells us and we delete the stored token immediately. See data deletion for removing the rest.

AI features

When a seller asks an agent to draft something, or asks for a page to be written, the relevant context is sent to Anthropic's API to produce the text. Anthropic does not train on data sent through their API. Sellers choose what material an agent is given.

Who else sees it

Supabase (database and file storage, hosted in the EU), Vercel (hosting), Stripe (payments), Brevo (email), Anthropic (AI features), and Meta (only for the Instagram features a seller has connected). Each holds only what it needs to do its job.

How long we keep it

Seller accounts and their business records are kept while the account is open, and for six years after closure where tax law requires it. Instagram event logs are kept for 12 months. Anything else is deleted on request.

Your rights

Under UK GDPR you can ask for a copy of your data, ask for it to be corrected or deleted, object to processing, or complain to the Information Commissioner's Office at ico.org.uk. Email privacy@hephus.com and we will answer within a month.

Changes

If this changes in a way that affects you, we will email you rather than quietly editing the page.

Last updated: [DATE]