Privacy

Cedria stores the data needed to run campaign workflows: account/workspace records, campaigns, tasks, content, assets, review packages, stakeholder contacts, comments, notifications, activity, reports, feedback, and operational logs.

Account and workspace records include user identity information from the authentication provider, workspace membership, roles, invites, notification preferences, timezone preferences, and workspace settings.

The app stores campaign plans, tasks, content schedules, asset records, review packages, stakeholder responses, reminders, feedback resolution status, reports, launch readiness, budgets, risks, issues, decisions, experiments, and learnings.

Asset file uploads are stored through the configured storage provider. The app tracks file names, versions, metadata, and review context. It does not expose raw storage paths in public pages or exports.

Stakeholder contacts may include names, email addresses, companies, roles, and review-related status. Review invitation emails and reminders use selected contact data to deliver review links.

The app stores email logs, delivery events, and suppressions for digests, invitations, reminders, and delivery safety. Suppression data helps avoid sending to bounced or complained addresses.

Payments, payment methods, invoices, and subscription management are handled by Stripe-hosted flows when billing is configured. Campaign Studio OS stores billing state such as plan, subscription status, and related Stripe identifiers needed to sync workspace billing.

Private preview feedback, tester onboarding records, first-party error logs, and first-party usage events help improve product quality. These records may include route, workspace, user, email, company, role, category, status, and sanitized metadata. They should not include secrets, raw tokens, signed URLs, storage paths, or long private content bodies.

Public review and client portal links are token-based access points for selected review-facing campaign content. They are designed not to expose internal tasks, budgets, risks, reports, private comments, or admin analytics.

Workspace owners/admins can export workspace data from data controls. Exports are designed to exclude raw tokens, signed URLs, storage paths, provider secrets, service keys, and webhook payloads.

Demo data can be cleared, and many records can be archived. Automated permanent workspace deletion, self-serve account deletion, and formal retention policies are not implemented yet.

This is an early-access product. Avoid storing highly sensitive production data until final production policies, legal documents, account lifecycle workflows, and operational practices are in place.

Use in-app feedback or contact the project owner with questions about private preview data handling. Do not send secrets, raw tokens, or sensitive production data in support messages.

July 14, 2026