Privacy Policy
Last updated: 11/1/2026
Last updated: 1 November 2026
This policy explains what personal data Nesktop uses, why we use it, who receives it, how long we keep it and your choices. It is for your information, so you do not need to accept it. We collect as little data as we can.
It covers the Nesktop website, web app, browser extension and related features (the "Service"). It follows the Turkish Personal Data Protection Law (KVKK) and, where it applies to you, the EU/EEA GDPR. Turkish users also have a separate short Turkish notice (the KVKK Aydınlatma Metni).
1. Who is responsible
Nesktop is the name of the service. The party responsible for your data (the "controller") is the operator of nesktop.com:
- Website: nesktop.com
- E-mail for all privacy questions and requests: nesktopinfo@gmail.com
2. The short version
- We use your data to run your account and your canvases. We do not sell it and we do not use it for advertising.
- We do not use your notes or content to train AI models.
- Analytics run only if you say yes in the cookie settings.
- A few simple counters help us notice bulk copying and abuse. Counters only raise alerts. A person decides.
- You can view and delete your data in Settings, and export most of it.
3. What we use, why, and whether you must give it
| Data | Why we use it | Legal basis (GDPR) | Must you give it? |
|---|---|---|---|
| Account data: name, username, e-mail address, hashed password, language and account preferences; your Google account identifier if you choose Google sign-in | To create and run your account, sign you in, and send service e-mails | Contract (to provide the account and Service you asked for); consent for optional Google sign-in | Name and e-mail are needed to create an account. Google sign-in is optional. |
| Your content: bookmarks, folders, canvases, widgets, notes, live-background settings and the saved state of a live scene | To store and sync what you ask us to keep | Contract | You choose what you save. If you do not save content, there will be no saved content to display. |
| Friends and related features, each only while we have it switched on: friend requests and your friend list; the status you set; a free-text status message; the messages you send and receive (their text, the layout link if you attach one, the time and whether it was read); records of layouts you send to friends; and a short "typing" signal that is kept for a few seconds. A friend request can carry an optional note only while direct messages are on. We also keep existing records for the periods in Section 7. | To provide the features you use. Your friends see your name, username and status, and your free-text status message if that feature is on. A person who sends you a request sees your name and username. Messages and layouts you send are shown to their recipients. | Contract (to provide the features you asked for) | Entirely optional. Each feature can be on or off independently of the others. Messages and requests contain other people's data too (their names and what they write). We use it only to deliver and show it, and to handle reports, appeals and legal duties. |
| NAPP store comments and ratings (only while this feature is on and you use it): the comments and ratings you post | To show them in the NAPP store and to handle reports | Contract (to provide the feature you asked for) | Entirely optional. |
| Private layout links: a copy of the layout as it was when you created the link (folders, bookmarks, web links and widget arrangement), the validity dates of the link, a record that an account saved or applied it, and your name or username, which the preview shows | To let anyone who has the link see the preview, and anyone with a Nesktop account save or use the layout | Contract (to provide the sharing feature you asked for) | Entirely optional. "Private" means unlisted, not access-controlled. |
| Service e-mails: your e-mail address and delivery information | To send verification, password reset, security and account messages | Contract; legitimate interests | Needed to receive them. |
| Waiting list (only while registrations are closed and we offer the waiting list, and only if you join it): your e-mail address, the language of the page, the time you ticked the consent box, and the time of the e-mails we send you | To write to you once when registrations open, plus one short "you are on the list" confirmation. We delete your address 30 days after the opening e-mail, and at the latest 12 months after you join the waiting list. Every e-mail has a link that deletes your address at once. No tracking. | Consent | Entirely optional. |
| Security and abuse prevention: a keyed hash of your IP address, your e-mail domain, a flag for disposable e-mail domains and the result of the bot check at sign-up; sign-in sessions; one-time codes and links; server logs (which include IP addresses) and error records | To stop fake accounts, spam and attacks, and to find and fix faults | Legitimate interests (keeping the Service safe); legal obligation where one applies | Needed to use the Service. |
| Misuse signals: counts of requests per account and per keyed hash of an IP address in short time windows, notes about automation tools and repeated failed sign-ins | To notice bulk collection, automated access and copying (Terms, Section 6) | Legitimate interests (protecting the Service and its users). We keep only summaries, not content, for a short period, and a person reviews each case. | Created by how the Service is used. You can object (Section 9). |
| Freeze and appeal records: the text of your appeal, a request for a copy of your data, our decision | To handle your appeal fairly and to explain our decision | Legitimate interests; contract | Only if you appeal. |
| Content reports: the report, the name and e-mail of the person who made it, our decision | To handle reports of illegal or rule-breaking content (Report content) | Legitimate interests; legal obligation where one applies | A name and e-mail are asked for, with an exception for the most serious offences. |
| Invitations and rewards (only if you invite someone or are invited): the invitation code, who invited whom, the number of different days the invited account was active (counted by the Service itself, not by analytics), and rewards earned, started, used or expired | To run invitations and rewards and prevent misuse | Contract; legitimate interests (preventing misuse) | Optional. We keep this data while the account exists. |
| Support messages: what you write to us, any attachments, and messages we send you for support | To provide support and answer you | Contract; legitimate interests | You choose whether to contact support. Conversations with NESKTOP team accounts (support), including your replies in them, are separate from messages between users and stay available when direct messages are switched off. |
| Analytics (only with your consent): a first-party visitor cookie, the pages you visit, an approximate country, and your account identifier if you are signed in. With the same consent, a signed-in member is also counted once a day in a total of active members; that total holds no names or identifiers. | To find and fix errors, and to count which features are used | Consent | Entirely optional. |
| Consent and acceptance records: your cookie choice, the version of the policy shown, the time (kept on our server only if you are signed in); which Terms you accepted and when | To show later what you chose and accepted | Legal obligation; legitimate interests (proof) | Needed to use the Service. |
| On your device: browser storage for your preferences, caches and the sign-in session | To make the Service work | Contract (to provide the Service you asked for; see the Cookie Policy) | Needed for sign-in. |
We do not look for special categories of data (such as health or religion). If you put such data in your own notes or messages, we treat it like any other content and do not use it for any other purpose.
"Legitimate interests" means that we have a reason to use the data, such as security, and have assessed its impact on your rights and freedoms. You can ask us about that assessment at any time.
4. How we collect it
You give us most of it yourself: when you sign up, save content, write to us or change settings. Some comes from your browser and the Service as you use it (logs, approximate country, device type). Some comes from Google, if you choose Google sign-in. Some comes from other users through features that are switched on, for example when they send you a friend request, a message or a layout, or set a status message, comment or rating. The browser extension sends data only for the features you switch on (Extension document). Collection is partly automated, for example by logs and counters.
5. Who receives your data
We do not sell your personal data. We share it only with the recipients below. The service providers process it for the purposes shown, under their terms or data-processing terms.
| Recipient | What for | Country |
|---|---|---|
| OVH, hosting provider | Servers, storage and network. All main service data is stored here. | Germany (data centre) |
| Google (Gmail), e-mail delivery | Sending all service e-mails, including waiting-list e-mails if you join the waiting list. Your e-mail address and the text of the e-mail pass through Google's mail servers. | USA (Google LLC) |
| Sign-in with Google and optional Google Calendar and Tasks connections, only if you choose them | USA (Google LLC) | |
| Google favicon service | Fetching bookmark icons. The bookmark information sent is the bookmarked domain, not the full bookmarked address or page content. | USA |
| Visual Crossing | Weather information, using the location text you give the weather feature | To be confirmed |
| Lemon Squeezy and Stripe | Payments, only if we switch payments on | To be confirmed |
| Your friends and the recipients of your messages or layouts | Your name, username and status; your free-text status message if that feature is on; the messages and layouts you send them. Existing messages stay readable for the 30 days described in Section 7 after direct messages are switched off. Layout cards you sent keep working after that; only text sent with them is removed. | Wherever they are |
| People who have one of your layout links | The preview and the layout copy (Section 3) | Wherever they are |
We share data with an authority only when a valid legal request requires it, or in an emergency to protect someone's safety. If we ever add another recipient that handles personal data, we update this list before it starts.
6. Transfers abroad
Our main data and our backups are stored in Germany. Some recipients above process data in other countries. Seen from Türkiye, a German host is also a transfer abroad.
- Türkiye (KVKK article 9): Some of the recipients above are outside Türkiye; their countries are listed above. A row that says "To be confirmed" is a service we do not use yet; we name its country before it starts handling your data. These transfers are subject to KVKK article 9. You can ask us for details about them.
- EU/EEA users (GDPR): Our main data and our backups are stored in Germany (EEA). Other recipients process data in the countries shown in Section 5. You can ask us for a copy of the safeguards we use.
7. How long we keep data
These are the periods that apply today.
- Account and saved content: while your account exists. They are deleted when you delete the account in Settings. The record of which Terms you accepted goes with it.
- Friends and messages: while direct messages are on, a message stays until it is deleted. When direct messages are switched off, existing messages stay readable and are included in your data export for 30 days from the switch-off, unless they are deleted earlier under the rules below. After those 30 days we delete them from our active systems; backups follow the backup rule below. When direct messages are switched off, we show every member the exact deletion date in the Service. Typing indicators stop, and new friend requests can no longer carry a free-text note (a note already sent stays visible to its recipient until the request is answered or withdrawn). Layout cards are not deleted after those 30 days: the card stays, so the recipient can still open the layout while its link is valid, but any text sent with it is removed. The 30-day rule does not apply to conversations with NESKTOP team accounts (support), including your replies in them. When you delete a message or a chat, it disappears for you. It is removed for good once both sides have deleted it, or when the sender unsends it. Friend entries stay until a friend is removed. Records of requests that were declined or cancelled stay until one of the two accounts is deleted. When an account is deleted, its friend entries and the messages it sent and received are deleted too, so they disappear for the other person as well.
- Private layout links: the stored copy and the record of who saved it stay until you delete your account. A revoked or expired link stops working, but the stored copy remains until then.
- Unverified accounts: we may delete accounts that stay unverified, after a notice to you.
- Accounts suspended for abuse: if an administrator deletes the account, deletion happens after at least 7 days of suspension plus a 30-day restore window.
- Sessions, one-time codes and links: they stop working when they expire or when you sign out (sessions up to 90 days after your last visit, e-mail verification links 24 hours, password reset links 30 minutes, pairing codes 2 minutes). The expired record may stay in our database until we clean it up.
- Sign-up protection data: 90 days.
- Misuse signals: deleted after 30 days, whether our misuse protection is switched on or off.
- Appeals: the text of an appeal is erased 180 days after our decision, whether our misuse protection is switched on or off.
- Content reports and our decisions on them: as long as needed to handle the report and any appeal.
- Analytics events: about 90 days.
- Consent records (with policy version): older records are deleted after 180 days. Your latest record stays while your account exists.
- Server logs and error records: about 30 days.
- Security and audit events: 12 months, or longer while needed for security.
- Support messages: until the request is closed, and as long as needed to handle follow-ups. Conversations with NESKTOP team accounts stay available when direct messages are switched off.
- NAPP store comments and ratings: until you delete them or your account is deleted. While the feature is switched off they are hidden, not deleted.
- Feedback when you delete an account: if you give optional feedback, we do not keep it.
- Backups: kept on our server in Germany with restricted access for up to 30 days, then deleted. Data you deleted may remain in a backup until then.
We may keep data longer where the law requires it.
8. Counters and automated decisions
Counters only raise alerts. No decision with legal or similarly significant effect is made solely by automated means. A person reviews each case and every appeal. We keep only summaries: a count, a kind, a time window and a small piece of evidence. We delete them after 30 days, whether our misuse protection is switched on or off. We never store the content of requests, full addresses, or a raw IP address in them.
9. Your rights and how to use them
You have the right to:
- ask whether we process data about you and get a copy;
- ask why we use it and who receives it, at home or abroad;
- have wrong or incomplete data corrected;
- have your data erased or destroyed, and ask us to tell the recipients;
- limit our use of it, or object to it, in particular where we rely on legitimate interests or where a result against you comes only from automated analysis;
- receive your data in a common format (portability);
- withdraw consent at any time, without affecting the lawfulness of processing carried out before you withdrew it;
- ask for compensation if you suffer loss from unlawful use of your data (KVKK).
You can view and delete much of your data yourself in Settings, and export most of it. The export includes the friend messages you can still see. It does not yet include your friend list and your layout links. To request those records or get help with any other data request, write to nesktopinfo@gmail.com from the e-mail address of your account. We may ask you to verify your identity to protect your data. We answer within 30 days, and in normal cases it is free.
In Türkiye, you must apply to us before making a complaint to the Personal Data Protection Board (Kurul), as required by KVKK article 14/2. We answer within 30 days. If we reject your request, you find our answer inadequate, or we do not answer in time, you may complain to the Board within 30 days of learning of our answer and, in any event, within 60 days of your application to us. If we do not answer within 30 days, you may complain once that period ends, within the same 60-day limit. In the EU/EEA, you may contact your national data protection authority directly; you do not have to apply to us first.
10. Security
We use HTTPS/TLS for network traffic, access controls on our systems, hashed passwords, access-restricted backups and a secure, HttpOnly session cookie. No system is completely secure. If a breach affects your personal data, we tell the authority and you, as the law requires.
11. Age
Nesktop is for adults aged 18 and over and is not meant for children. We do not knowingly collect children's data. If you think a child has an account, write to nesktopinfo@gmail.com and we will act.
12. Browser extension
The extension reads browser data only for the features you switch on and, where required, the optional permission you grant. It does not collect your browsing history. See the Extension document.
13. Changes to this policy
We may update this policy. We post the new version, update the date and, for material changes, tell you in the Service or by e-mail before they apply. You do not need to accept this policy. If we ever want to use your data in a new way that needs your consent, we will ask you for it separately.