Plexidy

Privacy

We protect customer and workspace data.

This policy explains what we collect, why we collect it, and how to contact us with questions.

Terms of Service Contact security
Privacy and data protection
Privacy commitments cover product, support, and Insider pages.

Primary actions

Use the links below to review related policies or ask privacy questions.

  • Review terms

    Understand how usage is governed.

  • Ask security

    Contact our security team for clarifications.

  • Report an issue

    Use the support form if you suspect a privacy concern.

Current status / summary

We collect only what we need to operate Plexidy and provide support. Data handling aligns with the controls listed below.

Area
Summary
Collection
Account, operational, support, and analytics data only.
Use
Service delivery, security, support, and product updates.
Sharing
No sale of data; limited sharing with processors for delivery.

Data we process

  • Account details

    Names, emails, and authentication data needed to operate the service.

  • Operational data

    Schedules, bookings, and related metadata stored to power product features.

  • Support context

    Information you share when contacting support, limited to the request.

  • Analytics

    Aggregated usage to improve performance and usability.

How we use it

Purpose
Use
Service delivery
Operate and improve scheduling, notifications, and account access.
Security
Detect abuse, enforce permissions, and audit access.
Support
Respond to requests and improve help content.
Product updates
Send release and status information when relevant.

Your choices

  • Access & correction

    Request a copy of your data or updates to inaccurate information.

  • Deletion

    Ask us to delete data where legally allowed and operationally feasible.

  • Communication preferences

    Control notification channels in account settings.

Retention and deletion

Data type
Retention approach
Account data
Retained while your workspace is active; removed after verified closure.
Operational records
Kept as needed to provide the service and meet audit obligations.
Support tickets
Stored for history; redaction available on request.
Analytics
Aggregated and de-identified where possible.

Recent activity / history

Date
Change
Reason
Feb 12, 2026
Updated retention language
Clarified timelines for support ticket data.
Jan 25, 2026
Added processor list link
Improved transparency for sub-processors.
Jan 10, 2026
Communication preference guidance
Aligned with notification settings UI.

Operational depth

Explain privacy commitments in terms teams can operationalize

Privacy policy content should detail collection, use, retention, and user-rights handling so legal language can map to daily operations.

Primary audience

Legal reviewers, compliance teams, and workspace administrators

Decision focus

Verify whether privacy handling aligns with internal obligations and customer commitments

Operational risk

Generic policy interpretation can hide operational gaps in data handling practices

Field scenario

A compliance reviewer validates whether user-request handling is supported by documented policy.

Execution walkthrough

  • 1. Frame the objective

    Privacy policy content should detail collection, use, retention, and user-rights handling so legal language can map to daily operations.

  • 2. Align participants

    Legal reviewers, compliance teams, and workspace administrators

  • 3. Validate the decision

    Verify whether privacy handling aligns with internal obligations and customer commitments

  • 4. Mitigate known risk

    Generic policy interpretation can hide operational gaps in data handling practices

Interpretation matrix

Signal
Interpretation
Operational scenario
A compliance reviewer validates whether user-request handling is supported by documented policy.
Successful outcome
Successful use of this page leaves teams with clear direction on Verify whether privacy handling aligns with internal obligations and customer commitments.
If skipped
Skipping this step often introduces Generic policy interpretation can hide operational gaps in data handling practices.
Recommended next step
Review cookies and terms pages together to confirm cross-policy consistency.
Legal centerEscalate an issue