YOUR DATA, EXPLAINED

Privacy, in plain language.

How information is used in a Planvyra workspace, what you can control, and where to ask questions.

Draft for review · No effective date set

Draft — pending approvalThis policy is a draft for review and is not a final privacy notice. The operating company, legal basis, retention periods, hosting regions, transfer safeguards, and privacy contact must be confirmed before it is published as an effective policy.

1. About this policy

Planvyra is a collaboration service for projects, tasks, documents, and team conversations. This draft describes the current application’s data handling. The operator’s registered legal name, address, applicable jurisdiction, and effective date have not yet been confirmed.

If your employer or another organisation provides your workspace, its administrators manage membership and project access. That organisation may have its own privacy policy and responsibilities for information uploaded to the workspace.

2. Information the service handles

  • Account information: your name, email address, password hash, profile information, and authentication settings.
  • Workspace content: projects, tasks, comments, chat messages, documents, files, memberships, and activity records you or your collaborators create.
  • Technical information: session identifiers, device or browser information, IP addresses used by authentication controls, and operational logs.
  • Optional services: notification destinations, browser push subscriptions, and information required by integrations you choose to connect. Billing records are used when a paid service is enabled.

3. Why information is used

The application uses this information to sign you in, enforce access permissions, store and display your work, support collaboration, deliver configured notifications, and investigate service problems. An enabled integration may receive the information needed to carry out the action you request.

The final policy must identify the operator’s legal basis for each processing purpose, any applicable legitimate interests, and any optional processing that requires consent.

4. Who can receive information

Content is available to workspace participants according to their access permissions and to authorised administrators. Hosting and storage providers process the data needed to run the service. Configured email, browser push, payment, and integration providers may process the information needed for their respective services.

The final provider list, processing locations, international transfer safeguards, and administrative access procedures must be confirmed for the production deployment. Connecting an external AI or MCP tool may disclose project content to that tool under the access you grant.

5. Browser storage and preferences

The application uses browser storage to retain sign-in tokens and interface preferences. This public website remembers your motion preference in local storage. Its screenshots are served locally and use fictional sample data; this landing page does not add advertising or analytics scripts.

Clearing browser storage removes local preferences and stored sign-in information, but does not delete your server-side account or workspace records. Your deployment or connected services may have additional storage practices that need to be disclosed in the final policy.

6. Retention and deletion

Records are stored so that your workspace can continue operating. The production retention schedule, backup retention, deletion timelines, and legal retention requirements are still to be confirmed. This draft does not promise automatic deletion after a fixed period.

Workspace deletion is not currently available as a self-service action. Contact your workspace administrator and the operator to discuss a request before relying on deletion for sensitive information.

7. Your choices and requests

You can update available profile details, change notification preferences, manage account sessions, and revoke supported integration tokens. Workspace administrators control team membership and project access.

Depending on the laws that apply, you may have rights to access, correct, delete, restrict, object to, or receive a copy of personal data, withdraw consent where applicable, and complain to a supervisory authority. The final policy must specify the applicable request procedure, verified privacy contact, and regulator.

8. Questions and updates

Product questions can be directed to [email protected], the contact currently configured in Planvyra. The operator must confirm the privacy request channel and this mailbox’s availability before the final policy takes effect.

An effective date and material-change notification process will be added to the approved policy. For the technical protections currently implemented, see Data protection.