Data Processing Addendum (draft outline)
Updated October 10, 2026
Draft — pending legal review; not yet in effect
This document is a working draft prepared for counsel. It may change before launch and is not yet in effect.
Draft for legal review — not in effect.
Structured outline for counsel. The facts come from the code and data model; [COUNSEL: …] marks legal drafting and [Eng: …] marks product gaps.
1. Parties and roles
- Processor:
[COUNSEL: legal entity]. Controller: the customer (workspace owner organization). - Agencies: an agency workspace can manage client workspaces.
[COUNSEL: whether the agency is controller or processor for client data, and the chain to InfluenceBot].
2. Subject matter, nature and purpose
- Hosting and processing of customer content to provide brand knowledge, persona creation, AI generation, editing, review, approvals, publishing, analytics, automation, lead capture, attribution and reporting.
3. Categories of data subjects
- Customer's members (users of a workspace).
- Real people portrayed by a digital twin, with recorded consent.
- People quoted in customer testimonials.
- Leads who submit public lead forms.
- Visitors who click tracking or affiliate links (pseudonymized).
- Social media users who comment, message or mention the customer's accounts (inbox and listening, where a network supports it).
- Customer's staff named in imported website pages or documents.
4. Categories of personal data
- See Privacy policy section 2.4–2.6. Special categories: likeness (face images) and voice of a consented real person may be biometric data in some jurisdictions.
[COUNSEL: assess; the product stores reference images and may compute identity embeddings for consistency scoring].
5. Duration and deletion
- Retention behaviour in code is listed in the privacy outline section 7.
[Eng: no workspace deletion, account deletion or bulk export exists today; the DPA's return-and-delete clause needs that tooling or a documented manual procedure with a deadline].
6. Processor obligations
[COUNSEL: instructions, confidentiality of personnel, assistance with data-subject requests and DPIAs, breach notification deadline, audits].- Product facts that support assistance: per-purpose lead consent records with withdrawal; persona consent records with revocation; audit log of actions in each workspace.
7. Technical and organizational measures (facts)
- Tenant isolation: every tenant query is scoped by workspace in the data-access layer; cross-tenant tests are part of the test suites.
- Encryption: TLS in transit; database connections over TLS; OAuth tokens, social tokens, AI provider keys (sealed), webhook secrets, commerce credentials, two-factor secrets and SSO secrets encrypted at rest; passwords hashed; API keys and emailed-link tokens stored as hashes.
- Access control: role-based permissions per workspace with custom roles; enterprise SSO, enforced SSO, verified domains, IP allow-list and SCIM deprovisioning (Beta).
- Platform staff access: time-limited, scoped access grants tied to a service order or support ticket, with reason, expiry, revocation and audit. Impersonation sessions record who impersonated and until when.
- Logging: append-only audit log; webhook deliveries signed and logged.
- Upload safety: file type checks; an antivirus hook exists, but no scanner is configured, so uploads are recorded as not scanned unless the operator requires scanning.
[Eng: configure a scanner before launch]. - Outbound fetches (website reading, product pages, webhooks) refuse private network addresses and respect robots.txt where applicable.
- Backups and recovery:
[Founder: Cloud SQL automated backups and point-in-time recovery — launch checklist 2.5].
8. Sub-processors
- See Sub-processors.
[COUNSEL: general authorization, notice period, objection right].
9. International transfers
[COUNSEL: SCCs / UK addendum / other mechanisms; Founder to confirm hosting regions].
10. Liability and order of precedence
[COUNSEL].
