Privacy Notice
A draft skeleton. It sets out the structure a finished notice will follow and describes no processing that has been verified. Do not rely on anything on this page.
Draft
This Privacy Notice is a draft, not a published agreement
The sections below set out the structure a finished Privacy Notice will follow. They are placeholders describing intended scope. Nothing on this page is a term, a commitment or a representation, and no part of it is currently in force.
A qualified legal professional must draft and review this document before EQ Books is offered commercially. Until that review is complete and a dated version is published here, do not rely on anything on this page.
Who is responsible for your data
Will name the entity that determines how personal data is processed, and distinguish two very different roles EQ Books plays.
- Controller entity: [REGISTERED NAME AND ADDRESS]
- Data protection contact: [PRIVACY EMAIL]
- The distinction between data about the customer’s own users, and data the customer uploads about its employees and counterparties where EQ Books acts on the customer’s instructions
What data is collected
Will enumerate categories rather than gesture at them, because a category omitted here is a category processed without notice.
- Account and identity data from the sign-in provider
- Company and ledger records the customer enters
- Employee records used for payroll, including statutory identifiers and bank details
- Uploaded documents and statements
- Technical and diagnostic data produced by using the service
Where the data comes from
Will distinguish data given directly from data received about someone.
- Entered by the customer or its users
- Received from the identity provider on sign-in
- Contained in documents and statements the customer uploads
- What the customer must tell its own employees before entering their data
Why it is processed, and on what basis
Will pair each purpose with a lawful basis. The pairing must be reviewed against the jurisdictions EQ Books is offered in.
- Providing the service, and performing the contract
- Security, abuse prevention and integrity of the ledger
- Legal and accounting record-keeping obligations
- Product communication, and where consent is required for it
- Lawful basis mapping: [TO BE ADVISED]
Employee and financially sensitive data
Payroll brings statutory identifiers and bank details into the system, which deserves its own section rather than a line in a list.
- Which identifiers are stored, and that they are held as ciphertext with only a masked fragment readable
- Who inside a customer’s company can see them
- The customer’s obligations as the employer of the people concerned
Sub-processors and disclosure
Will publish a maintained list. A privacy notice that names no processors while the product runs on hosted infrastructure is not accurate.
- Hosting, identity and any analytics or support tooling in use
- How a change of sub-processor is notified
- Disclosure compelled by law, and notice where notice is permitted
Where data is stored and transferred
Will state locations and the mechanism for any transfer out of them.
- Processing region: [REGION]
- Transfer mechanism, where one is required: [TO BE ADVISED]
How long it is kept
Retention is unusually delicate in an accounting product: the ledger is append-only, so a correction adds a reversing entry instead of erasing a record, and statutory retention periods may require records be kept even when deletion is requested.
- Retention period per data category: [NOT SET]
- How deletion requests interact with the append-only ledger
- Backup retention and the lag before deletion propagates
How it is protected
Will summarise the controls in place and link out rather than duplicate them. The mechanisms that exist today are described in detail on the security page, including what is not claimed: EQ Books holds no security certifications.
- Identity verification, per-company scoping and encryption of sensitive fields
- Breach notification timelines and the route by which notice is given
Your rights
Will set out the rights available and how to exercise them, including the case where the request should go to the employer rather than to EQ Books.
- Access, correction, deletion, portability, restriction and objection
- Withdrawing consent where processing relies on it
- How to make a request: [PRIVACY EMAIL]
- Response timeframe and identity verification for requests
Cookies and similar technologies
Will describe what is set, by whom and why, and must be written from an actual audit of the running site rather than from a template.
- Strictly necessary storage used to keep a session signed in
- Any analytics or measurement, and the consent mechanism if introduced
Children's data
Will state that EQ Books is a business product not directed at children, and what happens if such data is discovered in an account.
Changes to this notice
Will explain how updates are published and communicated.
- Effective date and version history
- Notice given for material changes
Contact and complaints
Will give a route to raise a concern, and the regulator to escalate to if the answer is unsatisfactory.
- Privacy contact: [PRIVACY EMAIL]
- Supervisory authority: [REGULATOR]
- General contact routes are listed on the contact page, where every address is also still a placeholder