Privacy
Privacy declares each Purpose for personal data, records Consent, answers access requests, masks data on request, and publishes its privacy notices.
Privacy declares each Purpose a Startup uses personal data for, records Consent, answers access requests, masks data on request, and publishes the notices. Data is masked, never deleted, so what was done stays provable.
Summary
| Part | This System |
|---|---|
| Group | Customers and identity |
| Status | Beta: it works, and its Verbs may still change |
| Shelf | Wakes: offered once its Event fires |
You can ask:
- “Delete everything we hold about this person”
- “What data do we keep on this customer?”
- “Add a cookie banner”
- “Stop using this person’s data for marketing”
What you get
| Part | This System |
|---|---|
| Starts | On for every Startup at creation, with nothing to install. |
| Wakes | On Visitor.identified when the Startup records its first known person. |
| Built from | Database, Event streams, Workflows, Encryption |
Nouns it owns
| Noun | Definition |
|---|---|
| Purpose | A Purpose is a named reason personal data is processed, with a lawful basis per jurisdiction. |
| Consent | A Consent is a person’s grant for one Purpose, with its basis, region, notice, evidence, and expiry. |
Verbs
| Verb | Object | Approval | Event |
|---|---|---|---|
| Purpose.create | Purpose | None | Purpose.created |
| Consent.create | Consent | None | Consent.created |
| Consent.update | Consent | None | Consent.updated |
Events
| Direction | Event | How |
|---|---|---|
| Emits | Purpose.created | By Purpose.create |
| Emits | Consent.created | By Consent.create |
| Emits | Consent.updated | By Consent.update |
States
None.
Who operates it
| Part | This System |
|---|---|
| Accountable | Privacy Officer |
| Team | Legal Team |
| Seat | A role agent holds it until a Human is seated. |
| Autonomy | assist |
| Also calls its Verbs | Success Manager, Legal Lead |
Approvals and limits
None.
Processes that use it
| Process | How it uses it |
|---|---|
| Contracting | A step calls Purpose.create |
| Privacy | A step calls Consent.update |
| Retention | A step calls Consent.create |
Rail underneath
None.
Views and dashboards
| View | Shows | Metrics |
|---|---|---|
| The Privacy Officer’s view | The Metrics its accountable Role answers for. | Privacy requests on time |
Access
What each Access level may call here.
| Access level | May call |
|---|---|
owner | Every Verb (9) |
admin | Every Verb (9) |
member | Every Verb (9) |
viewer | Read only (4 of 9) |
Import and export
None.
Fees and pricing
None.
Availability and limits
| Part | This System |
|---|---|
| Status | Beta: it works, and its Verbs may still change |
Compliance notes
Each request is answered inside its legal deadline, and data is masked across every System; the Purposes declared stay the founder’s.
Controls it carries:
- Log completeness
- Encryption
- Append-only records
- Breach notification
- Point-in-time recovery
- Processing definitions
- Action completion
- Privacy notice
- Lawful basis
- Purpose limitation
- Retention restriction
- Privacy requests
- Disclosure record
- Records of processing
Related Systems
Example
A b2c SaaS for journaling gets an erasure request from a user in the EU. Privacy masks that user’s data in every System, keeps proof of the request, and confirms within the legal deadline. The Privacy Officer Agent sees the request closed without touching it.