Personal Data Processing Policy
Last updated: October 12, 2026
Effective: October 12, 2026
Written to article 18.1 of Federal Law 152-ФЗ of 27 July 2006 "On Personal Data", this document sets out who processes what in Keepr, why, and on what legal basis. It applies to keepr.ru, the Keepr apps, and the on-premises edition unless your organization has a separate agreement.
01Operator
The personal-data operator is sole proprietor Igor Timoshenkov (ИП Тимошенков Игорь Юрьевич), INN 920459629619, OGRNIP 318237500311922, 299000, Sevastopol, Russia.
Questions about processing, subject requests and withdrawal of consent go to support@keepr.ru, which also reaches the person authorised to deal with Roskomnadzor. No separate officer responsible for organising processing is appointed: article 22.1 places that duty on operators that are legal entities, and this operator is a sole proprietor.
02Scope
This policy covers processing through the keepr.ru site, the Keepr web application, the Keepr panel in Jira, the browser extension, and contact with support.
In an on-premises deployment your organization is the operator: the data stays in its infrastructure and this policy does not apply to it.
The Russian text prevails; this English version is a convenience translation.
03Categories of data subjects
Site visitors who have not created an account. Registered users. Members of organizations created by other users. People invited to an organization — until the invitation is accepted, only the email address is processed. Representatives of payers whose details appear on payment documents.
Keepr does not process special categories of personal data or biometric personal data, and does not knowingly collect data from minors.
04Data processed
Everything processed, and how long it is kept. Workspace content is listed separately because you, not Keepr, decide what goes into it.
| Category | Contents | Retention |
|---|---|---|
| Account | Email address, password hash, email-verification marker | Until you delete your account, then erased within 7 days |
| Profile | Name, job title, phone, country, time zone, language, profile photo | Until you delete your account, then erased within 7 days |
| Organization membership | Name, job title, phone, country, time zone and photo set for one organization, plus role and workspace membership | While the membership lasts; erased with your account |
| Workspace content | Time entries, projects, tasks, clients, tags and the descriptions you type | As decided by the organization that owns it |
| Technical | IP address and browser details for sign-ins and security-relevant actions, session identifiers | In the organization's audit log while the organization exists; the IP address and browser details are erased with your account |
| Payment | Payer details on payment documents, payment and subscription history. Keepr never receives or stores card numbers — the payment provider handles them | 5 years (402-ФЗ art. 29, Tax Code art. 23) |
| Support requests | Name, email address, user id, organization, plan, page URL, browser and the text you wrote | Until the request is closed, then within the limitation period; erased with your account, including the copy in GitLab |
05Purposes of processing
Providing the service: registration and sign-in, syncing timers across devices, recording time, building reports, running invitations and enforcing access.
Service mail: email verification, password recovery, invitations, subscription notices and the digests you switch on.
Payment and accounting: taking payments and issuing receipts and payment documents.
Security and abuse prevention: the audit log, rate limiting, incident investigation.
Support: handling and answering your requests.
Traffic analytics — only with the consent you give in the cookie notice.
06Legal bases
Performance of a contract to which you are a party — art. 6 part 1 clause 5 of 152-ФЗ. This covers the account, workspaces and everything without which the service cannot be delivered. The contract is the Terms of Service you accept when registering.
Compliance with obligations imposed by law — art. 6 part 1 clause 2: accounting and tax records (402-ФЗ, Tax Code), and answering lawful requests from state authorities.
Consent — art. 6 part 1 clause 1. Only traffic analytics runs on this basis. You can withdraw it at any time under Analytics in your profile, and declining changes nothing about how the service works.
Personal data of an organization's members inside its workspaces is processed on that organization's instruction under art. 6 part 3: the organization is the operator for workspace content, and Keepr acts on its instruction.
07How and where data is processed
Processing is automated and involves transmission over telecommunications networks. Keepr takes no decisions producing legal effects on the basis of automated processing alone. Personal data is not disseminated or used for advertising, and Keepr does not sell personal data.
The databases in which personal data of Russian citizens is recorded, systematised, accumulated, stored, updated and retrieved are located in the Russian Federation (art. 18 part 5 of 152-ФЗ). The infrastructure is Timeweb Cloud: managed PostgreSQL, S3 object storage and mail.
08Sharing with third parties
Personal data reaches only processors engaged on the operator's instruction, and only as far as their work requires: Timeweb Cloud (database, object storage and mail hosting), ЮKassa (payments), Yandex Metrica (analytics, only after your consent) and Hawk (error tracking). All of them are in the Russian Federation.
An error report from your browser carries the error text and stack, the page URL with its query string, the User-Agent string, the window size, the recent trail of navigation and clicks, and your IP address. It carries no account id, email address or password.
Inside your organization, the owner, administrators and workspace managers see time entries in their workspaces — that is how the product works. One organization's data is never disclosed to another: even a cross-organization timer conflict is reported as a number, never a name.
09Cross-border transfers
Delivering the service involves no cross-border transfer of personal data: all of the infrastructure is in the Russian Federation.
Two auxiliary flows do leave Russia. A request sent through "Report a problem" creates a confidential issue in GitLab (GitLab Inc., USA) carrying your name, email address, user id and organization. The Keepr panel in Jira runs on Atlassian Forge (Atlassian, USA and Australia), and its calls to Keepr are made there.
You can avoid both: support requests can be emailed to support@keepr.ru instead, and the Jira panel is connected only if you choose to.
10Your rights and how to exercise them
You may obtain information about the processing of your personal data; demand that it be corrected, blocked or destroyed where it is incomplete, outdated, inaccurate, unlawfully obtained or not necessary for the stated purpose; withdraw consent; and complain to Roskomnadzor or to a court.
Name, email address, password, language and time zone can be changed yourself in your profile at any time. Everything else goes to support@keepr.ru. We answer within 10 working days of the request; the period may be extended by no more than 5 working days, with notice of why.
You can leave an organization and delete your account yourself, under Account in your profile. The account is erased 7 days after you ask, and until then you can sign in and cancel; an organization you own has to be transferred or closed first. If you cannot sign in, password recovery gets you back in. Records an organization imported about someone it never invited are that organization's, and a request about them goes to it.
Deleting the account erases your sign-in, profile, photo, sessions, API tokens, notifications and support requests, including their copies in GitLab, and removes your email address, IP addresses and browser details from the security log and from the records of the documents you accepted. Time entries and the rest of an organization's workspace content stay with that organization, attributed to an account id with nothing left behind it; requests about them go to the organization. A record of the destruction itself is kept for three years, as Roskomnadzor order No. 179 requires. Database backups age out on the hosting provider's rotation.
A request needs something showing you are party to the relationship with the operator — sending it from your account's email address is normally enough.
Where the request concerns an organization's workspace content, that organization is the operator for it and the request goes to them. Keepr acts on their instruction.
On withdrawal of consent or once the purpose is achieved, personal data is destroyed within 30 days, unless a contract or the law requires it to be kept.
11Security measures
Passwords are stored as argon2 hashes, never in the clear; password-recovery and email-verification links are single-use and expire. Sessions live in an HttpOnly cookie scripts cannot read, and every state-changing request carries a CSRF token.
Data is encrypted in transit. Access to production systems is restricted and logged. An organization's audit log records sign-ins, permission changes, policy changes and report exports.
Pages inside your workspace are excluded from session replay: workspace content does not reach analytics.
On establishing unlawful transfer of personal data, the operator notifies Roskomnadzor within 24 hours and reports the results of its internal investigation within 72 hours.
12Changes to this policy
The version in force is always published on this page with unrestricted access. The revision history with dates is below.
We email you about changes that materially affect your rights before the revision takes effect. Continuing to use the service after that date means you have read the new version.
Revision history