Data processing addendum
How Fabulous Limited processes personal data on behalf of a host running a community on success.digital.
Last updated 14 September 2026
It is a draft. 4 details are still outstanding, and it has not been reviewed by a lawyer. Do not rely on it.
- State of incorporation — The governing law and the courts a dispute is heard in.
- Registered address — A contract has to name the party it binds.
- Contact address for notices — Where a customer sends a legal notice or a termination.
- Contact address for data requests — Where a member sends an access, correction or deletion request.
How it fits
This addendum forms part of the terms of service. Where the two disagree about personal data, this one wins.
Roles
The host is the controller: they decide what their community collects and why. We are the processor: we hold and handle it on their documented instructions, which are the terms, this addendum, and the settings the host chooses in the product.
What is processed, and for whom
| Subject matter | Running a community on success.digital |
|---|---|
| Duration | While the host’s account is open, then thirty days |
| Nature and purpose | Storage, retrieval, display and delivery of community content and membership |
| Types of personal data | Email address, display name, profile picture and cover, biography, links, community and room membership, posts, discussions, replies, comments, direct messages, events and RSVPs, course enrolment and progress, moderation records |
| Categories of data subject | The host, their members, and visitors to a public community |
| Special category data | None is required by the product. A member may write anything in a post, so a host whose community is about health, belief or politics should assume it is present and say so in their own notice. |
Our obligations
- Process personal data only on the host’s instructions, and tell them if we believe an instruction breaks the law.
- Keep it confidential, and bind anyone with access to the same.
- Hold the security measures below, and not reduce them.
- Help the host answer a data subject’s request, and help with an impact assessment or a regulator.
- Tell the host without undue delay if personal data is breached, with what we know and what we are doing.
- Delete or return the data at the end, as set out below.
- Make available what the host needs to show we are meeting this, and allow an audit no more than once a year on reasonable notice.
Security
- Access is enforced by the database, not by the pages. Every table carries row-level security, so a request that should return nothing returns nothing whatever asks it. It is verified by impersonating each party in a rolled-back transaction rather than by reading the code.
- Encryption in transit (TLS) and at rest.
- Passwords hashed by the authentication provider and never visible to us.
- Private file storage reached only through short-lived signed links.
- Rate limits on every member-writable table, so one account cannot flood a community.
- An audit record of moderation and of every platform-administrator visit, visible to the host.
- Daily backups, retained thirty days.
Subprocessors
The host consents to these, and we will give notice before adding another:
| Who | What they do | Where |
|---|---|---|
| Supabase | Database, file storage, authentication | Mumbai, India (AWS ap-south-1) |
| Vercel | Application hosting and delivery | Global edge network; requests are served from the nearest region |
| SocketLabs | Sending notification and transactional email | United States |
Transfers
Fabulous Limited is a United States company and the data is held in Mumbai, India. For a host or member in the European Economic Area or the United Kingdom that is a restricted transfer, and the European Commission’s standard contractual clauses (module three, processor to processor, and module two where we act for a controller) apply and are incorporated here.
Data subject requests
The product answers most of these without us: a member can export everything they wrote and every record about them, leave a community, or delete their account, from their own settings. A host can export their community. Where a request needs us, we help the host rather than answering their member directly.
Return and deletion
On termination the host may export their community for thirty days. After that we delete it. Backups containing it roll off within thirty days of deletion.
Liability
The limits in the terms of service apply to this addendum.