Privacy Policy

The personal data controller is Saveliy Yudin, a self-employed individual under the Russian professional income tax regime, TIN 772747496179. Email: support@tetiva.app.

When you sign up at app.tetiva.app, you give an email address, a name and a password. The password is stored only as a bcrypt hash; we never know the password itself. We also keep the interface language, whether the email address is confirmed, and when the account was created and last changed.

Signing in creates a session that keeps the IP address and the User-Agent string of the browser or the app. The app adds the computer name to its User-Agent. A session is deleted 30 days after it was last used.

The activity log records sign-ins, sign-ups, invitations, changes to organizations and workspaces, and payments. Each entry says who did what and when, from which IP address and with which User-Agent, and for sign-ups and invitations also the email address. The log exists for security and for resolving disputes. Organization admins see their organization's events, but without IP addresses, User-Agent strings or sign-in events.

If you invite a colleague to an organization by email, we keep their address and send them the invitation. The invitation is deleted when it expires, no later than 30 days.

Sync sends the collections, requests, environments and variables of cloud workspaces to the server, including the values of secret variables. On the server all of it is stored encrypted (AES-256-GCM, a separate key per workspace). The contents are used only for sync, and the service's admin tools have no way to view them.

Payments in rubles are taken by YooKassa. It receives the amount, the plan name and technical payment and organization IDs. You enter your card details on the YooKassa page; we never receive them. If you turn on auto-renewal, we keep the ID of the saved payment method, its name as YooKassa reports it (for example, “Bank card *4444”), and the date and version of the terms you agreed to.

Payments in US dollars and euros are taken by lava.top. It receives your email address, the plan and the currency. We keep that address in the payment and subscription records.

Payment records — amount, plan, date and status — are kept for five years, as tax law requires.

Emails are sent through the smtp.bz service: email confirmation, password reset, invitations, organization ownership transfer, and payment and subscription notices. We send no marketing emails.

The site uses web analytics that collect anonymized visit data: cookies, IP address, browser type and version, operating system, screen resolution, referrer, pages viewed and interactions on them.

Analytics includes Yandex.Metrica Session Replay, which records anonymized sessions (cursor movement, clicks, scrolling) to help us assess usability. Input field contents are masked and are not captured in the recording.

We use Yandex.Metrica (including Session Replay). The collected data is processed by the service under its own policy: Yandex LLC. We do not link this data to specific individuals and do not use it to identify anyone.

The same Yandex.Metrica counter runs in the app.tetiva.app dashboard, without Session Replay or click maps. All it receives from there is the name of each section you open — no invite codes or other address parameters — and two events: sign-up and a successful payment (with plan and billing period). This tells us which source on the website new accounts came from.

The app collects no analytics and does not report how you use it. Requests you create go only to the addresses you put in them.

While Check automatically is on (the Updates section of the settings; on by default), the app asks api.tetiva.app for a file with the latest version number at most once a day, and right away if sync stops because this version is too old. The app adds only its own version and the name of the operating system to that request — nothing about you; the server sees the IP address and the User-Agent string. The log keeps the operating system, the app version, the User-Agent string and a truncated hash of the IP address — never the address itself. These records are used only to count installations.

When a new version is out and Download updates automatically is on (also the default), the app on macOS and Windows downloads it in the background from s3.twcstorage.ru, the same storage the files on the download page come from; that storage sees the IP address and the User-Agent string. Before offering the update, the app checks the file against Tetiva's ed25519 signature and its sha256 checksum, and it installs the update only when you click Restart to update. With the setting off, the update downloads only when you press Download. On Linux the app downloads nothing; updates come through apt.

Both settings can be turned off. With Check automatically off, the app makes no update requests on its own; Check now checks on demand.

Sync with Tetiva Cloud starts only after you sign in: then the data of the cloud workspaces you chose goes to the server. Working locally needs no account and does not contact our servers.

When you sign in through the browser, the app sends the computer name, the operating system and its own version. This sign-in request is deleted within an hour; the computer name stays in the session and the activity log.

A public collection page (share.tetiva.app) shows only the collection's contents: no author name, organization name or email address. Yandex.Metrica does not run on these pages.

A reader's IP address is used only in server memory, to rate-limit requests and count views, and is never stored in the database. If a collection is password-protected, entering the password gives the browser a cookie for 30 days; it holds nothing about you.

A report about a collection includes the reason and, if you wish, a message and an email address for a reply. The report is stored with a hash of the IP address computed with a secret key, which filters out repeated reports. The report is also emailed to support@tetiva.app.

The test API at playground.tetiva.app receives the IP address and technical request data in order to respond, limit load and protect the service from abuse. Request contents are not stored; the service log only gets de-identified technical information about requests.

The feedback forms on the site are served by Askyo (app.askyo.ru). Askyo receives technical browser data, and what you type into a form only once you submit it.

What you put in the form is up to you: usually an email address to reply to and the text of your message. We use it only to answer you and do not pass it to third parties. A technical browser identifier is stored alongside the message so the form does not ask you to fill it in twice.

The account, sync, organizations, payments and service emails are needed to provide the service; the legal basis is performance of a contract you are a party to, including the public offer (Article 6(1)(5) of Russian Federal Law No. 152-FZ “On Personal Data”). Sessions, the activity log and abuse protection keep the service secure; the legal basis is the controller's legitimate interest (Article 6(1)(7)).

Analytics data helps us understand how visitors use the site, find navigation problems, and improve page content and layout. Processing of cookies and analytics data is based on your consent, given by continuing to use the site after the cookie notice is shown, and on the controller's legitimate interest in improving the site. The update-check log is used to count app installations; the legal basis is the controller's legitimate interest.

The test API uses the IP address and its log to protect the service from abuse and to see how much it is used; the legal basis is the controller's legitimate interest.

Messages sent through the contact form and reports about public collections are processed in order to answer them; the legal basis is your consent, expressed by sending the message.

We do not sell data or use it for marketing emails.

Tetiva's servers are rented from ADMINVPS LLC and are located in a data center in Moscow. Data also goes to services that some features cannot work without: YooKassa and lava.top for payments, smtp.bz for sending emails, Yandex LLC for Yandex.Metrica, Askyo for the contact form, and Timeweb Cloud storage (s3.twcstorage.ru) for serving app files. Each of them receives only what the relevant section above describes.

Databases with personal data of Russian citizens are located in Russia, on servers in Moscow.

Retention periods: the account and workspace contents — as long as the account exists; sessions — 30 days after last use; the activity log — 1 year; invitations — until they expire, at most 30 days; payment records — 5 years; the update-check log, the test API log and reports about public collections — 1 year; contact form messages — as long as needed to answer them.

Once the purpose of processing is achieved or you withdraw consent, the data is deleted within 30 days unless the law requires keeping it longer.

Connections to the site, the dashboard and the server are encrypted (TLS). Passwords are stored as bcrypt hashes, email confirmation and password reset tokens as SHA-256 hashes, and workspace contents encrypted. Only the controller has access to the servers and admin tools, and every view of a user's data through those tools is logged. The service's information system is assigned protection level 4 under Russian Government Decree No. 1119 of 1 November 2012.

You can ask what data of yours we process, have it corrected, blocked or deleted, and withdraw your consent to processing. To do so, write to support@tetiva.app from the address linked to your account. We reply within 10 business days.

To delete your account, send a request to support@tetiva.app as well. The account and data linked to it are deleted within 30 days. Payment records and activity log entries are deleted when the periods above run out.

If you believe your rights have been violated, you can complain to Roskomnadzor (the Russian data protection authority) or go to court.

You can block cookies in your browser settings or delete stored cookies. Some site features may behave differently as a result.

To opt out of Yandex.Metrica, use the official add-on: yandex.com/support/metrica/general/opt-out.html.

We may update this policy. The current version is always available on this page; the date of the last change is shown at the top.