Last updated: February 22, 2026

Calendar 2 Server Privacy Policy

1. Overview

Calendar 2 Server is an Android app for one-way calendar replication:

• Device calendars to uploaded .ics data
• Device calendars to CalDAV overwrite target

The app is configured by you and runs sync from your device directly to the destination server you choose. This policy applies to the Android app distribution.

2. Who operates the app

• Publisher: Astronauta DEV
• App: Calendar 2 Server
• Contact: [email protected]

3. Data the app processes

The app processes data only to perform your configured sync jobs.

3.1 Calendar data read from your device

When you grant calendar permission and select calendars, the app reads event data such as:

• Calendar ID and event ID
• Title, description, and location
• Start/end times, all-day flags, and timezone
• Recurrence and exception metadata (RRULE, RDATE, EXDATE, recurrence linkage)
• Attendee email addresses (unless you enable attendee removal)

3.2 Profile and sync configuration data

• Selected calendars
• Destination URL or collection URL
• Authentication mode (none, basic, bearer)
• Schedule settings (interval and constraints)
• Export options (remove description/remove attendees/include declined)

3.3 Credentials

• Profile credentials are stored via Android encrypted storage backed by Android Keystore.
• For scheduled headless worker execution, active profile snapshots are persisted locally.

3.4 Logs and diagnostics

The app stores local sync logs for troubleshooting, including:

• Start/end/failure messages
• Durations, HTTP status codes, failure step/reason
• Worker trigger metadata for scheduled runs

Sensitive values are sanitized before log persistence/display, including auth headers, URL credentials, token/password-like query parameters, and sensitive JSON keys.

4. How data is used

• Read selected device events
• Build iCalendar payloads
• Upload or replicate data to your configured destination
• Run background schedule jobs
• Display status and logs in-app

The app does not use your calendar data for advertising personalization.

5. Where data is sent

Calendar 2 Server does not provide a hosted sync backend. Data is sent from your device directly to endpoints you configure in your profile, including your own servers, third-party CalDAV services, or custom HTTP/HTTPS endpoints. You are responsible for the destination privacy and security posture.

6. Local storage and retention

Data is stored locally on your device, including:

• Profiles (c2s.profiles.v1 local storage, sanitized of inline secrets)
• Sync logs (Android local database sync_logs)
• Scheduler state and pending work metadata (Android shared preferences)

You can remove data by deleting profiles, clearing logs in the app, or uninstalling the app.

7. Permissions

• android.permission.READ_CALENDAR to read selected calendars/events for export/sync
• android.permission.INTERNET to send sync traffic to configured endpoints

8. Data sharing

Except for your configured sync destinations, the app does not intentionally transmit your calendar payloads to the publisher. No built-in ad SDK or third-party analytics SDK is included in the current Android app distribution.

9. Security notes

• Credential storage via Android encrypted storage
• Secret/token sanitization in logs and error surfaces
• Optional background constraints (Wi-Fi only, charging only, battery not low)

No mobile app can guarantee absolute security. Protect your device, use strong endpoint credentials, and prefer TLS endpoints.

10. Your choices and controls

• Choose which calendars are included
• Disable automatic scheduling (manual-only mode)
• Remove attendees and/or descriptions from exported payloads
• Disable or delete profiles
• Remove saved credentials and logs

11. Children

Calendar 2 Server is not specifically directed to children.

12. Changes to this policy

This policy may be updated as features change. The "Last updated" date reflects the current version.

13. Contact

Questions about this policy: [email protected].