beimir Calendar

Privacy and data

The application does not use hidden analytics, advertising, profiling or data sales. It stores only information entered for the account and schedule, plus minimal technical records needed to operate the service.

Responsibility

The service operator is listed below. Each teacher is responsible for the lawful use of their students’ data.

Stored data

Teacher name and email, email verification, schedules, student data, age, notes, groups, holidays, settings and technical events.

Excel import

The Excel file is processed in the browser and is not uploaded to the server as a whole. Only student fields selected and confirmed by the user are saved; a birth date is converted to age when that option is enabled.

Purpose

Sign-in, device synchronisation, schedule planning, backup and error diagnosis.

Location

The schedule is encrypted in the browser before transmission. The server and backups receive only an encrypted container; an encrypted local copy may be kept in the browser.

Who can read it

During normal operation, student records, notes and schedules are decrypted only on the user’s unlocked device; the key is not sent to the server. Account metadata and technical logs are outside the encrypted workspace.

Infrastructure and recipients

The encrypted container and account data are hosted on a DigitalOcean server in Frankfurt, Germany. Email addresses and service-email content are sent to Resend in the United States for verification and password resets; Resend provides contractual safeguards for international transfers.

Transfer to Planner

Selected student and availability data is sent to planner.beimir.ch only after an explicit click. Planner encrypts projects, jobs, results and their backups with AES-256-GCM, but unlike Calendar it is not end-to-end encrypted: the server worker temporarily decrypts data in memory to calculate the plan. A completed plan returns to Calendar only after review and confirmation.

Live calendar subscription

This is an explicit exception to end-to-end encryption: the browser separately publishes a finished feed containing lesson times and names. The server and anyone holding the secret link can read that feed, but it grants no account access and contains no notes or full student records. Disabling it removes feed access.

Retention

Data remains until the account is deleted. Technical log retention is set by the administrator; backups rotate separately.

Your controls

You can download your data, delete schedule data or delete the whole account. Contact the operator to request corrections.

Security

The schedule uses end-to-end AES-256-GCM encryption; a separate random key is protected by the password in the browser. Keep the recovery code separately: without the password and code, even the operator cannot restore the data. HTTPS, email verification and rate limiting provide additional protection.