PMAPP
Placeholder. This page has the structure a real policy needs but not binding legal text — see the TODOs in each section. Do not treat this as a published policy until reviewed by counsel.

Privacy Policy

Last updated: TBD (placeholder date)

1. Overview

TODO: standard intro -- who this policy covers (hosted PMAPP customers; self-hosted deployments are the operator's own responsibility), scope.

2. Information we collect

Based on what the product actually stores today:

  • Account info: name, email, username, avatar
  • Workspace content: projects, boards, cards, comments, attachments, labels
  • Usage/activity: the audit log, notifications, session records
  • AI interactions where enabled: chat/voice messages sent to the assistant, and any images/audio/documents you ask it to ingest
TODO: confirm this list against the current schema before publishing, and add anything collected outside the app itself (e.g. server logs, error reporting if enabled).

3. How we use information

TODO: standard purposes -- providing the service, sending the notifications you've opted into, security/audit logging, improving the product.

4. AI processing and subprocessors

When the AI assistant is enabled for a workspace, the content needed to answer a request (board/card data, or a message you send it) is sent to a third-party AI provider. As configured in this codebase today, that can include Anthropic, OpenAI, and ElevenLabs (for text-to-speech). These providers process that content to generate a response; PMAPP does not control their retention independently of what their own terms specify.

TODO: confirm the current provider list against production config, link each provider's DPA, and state whether any provider is used for model training (typically opt-out via enterprise API terms -- confirm, don't assume).

5. Data retention

TODO: retention periods per data type. Audit log retention is plan-dependent already (see /pricing) -- 90 days (Team), 365 days (Studio), custom (Enterprise); other data types (e.g. deleted-card/attachment retention, backups) still need a stated policy.

6. Data sharing

TODO: who data is shared with beyond the AI subprocessors above (payment processor once Stripe is live, email/SMTP provider, hosting infrastructure) and under what conditions (legal requests, etc).

7. Your rights

TODO: GDPR/CCPA rights (access, correction, deletion, portability) -- account deletion and data export are listed as not-yet-built in docs/COMMERCIALIZATION_PLAN.md's Productionization section, so this section can't promise more than the product currently supports.

8. Cookies

The web app sets a session cookie (accessToken) to keep you signed in. No analytics or advertising cookies are set today -- no analytics provider is wired into this codebase yet.

TODO: revisit this section (and add a cookie-consent mechanism) the moment an analytics provider is actually added -- see the open "Analytics" item in docs/plans/marketing-site-plan.md.

9. Data security

TODO: standard security-measures statement.

10. Children's privacy

TODO: standard age-restriction statement.

11. International data transfers

TODO: where data is actually hosted; transfer mechanism if applicable.

12. Changes to this policy

TODO: standard notice-of-changes language.

13. Contact

TODO: same placeholder address as /contact -- confirm the real one before publishing.