Privacy Policy — “Admin v Kurse” (Админ в курсе)
Contents
- In short
- 1. Who is responsible
- 2. Whose data this is about
- 3. What the server does not store
- 4. What the server stores
- 5. Notifications and Apple
- 6. What is stored on your phone
- 7. Why we process data
- 8. Who receives data
- 9. Where data is stored
- 10. How we protect data
- 11. How to delete data
- 12. Your rights
- 13. Age
- 14. Changes to this policy
- 15. Contact
Version of 18 November 2026. English version of the Russian «Политика конфиденциальности»; the Russian text prevails.
In short#
- Conversations stay in VK. The server relays them between VK and your phone and does not store them — no messages, no comments, no attachments.
- The server keeps service data only: who signed in (VK ID number and name), which communities are connected, event and message numbers, “who replied” marks. The only text it stores is written by the team itself: a note about a customer, reply templates, the reason of a “Nudge” reminder.
- The server is in Russia: DataPro Moscow II data centre, Khimki, Moscow Region.
- Four parties receive data: VK (the whole app works through it), Apple (delivers notifications), the server's hosting provider and the provider hosting the website and email. No ads, no analytics, no sale of data.
- The website has no cookies, trackers or scripts.
- You can delete your account in the app: Settings → “Delete account”.
1. Who is responsible#
The app “Admin v Kurse” and its server (api.adminvkurse.ru) are developed and operated by an individual, Denis Larin (“we”).
Contact for any privacy question: admin@adminvkurse.ru.
The app is not affiliated with VK and is not a VK product. It works through the documented VK API.
2. Whose data this is about#
- App user — a manager of a VK community (creator, administrator, editor or moderator) who signed in to the app.
- Community customers — people who message the community, comment, like, join, or place orders.
- Community managers who do not use the app — VK tells us their ID numbers and roles so that we can grant permissions correctly.
The roles differ. For app users' data we are the data operator (controller): we decide what is stored and why. The community is responsible for its customers' and other managers' data: it is the operator and decides why and how that data is used, while we process it on the community's instruction and only so the app can work (Terms of Use, section 6).
3. What the server does not store#
- Texts of messages and comments, wall posts.
- Photos, videos, voice messages, files. The phone uploads attachments directly to VK servers and downloads them directly from VK.
- Names, photos and profiles of customers. The phone requests a customer's card from VK through our server; nothing of it stays on the server.
- Lead-form answers, order addresses and comments, text reasons for bans.
- VK ID tokens: they are used once at sign-in and are not kept.
- Email and phone number — we do not request them at sign-in. From what VK ID returns together with your name, the server takes only the ID number, first name and last name; it neither reads nor stores the rest.
- “Typing” and “opened the conversation” signals to teammates (with your name) — relayed, not stored.
How it works: VK sends our server an event (“new message”, “new comment”), which may contain text. The server takes only the numbers from the event, sends your phone a “something new” signal and discards the rest. The phone then fetches the text from VK itself, with our server acting as a relay; the server does not save VK's response or write it to logs.
Three exceptions — text written by the team itself:
| What | Limit | Kept |
|---|---|---|
| Team note about a customer (a copy is written to VK's “Comment” field) | 96 characters | until the note is cleared or the community is disconnected |
| Quick reply templates | title up to 100 characters, text up to 4,096 characters, up to 200 templates per community | until the template is deleted or the community is disconnected |
| Reason of a “Nudge” reminder | 100 characters | until the reminder is dismissed or done |
4. What the server stores#
About the app user#
| Data | Why | Retention |
|---|---|---|
| VK ID number, first and last name (from VK ID at sign-in) | to recognise you, grant permissions according to your VK role, and label your replies for teammates | until you delete your account |
| Sign-ins on devices: a hash of the session token, device model and OS version (“iPhone · iOS 27.0”), sign-in method, time of sign-in and of last activity | to keep you signed in and show the “Devices” list | until you delete your account. A sign-in unused for 90 days stops working; its record remains until you delete your account |
| Device address for notifications (Apple push token) | to send you push notifications | erased on sign-out, when a sign-in is ended, on account deletion, and when Apple reports the address as no longer valid |
| “Events” push settings (which types are on) | to send only what you want | until you delete your account |
| “Who on the team sent this message” marks: community number, customer's VK ID number, message number, you, time | author label under the community's reply | 180 days |
| “Who replied to a comment” and “who marked it handled” marks | same for comments | 90 days |
| Backup sign-in by code (issued manually, e.g. to App Store reviewers): hash of the code, VK ID number and name it was issued for | sign-in without VK ID | until you delete your account |
| “Connect community” requests: your VK ID number, community number, time, result | connecting a community | valid for 10 minutes; the record is erased on account deletion or when the community is disconnected |
| Consent to the processing of personal data: the version you accepted and the time of the tick | to confirm that consent was given | until you delete your account |
About the community#
| Data | Retention |
|---|---|
| Community number, community access key (encrypted with AES-256-GCM; the encryption key is kept separately from the database), who connected it and when | while the community is connected |
| Settings for receiving VK events (Callback server number, hash of the secret, confirmation string) | while the community is connected |
| List of managers: VK ID number and role of each (a copy of VK's response) | while the community is connected; refreshed every 10 minutes |
| Which VK label “👤 Name” belongs to which manager (conversation lead) | while the community is connected |
About community customers#
| Data | Retention |
|---|---|
| “Events” log: event type, time, the person's VK ID number, numbers of the post, comment or other object, “answered” / “handled” marks, service numbers (order or donation amount and currency, order number and status, lead-form number, poll option, ban end date) — no text | 90 days |
| “Who replied” marks (see above) — they contain the customer's VK ID number and the message number | 180 and 90 days |
| Customer note and “Nudge” reminder (customer's VK ID number, due time, reason, who set it and for whom) | see the table in section 3 |
| Numbers of VK events already processed (to avoid processing twice) | 2 days |
The server holds no customer names — only their VK ID numbers.
Technical logs#
The server keeps request logs: IP address, time, method, request path (conversation numbers in it are masked) and response code. Logs contain no tokens, no text and no customer ID numbers. The web server log is kept for 7 days, the service's system log for up to one month.
Website and email#
The adminvkurse.ru website has no cookies, trackers, ads or scripts. The website's hosting provider keeps a technical request log: IP address, time, page address, response code, referring page and browser name. The log sits in our hosting container and is kept for no longer than 7 days: older entries are erased automatically. We look into it only to diagnose faults and fend off attacks.
Emails to admin@adminvkurse.ru are stored in a mailbox at the email hosting provider. We delete them once the matter is resolved and the correspondence is no longer needed — no later than one year after the last email.
Backups#
An encrypted copy of the database is made every night. Copies are kept only in Russia, on the main server: the last 14. A copy can only be decrypted with a key that is not on the server. Data erased from the database therefore disappears from backups within 60 days at the latest.
5. Notifications and Apple#
Push notifications are delivered by Apple (Apple Push Notification service). To deliver one, the server sends Apple your device address and a short service payload.
- About a customer's message: the payload holds numbers only — community, the customer's VK ID number, message number. No text and no name: the app on your phone fetches those from VK through our server and puts them into the notification.
- About events (comments on posts, likes, joins, orders and so on): event type, numbers and the author's VK ID number, service numbers (e.g. an order amount). If you can see more than one community, also the community's name.
- Exception. The text of comments on photos, videos, market items and in discussion boards is currently sent in the push payload in plain text (up to 1,500 characters): VK does not let us read such a comment later — it exists only in the event itself. Apple is technically able to see this text. We plan to encrypt it so that only your phone can read it.
You can turn notifications off in iOS Settings, or per type in the app.
6. What is stored on your phone#
- Session token — in the iOS Keychain, on this device only, not synced to iCloud.
- Cache, so screens open instantly: conversation list, messages, customer cards, notes, templates, reminders, the “Events” feed, the wall, avatars. Kept in the app's storage under iOS data protection (unreadable while the phone is locked) and excluded from iCloud backups.
- Drafts of replies.
- Texts of comments on photos, videos, market items and discussion boards — there is nowhere else to get them from (section 5).
- Debug log — only if you turned “Debug” on in Settings yourself. It contains no message text, names or tokens; customer numbers are replaced with pseudonyms. The log is not sent anywhere; only you can share it.
- Delivered notifications are kept by iOS itself.
“Sign out” erases the session token, drafts and the debug log; the cache stays on the phone under iOS data protection. “Delete account” erases all app data from the phone, including the cache.
Device permissions#
| Permission | Why |
|---|---|
| Camera | take a photo and send it to a customer |
| Microphone | record a voice message |
| Photos (add only) | save a photo from a conversation |
| Speech recognition | show a voice message as text. Recognition runs on the phone; audio is not sent anywhere |
| Face ID | app lock. iOS performs the check; the app never receives face data |
| Notifications | push notifications |
iOS asks for each permission separately; declining one does not block the rest of the app.
7. Why we process data#
- to sign you in and check that you manage the community and what you are allowed to do;
- to run the app: conversations, events, wall, labels, reminders, notes, templates;
- to send notifications;
- to show the team who replied;
- to prevent abuse and diagnose faults (logs).
We show no ads, run no behavioural analytics, build no profiles, and do not sell or share data with anyone other than those listed in section 8. The app contains no third-party libraries or trackers.
Legal bases.
- App users' data — to perform the Terms of Use you accept at sign-in (Russian Federal Law “On Personal Data”, Article 6(1)(5)). The app cannot work without your ID number, name, sign-in and push address.
- Keeping the database with the hosting provider and sending your device address to Apple — also on the basis of your consent, given with a separate tick box («Согласен на обработку персональных данных», “I agree to the processing of personal data”) on the sign-in screen — users who signed in earlier are shown it once; its text is at adminvkurse.ru/consent.
- Logs with IP addresses — to protect the service from abuse (Article 6(1)(7)).
- Community customers' data — on the community's instruction.
8. Who receives data#
| Who | What and why |
|---|---|
| VK — VK LLC (OOO «ВК», OGRN 1027739850962, Moscow): VK ID and the VKontakte API platform | Sign-in through VK ID. Every request the app makes about a community goes to VK with the community key: this is VK's own data, and we send back what you do (your reply to a customer, a label, a note). |
| Apple (Apple Inc., Apple Push Notification service, USA) | Device address and push payload (section 5) — to deliver notifications. Apple's servers are located outside Russia, so this is a cross-border transfer of data. There are no other transfers abroad. |
| Hosting provider — VDSina — Hosting-tekhnologii LLC (OOO «Хостинг-технологии», INN 7721833428, Moscow), DataPro Moscow II data centre (Khimki, Moscow Region) | The server and the database physically run there. Community keys and backups are encrypted. |
| Website and email hosting — Jino — Avguro Technologies LLC (OOO «Авгуро Технолоджис», INN 7706641390, Moscow) | The adminvkurse.ru website and the admin@adminvkurse.ru mailbox: emails you send us and the website's technical request log (section 4, “Website and email”) are stored there. It receives no data from the app. |
An uptime monitoring service only checks that the server responds; it receives no user or customer data.
Data may be disclosed on a lawful request from a public authority.
9. Where data is stored#
The server, the database and its backups are in Russia. So are the website and email, with the hosting provider in Moscow. Data on the phone stays on your device. The only data leaving Russia is what Apple needs to deliver notifications (section 5).
10. How we protect data#
- All traffic between the app and the server uses HTTPS.
- Session tokens are stored on the server as hashes only; community keys are encrypted.
- The community key never reaches the phone.
- Permissions in the app come from your role in VK: once the role is removed, access is gone.
- Only the service owner has access to the server.
- Backups are encrypted.
11. How to delete data#
Delete your account. In the app: Settings → “Delete account” (the app's interface is in Russian: «Настройки» → «Удалить аккаунт»).
Erased immediately: your VK ID number and name, all sign-ins on all devices, push addresses, push settings, sign-in codes and connection requests. All app data is erased from the phone.
What stays with the team, but without you:
- “who replied” and “who handled” marks — they show “deleted user” instead of you (anonymised);
- customer notes, templates and reminders — without the author's name;
- a community stays connected as long as another manager can see it in the app; the “connected by” mark is erased.
If nobody but you can see a community in the app, it is disconnected and all its data on the server is erased. The app lists such communities before you confirm.
Deleting your account does not affect your VK account, the community, or the conversations in VK. If you sign in again, a new account is created from scratch.
Disconnect a community. Settings → Communities → the community → “Disconnect community” (available to the creator and administrators). The server erases the community key, notes, templates, reminders, the “Events” log and “who replied” marks. You can additionally revoke the issued key in VK: Manage community → API usage.
Sign out. Settings → “Sign out” ends the sign-in on this phone. Sign-ins on other devices are ended in Settings → Devices.
No access to the app? Email admin@adminvkurse.ru with a link to your VK page and we will delete the account manually. To avoid deleting someone else's account, we will ask you to confirm the page is yours.
Erased data remains in encrypted backups for up to 60 days (section 4).
12. Your rights#
You can:
- find out what data about you is stored and get a copy;
- ask us to correct or delete it;
- withdraw consent and stop using the service;
- complain to the data protection authority (in Russia — Roskomnadzor) if you believe your rights have been violated.
Email admin@adminvkurse.ru. We reply within 10 business days; if we need more time we will tell you why, and it will be no more than 5 further business days. To avoid giving data to a stranger, we will ask you to confirm that the VK page is yours.
You can withdraw consent by the same email or by deleting your account. The app cannot work without consent and without an account.
If you are a community's customer and want to know what the community has recorded about you (a note, a reminder) or to have it deleted, contact the community: it controls that data. You may also write to us — we will pass the request to the community and help carry it out.
13. Age#
The app is a work tool for community managers. You must be at least 18 to use it. We do not knowingly collect data of users under 18; if we learn that a person under 18 has created an account, we will delete it.
14. Changes to this policy#
The current version is always on this page, with its date at the top. We will announce material changes (new data, new recipients) in the app before they take effect.
15. Contact#
Denis Larin, admin@adminvkurse.ru.