Privacy Policy
What Memo.top does with your data — described from the service's own source code.
This policy explains what data Memo.top collects, why, who it is shared with and how long it is kept. It is written from how the service actually behaves: every statement here matches what the service really does, rather than what would be pleasanter to write.
That is why there are uncomfortable passages in it — about web analytics without a consent banner, about the "encrypted widget" not being end-to-end, and about account deletion still being done by hand. We decided you are better off knowing these things than reading a smooth formulation.
1. The short version
This section collects what you should know before reading the full text — including the things such documents usually leave out. It is a summary, not a replacement for the sections below.
- We do not sell your data, we do not show ads and we do not build advertising profiles. Memo.top has no payments, so we collect neither payment details nor a phone number.
- Your content is not sent to any artificial intelligence provider. The service performs no AI processing of your bookmarks or notes — see section 6.
- There are four external recipients: Yandex.Metrica, Google, Telegram and VK. The full list, with what each one receives, is in section 8.
- The Yandex.Metrica counter loads the first time you open the site. We have no cookie consent banner, so we do not claim that we obtained your consent in advance. How to limit the collection is explained in section 9.
- Genuine client-side encryption exists only for secret notes. The "encrypted widget" works differently: the password is sent to the server, and during the operation the server sees the plaintext. It is not end-to-end — see section 7.
- When you save a bookmark, our server opens that page itself and keeps its full text and a screenshot. No data about you is sent to that site — see section 4.
- There is currently no way to delete your account from the interface, and no one-click export of your data either. Both are done on request to support@memo.top — see section 15.
- The service has no automatic retention periods and no scheduled clean-ups: data is kept until you or we delete it — see section 13.
2. Who we are
The controller of your personal data is PAYMASTER TECHNOLOGIES ELEKTRONIK PAZARLAMA DIS TICARET LIMITED SIRKETI, Turkey, registration number 451893-5. Postal address: Merkez Mah. Kagithane Cad. A, Office No 11/61, Kagithane / Istanbul / Turkey.
The operator is established in Turkey, outside the European Union. The GDPR nevertheless applies to this processing because we offer the service to people in the Union (Art. 3(2) GDPR), and we describe our practices by reference to it throughout this document.
For anything concerning your data, including requests to exercise your rights, write to support@memo.top. This is the only address at which we accept such requests.
- Representative in the Union (Art. 27 GDPR)
- not appointed
- Where the servers and databases are physically located
- Turkey — this is where the servers, databases, search index and file storage are located
Where the servers and databases are physically located is stated above in this section. We make no other statement anywhere in this document about where exactly the data is stored.
Back to top3. What this policy covers
This policy covers everything that forms part of Memo.top as a service, not only the main website.
- The memo.top website and its language versions, together with the related service domains — memo.web.money, beta.memo.top, bxod.com.
- Embeddable pages: the calendar and the user card, which can be placed on a third-party website.
- The extension for the Chrome browser.
- The calendar service behind meetings and booking — this is our own infrastructure, not a third-party supplier.
- Your public profile page at /user/:username, if you have published it.
This policy does not cover the websites you bookmark, nor the services you sign in with (Google, VK, Telegram, WebMoney): when you sign in, their own authentication service processes your data under their own rules. For WebMoney this is said about sign-in specifically. Where WebMoney acts in its other role — as the storage for your files and the channel for service notifications — it is infrastructure of the operator's group and this policy does cover it; see subsection 8.1.
Back to top4. What data we collect
Everything the service actually records is listed below. The list was compiled from the database schema and the source code, not from a template.
4.1. Account data
- Your email address and, if you added one, a secondary address together with its confirmation status.
- Your name, nickname, the avatar link taken from a social network and any avatar file you uploaded.
- Your WMID, if you sign in with WebMoney.
- A username — generated automatically by the service when the account is created.
- Your bio, greeting and meeting topic, if you filled them in.
- Your interface language and the source of your registration.
- Your Telegram chat identifier, if you connected Telegram notifications.
- A hash of your password, the confirmation and password-reset tokens, and the list of your active sessions.
The service holds no phone number — we neither ask for one nor store one.
4.2. Data received from sign-in services
- WebMoney: when you sign in with a ticket, we receive your WMID and the IP address the sign-in came from. In a separate request by WMID, the service retrieves your nickname and avatar and stores them in your profile.
- Google: the account identifier and the account data you allowed to be passed on at sign-in.
- VK: the same — the account data passed on at sign-in.
- Telegram: the data from the Telegram login widget and the chat identifier used for notifications.
4.3. Your content
Everything you create in the service is stored by us: pages and their settings, widgets, bookmarks (title, description, address, icon, preview image and the "login" and "password" fields if you filled them in), notes, secret notes, tasks, RSS feeds, uploaded files and gallery images.
The calendar part stores events with their title, description and comment, busy slots and meeting requests — including the message the sender attached to a request. Notifications are stored together with the text shown in them and with a record of who triggered them.
4.4. What the service generates itself
Some data appears without any action on your part: the service produces it so that a bookmark looks right and can be found again.
- When you save a bookmark, our server opens the address you gave and takes the title, description, icon and preview image from it.
- Beyond that, the server keeps the full text of the saved page, a screenshot of it, and the images and links found on it. This copy stays with us and remains even if the original page changes or disappears.
- Reference information about the site is collected by the bookmark's domain name.
- Your bookmarks, notes and tasks are indexed in our search index together with your account identifier, so that search works.
4.5. Technical data and logs
- Server-side application logs. Request addresses and technical error details may end up in them.
- The IP address received from WebMoney when a sign-in ticket is verified goes into the server log; it is not written to the database.
- The calendar service stores in its database the IP address of the previous and the current sign-in, the number of sign-ins and their dates.
- In-application error tracking is switched off — no error data is sent outside.
4.6. The browser extension
The extension stores your session data and its own settings locally in your browser. It also has an optional permission to access your browser bookmarks.
4.7. What we do not collect
- Phone numbers.
- Payment details and card data — the service has no payments.
- Biometric data.
- Precise device location.
- We do not ask for special categories of data (Art. 9 GDPR). If you place such information in your own notes or bookmarks, it is stored like any other content of yours.
5. How we use the data
- To create and run your account and to recognise you when you sign in.
- To store, display and synchronise your content across your devices and the extension.
- To make search over your bookmarks, notes and tasks work.
- To show the preview image and icon of a saved page.
- To run the calendar: meeting requests, slots, reminders and notifications over the channels you chose.
- To send service email — address confirmation, password recovery, meeting notifications.
- To understand how the site is used, through web analytics.
- To protect the service against abuse and to investigate failures using the logs.
We do not use your data for advertising, we do not pass it to ad networks, and we neither sell nor trade it. We do not build a profile of you in order to make decisions about you — see section 17.
Back to top6. Artificial intelligence
We include this section because it is now the first question people ask. The answer is short.
- Your content is not passed to any artificial intelligence provider. Memo.top has no integrations with such services.
- Your data is not used to train models — neither ours nor anyone else's.
- The service performs no automatic AI categorisation of bookmarks.
- "AI News" is a topical news feed from an external news source. We request a feed on that topic from it; none of your personal data is sent in the process.
7. Encryption: what the server can see
The service has two different password-protection mechanisms, and they work in fundamentally different ways. We describe them separately because what is accessible to us depends on which one you use.
- Secret note — client-side encryption
- The contents are encrypted in your browser before they are sent. The password stays in the form on the page: it is saved neither in browser storage nor on the server. We receive and store ciphertext only and never see the plaintext. The flip side: if you lose the password, neither you nor we can recover the note — there is no way around it.
- Encrypted widget — server-side encryption
- You type the password in the browser and it is sent to the server. The server decrypts the password and uses it to encrypt the widget contents itself. The key that protects the password in transit is issued by the server and stored by the server.
Two more circumstances are better stated plainly. First, in an ordinary, unencrypted widget the bookmark's "login" and "password" fields are stored in the database in the clear. Second, if an account is created for you on another user's initiative, the generated password is emailed to you in plain text — change it immediately after your first sign-in.
Back to top8. Who we share data with
There are four external recipients, and all of them are listed below. We do not sell data and we do not pass it to ad networks or data brokers.
| Service | What is shared | Why | Where it is located |
|---|---|---|---|
| Yandex.Metrica | IP address, User-Agent, the address of the page you are viewing, click map and link clicks | Web analytics: counter 98354174. Loaded on every page of the site | Russia |
| IP address and User-Agent when the web fonts load on any page of the site; your account data if you sign in with Google | Rendering the interface fonts; Google sign-in | USA | |
| Telegram | Chat identifier and the text of a meeting notification | Delivering notifications — only if you connected Telegram yourself | UAE |
| VK | The account data passed on at sign-in | VK sign-in — only if you use it | Russia |
Only the first two rows are unconditional: the analytics counter and the web fonts load on every page. Telegram and VK receive data only if you connected those services yourself. Countries and the legal basis for transfers are covered in section 12.
8.1. Our own infrastructure and the services of our group
What is listed here is not a disclosure to third parties: it is processing inside the service and inside the operator's group. We describe it because you are entitled to know where your data physically ends up. A note on WebMoney: in this subsection it acts as infrastructure of the operator's group — the storage behind the "Files" widget and the service notifications in Keeper. As a sign-in provider WebMoney acts in a different role, external to us: there your data is processed by its own authentication service under its own rules — see section 3.
- The calendar service, the search index, the screenshot generator, the mail server, the databases and the cache are our own infrastructure.
- WebMoney sign-in, our side of the verification: when the ticket is verified we receive your WMID and IP address; the nickname and avatar for your profile are then fetched by WMID. The authentication itself happens on WebMoney's side and under its own rules — see section 3.
- WebMoney Keeper notifications: the recipient receives the notification text only — for example, that you granted them access to a widget. The contents of the widget are not sent anywhere.
- Files you upload to the "Files" widget are stored not on our main server but in a subsidiary service of the operator that runs under a white label. The folder in that storage is named after your account identifier, and access to it is granted to your WMID.
8.2. Reference lookups by domain name
To show a site's icon and information about it, the service makes reference lookups by the domain name of the bookmark you are saving. Such a lookup carries the domain name only — no user identifier, no full page address and nothing about who saved the bookmark. It contains no personal data, so these services are not recipients of personal data.
For the same reason the list does not include the external news feed source, the city-name suggestion service or the weather forecast service: what they receive is, respectively, a feed topic, the city search string you typed and a location name.
8.3. The websites you bookmark
Our server contacts those sites on its own behalf. Your IP address, your account and any other information about you are not sent there, so those sites are not recipients of your data.
The reverse matters: what the server retrieved from such a page — its full text and a screenshot — is stored by us. See subsection 4.4 for details.
9. Cookies and local storage
The service uses cookies and browser storage. Some of it keeps you signed in, some of it makes the interface work, and one item is for web analytics.
| Where it is stored | What exactly | Why | For how long |
|---|---|---|---|
| Cookie | access-token, client, uid, expiry, token-type | The marker that you are signed in. Set when you sign in through Telegram and when the calendar token is exchanged | Until the token expires — see section 13 |
| Cookie | authinfo — encrypted; contains the user identifier, the sign-in method and the domain | Passing sign-in details between the service domains | 1 hour |
| Cookie | The application session cookie | Server-side technical operation | Until you close the browser |
| Cookie | Yandex.Metrica cookies | Web analytics | Set and determined by Yandex |
| localStorage | The access token and the values related to it | So that you do not have to sign in every time you open the site | Until you sign out or clear the storage |
| localStorage | The return address after sign-in, the chosen language, the calendar theme, widget settings | Remembering your interface choices | Until the storage is cleared |
| localStorage | A cache of widget contents — including the list of your bookmarks | Fast rendering without reloading | Until the storage is cleared |
| sessionStorage | The password of an encrypted widget — in the clear | So that you do not have to retype it on every access to the widget | Until you close the tab |
| Service Worker cache | Interface files | Keeping the site usable on a poor connection | Until the version is updated or site data is cleared |
| Extension storage | Session data, settings and — if the permission was granted — a copy of your browser bookmark tree | Running the extension | Until the extension is removed or its data is cleared |
If you disable the cookies responsible for sign-in, you will not be able to stay signed in. That is a technical consequence, not a requirement of ours.
Back to top10. Legal bases for processing
We process personal data on the legal bases set out in Art. 6 GDPR. The basis is stated separately for each purpose.
| Purpose of processing | Legal basis |
|---|---|
| Creating an account, signing in, storing and displaying your content, synchronisation, search, the calendar, meeting notifications, storing uploaded files | Art. 6(1)(b) — performance of our contract with you (the terms of service) |
| Server logs, protecting the service against abuse, investigating failures | Art. 6(1)(f) — our legitimate interest in keeping the service working and secure |
| Automatically retrieving the title, description, icon, preview image, full text and screenshot of a page from your link; reference lookups by domain name | Art. 6(1)(f) — our legitimate interest in displaying bookmarks usefully. You have the right to object to this processing (Art. 21) — see section 15 |
| Publishing your profile on a publicly accessible page | Art. 6(1)(a) — your consent, which you give by a separate action and can withdraw at any time |
| Telegram notifications | Art. 6(1)(a) — your consent: you connect the channel yourself and can disconnect it |
| Web analytics (Yandex.Metrica) | Art. 6(1)(a) — consent. See the caveat below |
| Responding to lawful requests from public authorities | Art. 6(1)(c) — compliance with a legal obligation |
| Creating an account on the initiative of another user who is granting you access | Art. 6(1)(f) — legitimate interest in granting that access. At that moment there is no contract with you yet; you are informed by email (Art. 14) and may object immediately and demand erasure |
Caveat on web analytics: consent is the appropriate basis for this processing, but no mechanism for obtaining it in advance is implemented on our side, and the counter loads before you take any action. We state this plainly and do not claim that consent was obtained. Ways to limit the collection are in section 9.
11. Who else can see your data
By default your content is visible to you alone. Below are all the cases in which someone else can see it, and exactly what happens in each.
11.1. Sharing a widget
You can give another person access to your widget by entering their email address or WMID. The contents of the widget are not sent anywhere: they stay in the service and simply become visible to the person you shared with.
A