← Back
Privacy,
Privacy,
kept practical.
Agency customer content stays tenant-isolated and is used only to run your workflow.
What we collect
Only what we need to run the product and support the workflow.
- Waitlist or support contact details you choose to provide.
- Briefs, uploaded references, generated drafts, comments, and approval telemetry inside Narraplex.
- Operational logs and service analytics used for reliability, abuse prevention, and support.
What we do not do
The defaults are designed for procurement conversations, not growth hacks.
- We do not scrape social accounts for the core product workflow.
- We do not use customer content or edits to train centralized foundation models.
- We do not mix learning signals across client workspaces.
- We do not ask for social passwords or unnecessary private communications access.
How workspace learning works
Learning is local to the workspace that generated the signal.
- Behavioral improvements come from what your team or client approves, edits, or rejects in the workflow.
- Off-platform feedback only becomes a product signal if your team logs it back into Narraplex.
- Structured learning stays attached to that workspace rather than becoming cross-tenant training data.
Retention & deletion
Delete and export paths matter for agencies with procurement requirements.
- Retention windows can be set to fit the account and client sensitivity level.
- Delete and export are supported at the workspace level.
- Raw archives can use short-retention defaults while approved workflow history stays scoped to the tenant.