Privacy Policy
What we hold, why we hold it, how long for, and how to make us delete it. Last updated 21 September 2026.
The controller
CFBM Management Services is the trading name of CORE-FBM MANAGEMENT LTD, registered in England and Wales, company number 17168590, registered office 82A James Carter Road, Mildenhall, Suffolk, IP28 7DE. We are the data controller for everything described here. For anything at all to do with this policy, write to info@corefbm.com.
This covers three places: this website, the client portal at portal.corefbm.com, and the records we keep to run the work itself. Most privacy notices only describe the first of those. Ours describes all three, because the second and third are where the information that actually matters lives.
An enquiry, and nothing else
The forms here ask for a first name, a last name and an email address, and give you a message box. We also record which page the form was sent from, so an enquiry arrives with the context of what you were reading. Our server keeps ordinary web logs, which include IP addresses, for security and troubleshooting.
corefbm.com carries no analytics, no advertising pixel and no third-party script of any kind, and sets no cookie. There is no cookie banner because there is nothing to consent to. Every asset the site loads comes from corefbm.com, which is enforced by a content security policy rather than being a promise you have to take on trust.
Rather more, and worth reading
Contact and company details. A name, a company name, an email address, a phone number and a billing address. Where two people are named on one account, both.
Identity documents. Adult platforms require the people involved to be identified and age-verified, so we ask for photo identification during onboarding and hold it. It is deleted automatically five years after upload, by a job that runs on its own rather than waiting for someone to remember.
Your agreement. The signed document, plus the signature itself, the date and time, the IP address it was signed from and the browser it was signed in. Those last three are what makes a signature evidence rather than a picture, and they are kept for as long as the agreement could be disputed.
Account credentials. For account management and messaging, the software the desk runs on signs in as the creator, so we hold the login. It is encrypted at rest with a per-record key rather than stored as text. You can change the password yourself at any moment without asking us, and we would tell you to.
What the account does. Earnings, subscriber counts and message activity, read from the platform so we can report on it and invoice correctly. Where a platform sends us a subscriber's details as part of a message or a transaction, that reaches us too, and we hold it only as long as running the account requires.
Email. Messages you send us, and our replies.
None here, one in the portal
This website sets no cookie. The client portal sets a single session cookie so that signing in works, which is strictly necessary for a service you asked for and needs no consent under PECR. It carries a random session identifier and nothing else, it is not shared with anybody, and it is gone when you sign out.
Lawful bases
Replying to an enquiry you started is legitimate interest. Everything to do with an engagement is performance of a contract. Identity documents and invoicing records are legal obligation, the first because platforms and the law require age and identity checks and the second because HMRC requires books. Newsletter email is consent, given by ticking a box yourself, and withdrawn by one click in any email we send.
Retention, with actual numbers
Enquiries that go nowhere: twelve months. Identity documents: five years from upload, then deleted automatically. Invoices, agreements and anything else with a tax consequence: six years after the relationship ends, because UK law requires it. Account credentials: deleted when the engagement ends, and you should change the password as well rather than take our word for it. Server logs: weeks, not years.
Processors, and where they are
The website is served by Cloudflare. The application behind it runs on Fly.io in London. Email reaches us through Google Workspace and Amazon SES. Each is a processor acting on our instructions and none is given your data for their own purposes. Fly.io and Amazon are US companies, so some data may be processed outside the UK under the UK extension to the EU-US Data Privacy Framework or standard contractual clauses. We do not sell anything to anybody and we do not share your data with other creators or clients.
What is actually in place
Everything is served over HTTPS. Staff accounts carry two-factor authentication. Credentials are encrypted at rest. Staff access is scoped by role, so not everyone can see everything, and the client-facing portal cannot reach the staff side at all. No arrangement is perfect and we will tell you promptly if something goes wrong that affects you.
What you can ask for
You can ask what we hold, ask for it to be corrected, ask for it to be deleted, ask us to stop using it, object to a particular use, or ask for a copy in a portable form. Email info@corefbm.com and we will answer within one month. Some of it we cannot delete on request, and we would rather say so than pretend otherwise: an invoice inside the six-year window, and an identity document inside its retention period, both have to stay.
If you think we have handled your data badly, you can complain to the Information Commissioner's Office at ico.org.uk. We would rather you told us first so we can put it right.