Data Retention & Protection Policy
This Data Retention & Protection Policy establishes Calenix's approach to retaining, protecting and securely disposing of information processed through the Services.
Calenix seeks to retain information only for as long as reasonably necessary to provide the Services, meet legal and contractual obligations, maintain security and resolve disputes.
1. Scope
This policy applies to information processed through:
- Calenix accounts;
- scheduling services;
- calendars;
- bookings;
- payment-related records;
- integrations;
- customer support systems;
- application databases;
- logs;
- backups;
- analytics systems; and
- other systems used to operate Calenix.
2. Data Categories
Information may include:
- account information;
- contact information;
- scheduling information;
- calendar information;
- booking information;
- integration information;
- payment and transaction information;
- communications;
- technical information;
- security logs;
- support records; and
- legally required business records.
3. Retention Principles
Calenix applies the following principles:
- Data should not be retained longer than reasonably necessary.
- Sensitive information should receive appropriate protection.
- Access should be restricted to authorised personnel.
- Information should be securely deleted when no longer required.
- Legal holds and regulatory requirements take precedence where applicable.
- Backup copies may persist for a limited period after production deletion due to backup and disaster-recovery processes.
4. Account Data
Account information is generally retained while an account remains active.
Following account closure, information may be deleted or anonymised within 90 days, subject to:
- legal obligations;
- outstanding transactions;
- dispute resolution;
- fraud prevention;
- security requirements;
- backup retention; and
- legitimate business recordkeeping.
5. Calendar Data
Calendar information is retained only for as long as necessary to provide the calendar integration and associated scheduling functionality.
When a user disconnects a calendar integration, Calenix will stop accessing that calendar through the revoked connection.
Cached or synchronised calendar information may remain temporarily where technically necessary for deletion processes, backups, security or legal obligations.
6. Integration Tokens
OAuth access tokens, refresh tokens and similar credentials are treated as sensitive information.
Calenix limits access to such information and uses appropriate security controls.
When an integration is disconnected or authorisation is revoked, associated credentials should be invalidated or deleted within a reasonable operational period.
7. Booking Data
Booking records may be retained to:
- provide booking history;
- support customer service;
- facilitate reporting;
- process refunds or disputes;
- maintain financial records; and
- meet legal obligations.
8. Payment Records
Payment records may be retained for accounting, tax, fraud prevention, dispute resolution and legal requirements.
Where payment processing is provided by a third-party payment processor, payment-card information may be retained by that processor under its own policies and applicable obligations.
9. Security Logs
Security and operational logs may be retained for a period reasonably necessary to:
- investigate incidents;
- identify suspicious activity;
- troubleshoot systems;
- maintain service reliability;
- meet security requirements; and
- comply with legal obligations.
Target retention period: 90 days
10. Backups
Calenix may maintain encrypted or otherwise protected backups for disaster recovery and business continuity.
Backups are subject to controlled access.
Information deleted from production systems may remain in backup copies until those backups expire through the normal backup lifecycle.
Target retention period: 90 days
11. Secure Deletion
When information reaches the end of its applicable retention period, Calenix may:
- securely delete it;
- anonymise it;
- aggregate it so that it no longer identifies an individual; or
- securely destroy the relevant storage medium where appropriat
12. Data Protection
Calenix uses appropriate measures to protect retained information, which may include:
- encryption;
- access controls;
- authentication;
- least-privilege access;
- monitoring;
- secure infrastructure;
- vulnerability management;
- backup controls; and
- incident response.
13. Legal Holds
Calenix may suspend deletion where information is subject to:
- litigation;
- investigation;
- regulatory proceedings;
- legal preservation requirements; or
- another legitimate legal hold.
14. User Requests
Users may request access to, correction of or deletion of their personal information, subject to applicable law.