> ## Documentation Index
> Fetch the complete documentation index at: https://docs.myclerkbook.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Compliance

> POPIA and GDPR posture, stated plainly and without borrowed credentials.

myClerkBook is built in South Africa and designed against **POPIA** and
**GDPR** from the schema up rather than bolted on afterwards.

## What that means

<CardGroup cols={2}>
  <Card title="Data minimisation" icon="filter">
    We collect what the product needs to work, and the largest category, your
    financial records, is the thing you came here to store.
  </Card>

  <Card title="Purpose limitation" icon="crosshairs">
    Your books are used to show you your books. They are not sold, not shared
    with advertisers, and not used as training data.
  </Card>

  <Card title="Access is enforced, not promised" icon="lock">
    Every row is scoped to its owner by the database, not by application code
    remembering to filter.
  </Card>

  <Card title="Deletion is real" icon="eraser">
    Hard delete, with no retained shadow copy.
  </Card>
</CardGroup>

## What we do not claim

<Warning>
  **myClerkBook holds no compliance certification.** There is no SOC 2 report,
  no ISO 27001 certificate and no third-party audit behind this page. Designing
  against a framework is not the same as being certified against one, and
  saying otherwise would be the exact kind of borrowed credibility this product
  is built to avoid.
</Warning>

What we can say is checkable: there is no bank connection, no aggregator, no
card data, no session recording and no stored IP address. Each of those is a
statement about what the system is capable of, which is a stronger guarantee
than a statement about how carefully it is operated.

## Your rights under both frameworks

| Right                     | How it is served                                                |
| ------------------------- | --------------------------------------------------------------- |
| Access                    | Your data is visible to you in the product at all times         |
| Portability               | Plain CSV, on both plans, by request at `legal@myclerkbook.com` |
| Rectification             | Every record is editable by you                                 |
| Erasure                   | Delete a record, or close the account entirely                  |
| Objection and restriction | [Email us](mailto:legal@myclerkbook.com)                        |

See [Data retention and deletion](/privacy-and-security/data-retention-and-deletion)
for how each of these works in practice.

## Sub-processors

myClerkBook relies on a small number of providers to operate: hosting,
authentication, the database, payments, email and product analytics. Each holds
only the category of data its function requires. The payment provider holds
card details and we do not; we hold your books and it does not.

The current list is maintained in the
[Privacy Policy](https://myclerkbook.com/legal/privacy), which is the
authoritative version.

## Not accounting software

<Note>
  myClerkBook is a book of account for your own record-keeping. It is not
  double-entry accounting software and does not produce statutory financial
  statements. Nothing here is tax or accounting advice.
</Note>

<Card title="Back to the privacy architecture" icon="arrow-left" href="/privacy-and-security/our-privacy-architecture">
  The three layers, and the capability that does not exist.
</Card>