Privacy policy

The Vremya.io browser extension and the vremya.io website. The extension gathers your calendars in one place, syncs events between them and exports time to your issue and time trackers; the website holds your account, your subscription and the documentation.

Calendar events, issue keys, mapping rules, logs and every credential you enter — OAuth tokens, CalDAV passwords, tracker API tokens — live in the extension's local storage on your device. They are never uploaded to us and we cannot read them: the extension talks to your calendar and tracker services directly.

A random identifier generated when you install it, used to check your subscription. If you link the extension to a site account, we also store the time and the IP address of that request. Anonymous crash reports stay off until you enable them in the extension settings; they carry the error and its stack trace with e-mail and user name stripped, never your calendar or issue content.

Your e-mail address plus the name and picture you choose to add; sign-in codes; active sessions with their IP address and browser user agent; a log of account actions. For purchases we keep the amount, currency, status, the provider's payment id, the receipt link and the last four digits of the card — full card details are handled by the payment provider and never reach us.

Two: a session cookie that keeps you signed in and a language cookie that remembers the site language. The theme is stored in your browser rather than in a cookie. No advertising or cross-site tracking cookies.

The payment providers YooKassa and CryptoCloud for purchases, our own mail server for sign-in codes and receipts, and a self-hosted GlitchTip instance for crash reports, which are routed through vremya.io rather than a third-party endpoint. We do not sell your data and do not share it for advertising.

Data received from Google APIs is used only to read and sync your calendar events, in line with the Chrome Web Store User Data Policy including its Limited Use requirements. It stays on your device, is never used for advertising and is never read by a human. You can revoke access at any time in your Google account or by disconnecting the calendar in the extension.

Account data until you delete the account. Sign-in codes expire after 15 minutes; sessions expire or end when you sign out. Payment records are kept for as long as accounting rules require. Deleting your account under Account → Profile removes your profile, sessions, activity log, telemetry and payment records from our database.

You can export or clear the extension's data in the extension itself, turn crash reports off, unlink the extension from your account and delete the account. For access, correction or any other request, write to support.

Ask us anything about this policy or about the data we hold.