Privacy Policy
How Demirius Ltd handles personal data about visitors to my-pepts.com, the labs that sign up for My-Pepts, and their staff.
Last updated
Contents · 13 sections
- 1.Who we are and what this policy covers
- 2.If you shop at a lab's store
- 3.What we collect
- 4.Why we use it, and our lawful basis
- 5.Marketing
- 6.Cookies
- 7.Who we share it with
- 8.Where your data goes
- 9.How long we keep it
- 10.How we protect it
- 11.Your rights
- 12.Complaints
- 13.Children, automated decisions and changes
This policy explains what personal data we collect when you visit my-pepts.com or use a My-Pepts account, why, who sees it, how long we keep it, and the rights you have over it. If you are a shopper at a lab's store, start with the section for shoppers.
1.Who we are and what this policy covers#
Demirius Ltd, trading as My-Pepts, is the controller of the personal data this policy describes. That means we decide why and how it is used, and we are the ones you can hold to this policy.
- Company
- Demirius Ltd, trading as My-Pepts
- Registered in
- England and Wales
- Company number
- 16820023
- Registered office
- 47 Cranwell Crescent, Eaton Leys, Milton Keynes, MK17 9GS, England
- VAT number
- GB 505 3821 14
- hello@my-pepts.com
This policy covers:
- people who visit my-pepts.com;
- people who sign up for My-Pepts or use its account dashboard or a store admin, including lab owners and the staff they invite;
- people who contact us, or buy a service from us such as a branding package.
For anything about your data, including a request to see or delete it, email hello@my-pepts.com. We are a small company and are not required to appoint a Data Protection Officer, so requests are handled by us directly.
2.If you shop at a lab's store#
Each store on My-Pepts is run by an independent lab, which is the seller and the controller of the personal data it collects from its shoppers. We host and run the software for the lab, as its processor, under our Data Processing Agreement. The lab's own privacy notice, on its store, explains what it does with your data.
To make a request about data a store holds about you, contact the lab that runs it. If you write to us instead, we pass your request to the lab and tell you we have done so.
We act as a controller for a few purposes that span every store: protecting the Platform from attacks, fraud and abuse, for which we use technical data such as IP addresses and request logs, and responding to lawful requests from authorities. This policy covers that use.
3.What we collect#
- When you visit my-pepts.com: what our hosting provider records with each request, which is your IP address, browser and device type, the page requested, the page that linked to it, and the time. We do not use analytics or advertising cookies on my-pepts.com.
- When you sign up: your name, email address and password (stored only as a salted hash, so nobody here can read it), and your business's name, address and country, its company and VAT or tax numbers where it has them, and the store address you choose.
- When you pay: your billing name, address and email, your plan and your invoices. Your card details go straight to Stripe; we receive only the card brand, the last four digits, the expiry date and whether the payment succeeded.
- If we verify your business: the documents and information we ask for, such as company registration documents, proof of address, the address you ship from and the payment provider you use.
- When you use your account dashboard or store admin: sign-in records (time, IP address and browser), the actions we log for security and support (such as changing plan, inviting staff or creating an API key), and how much of your plan's limits you use.
- When you invite staff: their name, email address and role. If you are a member of staff, your lab gave us these.
- When you use AI features: what you send to the feature and what it returns.
- When you connect another service: the identifiers and access tokens needed to connect it, such as your Google Ads customer ID. Access tokens are stored encrypted.
- When you buy a domain through us: the registrant details the registry requires (name, organisation, postal address, email and phone number). We pass them to our registrar partner and the registry, and the registry's rules may require some of them to appear in the public registration database.
- When you order a branding package: your brief, the files you share and our correspondence about the work.
- When you contact us: your message, your contact details and our reply.
- If you ask to hear from us: your email address and the record of when you agreed.
We do not ask for special category data, such as anything about health, ethnicity, beliefs or sexuality. Please do not send it to us.
4.Why we use it, and our lawful basis#
UK GDPR requires a lawful basis for each use of personal data. Here they all are.
| What we do | Data used | Lawful basis |
|---|---|---|
| Create and run your account and provide the Platform | Account, business, sign-in and usage data | Performance of our contract with you |
| Take payment and send invoices | Billing data | Performance of our contract with you |
| Send service emails: receipts, trial and renewal reminders, security alerts, notice of changes to our terms | Email address, account data | Performance of our contract with you |
| Verify the businesses that sell on the Platform | Verification data | Legitimate interests: keeping unlawful sellers off the Platform, which protects shoppers, other labs, and our standing with our own providers |
| Keep the Platform and its stores secure, and prevent fraud and abuse | IP addresses, request logs, sign-in records, audit logs | Legitimate interests: protecting the service and the people who use it |
| Provide the AI features you choose to use | What you send to them | Performance of our contract with you |
| Connect the services you choose to connect | Identifiers and access tokens | Performance of our contract with you |
| Register a domain you buy | Registrant details | Performance of our contract with you |
| Deliver a branding package | Brief, files, correspondence | Performance of our contract with you |
| Answer messages and provide support | Your message and contact details | Performance of our contract with you, or, if you are not a customer, legitimate interests: answering the people who write to us |
| Improve the Platform | Usage data, in aggregated form | Legitimate interests: knowing which features are used, so that we build the right ones |
| Send news and offers | Email address | Consent, which you can withdraw at any time |
| Keep accounting and tax records | Billing records | Legal obligation, under tax and company law |
| Record that you accepted our terms, enforce them, and establish or defend legal claims | Acceptance records, account data, correspondence | Legitimate interests: being able to show what was agreed |
| Respond to courts, regulators and law enforcement | What the request lawfully requires | Legal obligation |
- Create and run your account and provide the Platform
- Data used
- Account, business, sign-in and usage data
- Lawful basis
- Performance of our contract with you
- Take payment and send invoices
- Data used
- Billing data
- Lawful basis
- Performance of our contract with you
- Send service emails: receipts, trial and renewal reminders, security alerts, notice of changes to our terms
- Data used
- Email address, account data
- Lawful basis
- Performance of our contract with you
- Verify the businesses that sell on the Platform
- Data used
- Verification data
- Lawful basis
- Legitimate interests: keeping unlawful sellers off the Platform, which protects shoppers, other labs, and our standing with our own providers
- Keep the Platform and its stores secure, and prevent fraud and abuse
- Data used
- IP addresses, request logs, sign-in records, audit logs
- Lawful basis
- Legitimate interests: protecting the service and the people who use it
- Provide the AI features you choose to use
- Data used
- What you send to them
- Lawful basis
- Performance of our contract with you
- Connect the services you choose to connect
- Data used
- Identifiers and access tokens
- Lawful basis
- Performance of our contract with you
- Register a domain you buy
- Data used
- Registrant details
- Lawful basis
- Performance of our contract with you
- Deliver a branding package
- Data used
- Brief, files, correspondence
- Lawful basis
- Performance of our contract with you
- Answer messages and provide support
- Data used
- Your message and contact details
- Lawful basis
- Performance of our contract with you, or, if you are not a customer, legitimate interests: answering the people who write to us
- Improve the Platform
- Data used
- Usage data, in aggregated form
- Lawful basis
- Legitimate interests: knowing which features are used, so that we build the right ones
- Send news and offers
- Data used
- Email address
- Lawful basis
- Consent, which you can withdraw at any time
- Keep accounting and tax records
- Data used
- Billing records
- Lawful basis
- Legal obligation, under tax and company law
- Record that you accepted our terms, enforce them, and establish or defend legal claims
- Data used
- Acceptance records, account data, correspondence
- Lawful basis
- Legitimate interests: being able to show what was agreed
- Respond to courts, regulators and law enforcement
- Data used
- What the request lawfully requires
- Lawful basis
- Legal obligation
Where we rely on legitimate interests, we have weighed our interest against your rights and concluded that it is not overridden: each use is narrow and expected. You can object to any of them, and we will stop unless we have compelling grounds to continue. See your rights.
5.Marketing#
We send news and offers by email only to people who have opted in, and every message has a one-click unsubscribe. Service emails about your account, billing or security are not marketing, and you receive them for as long as you have an account.
8.Where your data goes#
We keep account data in the United Kingdom (London). Each lab's store, with its own database, files and backups, is hosted in the European Union (Germany or Finland) by default, or the United States for a store hosted there. Some of our providers are based in the United States or process data there, including Vercel, Hetzner, Amazon Web Services, Resend, Stripe, Anthropic and Google, as the Sub-processors page shows. We would rather say that plainly than describe the stack as if it were all local.
When personal data leaves the UK, we rely on a safeguard UK data protection law allows: UK adequacy regulations (which cover the EEA, among others), the UK Extension to the EU-US Data Privacy Framework where the recipient is certified under it, or the International Data Transfer Agreement or the UK Addendum to the EU Standard Contractual Clauses, together with a transfer risk assessment. You can ask us for a copy of the safeguard that applies to a particular provider.
9.How long we keep it#
We keep personal data only as long as we have a reason to, and then delete it. A fixed period runs from when the reason for keeping the data ends: the account closing, the conversation ending, or the financial year closing.
| What | How long | Why that long |
|---|---|---|
| Account and business details, staff accounts, connected-service tokens | While the account is open, then deleted within 60 days after your subscription ends, and deleted from backups within 35 days after that | You can still sign in and export for 30 days after you leave |
| Billing records and invoices | 6 years from the end of the financial year they belong to | HMRC and company law require us to keep accounting and VAT records |
| The record that you accepted our terms (which version, when, and from which IP address) | 6 years after your account closes | The time within which a claim about the contract can be brought |
| Business verification documents | While the account is open, and 12 months after it closes | To answer questions from payment providers, regulators or authorities about a store we hosted |
| Sign-in sessions (IP address, browser) | Until the session expires or you sign out | They exist to keep you signed in |
| Security and audit logs (sign-ins, plan changes, staff and API key changes) | 12 months | Long enough to investigate an incident that is noticed late |
| Web server request logs | Up to 30 days | Finding faults and blocking attacks |
| Support emails and messages | 24 months after the conversation ends | Context for a later question about the same thing |
| Enquiries from people who did not sign up | 12 months after the last message | Long enough to pick up a conversation again |
| Branding package briefs and files | While the account is open, then deleted with it | So that the work can be revised or reused for your store |
| Content sent to AI features | Kept in your store only if you save it. Our AI provider keeps it for a limited period under its commercial terms, for safety monitoring, and then deletes it | Providing the feature you asked for |
| Marketing consent, and the record that you unsubscribed | Until you unsubscribe; the unsubscribe record is then kept indefinitely | The only way to honour an opt-out is to remember it |
- Account and business details, staff accounts, connected-service tokens
- How long
- While the account is open, then deleted within 60 days after your subscription ends, and deleted from backups within 35 days after that
- Why that long
- You can still sign in and export for 30 days after you leave
- Billing records and invoices
- How long
- 6 years from the end of the financial year they belong to
- Why that long
- HMRC and company law require us to keep accounting and VAT records
- The record that you accepted our terms (which version, when, and from which IP address)
- How long
- 6 years after your account closes
- Why that long
- The time within which a claim about the contract can be brought
- Business verification documents
- How long
- While the account is open, and 12 months after it closes
- Why that long
- To answer questions from payment providers, regulators or authorities about a store we hosted
- Sign-in sessions (IP address, browser)
- How long
- Until the session expires or you sign out
- Why that long
- They exist to keep you signed in
- Security and audit logs (sign-ins, plan changes, staff and API key changes)
- How long
- 12 months
- Why that long
- Long enough to investigate an incident that is noticed late
- Web server request logs
- How long
- Up to 30 days
- Why that long
- Finding faults and blocking attacks
- Support emails and messages
- How long
- 24 months after the conversation ends
- Why that long
- Context for a later question about the same thing
- Enquiries from people who did not sign up
- How long
- 12 months after the last message
- Why that long
- Long enough to pick up a conversation again
- Branding package briefs and files
- How long
- While the account is open, then deleted with it
- Why that long
- So that the work can be revised or reused for your store
- Content sent to AI features
- How long
- Kept in your store only if you save it. Our AI provider keeps it for a limited period under its commercial terms, for safety monitoring, and then deletes it
- Why that long
- Providing the feature you asked for
- Marketing consent, and the record that you unsubscribed
- How long
- Until you unsubscribe; the unsubscribe record is then kept indefinitely
- Why that long
- The only way to honour an opt-out is to remember it
Store Data, including shoppers' personal data, belongs to the lab and follows the timetable in our Terms of Service: available to export for 30 days after a subscription ends, deleted from live systems within 30 days after that, and its backups deleted or made permanently unreadable within 35 days after that.
10.How we protect it#
- Everything is served over HTTPS, and our database provider encrypts account data at rest.
- Passwords are stored only as salted hashes, so a forgotten password is reset, never recovered.
- Card details never reach our servers: Stripe handles them.
- Each lab's store runs as its own deployment with its own database, so one store cannot read another's data.
- Access to production systems is limited to the people who run the Platform, and protected by multi-factor authentication.
- Credentials and keys are kept in our providers' secret stores, never in source code.
No system is perfectly secure. If a breach puts your rights at risk, we will tell the Information Commissioner's Office within 72 hours of finding out, and tell you without undue delay where the risk to you is high.
11.Your rights#
Under UK GDPR you can ask us to:
- give you a copy of the personal data we hold about you, and tell you what we do with it;
- correct anything inaccurate or incomplete (much of it you can edit yourself in your account);
- delete it, where we no longer need it. We cannot delete billing records before the period tax law sets, and we will say so rather than pretend otherwise;
- restrict how we use it while a dispute about it is resolved;
- object to any use we base on legitimate interests, and to marketing at any time;
- move the data you gave us to another service, in a machine-readable format;
- withdraw consent where we rely on it. Withdrawing does not undo what was lawful before.
Email hello@my-pepts.com. We complete a request within one month, which the law lets us extend by up to two further months for a complicated one. There is no charge. We may ask you to confirm your identity, and we ask only for what we need to be sure.
12.Complaints#
If you are unhappy with how we have handled your data, tell us first at hello@my-pepts.com. We acknowledge a complaint within 30 days, look into it, and tell you the outcome without undue delay.
You also have the right to complain to the UK's data protection regulator at any time: Information Commissioner's Office, Wycliffe House, Water Lane, Wilmslow, Cheshire SK9 5AF, helpline 0303 123 1113, ico.org.uk/make-a-complaint.
13.Children, automated decisions and changes#
Children. My-Pepts is for businesses and is not for anyone under 18. We do not knowingly collect data about children; if you think we have, tell us and we will delete it.
Automated decisions. We do not make decisions about you based solely on automated processing that have legal or similarly significant effects. A person reviews every decision to refuse, suspend or close an account.
Changes. We update this policy when what we do changes, and the date at the top is the date it last changed. If a change is significant, we email account holders rather than relying on you to check.
Company details
- Company
- Demirius Ltd, trading as My-Pepts
- Registered in
- England and Wales
- Company number
- 16820023
- Registered office
- 47 Cranwell Crescent, Eaton Leys, Milton Keynes, MK17 9GS, England
- VAT number
- GB 505 3821 14
- hello@my-pepts.com
Last updated