Privacy Policy
Last updated: 22 October 2026
1. Who we are
LinkSharing is a service of Maksym Domin, who operates linksharing.top and its subdomains and is the data controller for the purposes of this policy. We host small business pages free of charge.
For any question about this policy, or to ask us to delete your data, write to preventorua@gmail.com. We answer within 30 days.
2. What this policy covers
This policy covers two different things. Read the part that applies to you.
- Visitors and page owners — people who open a page on linksharing.top, and businesses whose page we host. See sections 3 to 5.
- Google account data — data our internal tools read from Google APIs after a Google account owner grants access. See section 6. This is the section the Google API review concerns.
3. Data we collect from visitors
| What | Why | How long |
|---|---|---|
| IP address, browser identification, requested address, date and time | Web server logs. Needed to deliver pages, find faults and stop abuse. | 14 days, then deleted automatically |
| Page views, referring site, approximate region | Visitor statistics. We run our own analytics on our own server. The IP address is shortened before it is stored. | 12 months |
We do not use advertising cookies. We do not sell visitor data. We do not pass visitor data to advertising networks or data brokers.
4. Data on the hosted pages
A hosted page shows business information: company name, services, address, telephone number, opening hours and a link to a public map listing. This information is business contact data that the business publishes about itself.
If you are the business and you want your page changed or removed, write to preventorua@gmail.com. We remove the page and its subdomain within 7 days of a confirmed request.
5. Who we share data with
We share personal data with nobody, except in these two cases:
- Our hosting provider. The servers stand in Germany. The provider processes data only on our instruction.
- A legal authority, when the law requires it.
We do not sell personal data. We do not transfer it for advertising.
6. Google user data
We operate internal tools that work with our own Google accounts and our own Google properties. A Google account owner grants access with the standard Google sign-in screen. No data is read from any account that has not granted access.
6.1 What we access, and why
| Google service | What the tool does |
|---|---|
| Search Console | Reads search statistics for websites we own. Submits sitemaps for those websites. |
| Drive | Reads and writes our own working files and spreadsheets. |
| Gmail | Reads and sends mail in our own mailbox, for our own correspondence. |
| Calendar | Reads and writes entries in our own calendar. |
| Admin SDK | Manages users and groups in our own Google Workspace domain. |
| Merchant Center | Reads and updates our own product listings. |
| Site Verification | Confirms that we own a website before we add it to Search Console. |
6.2 What we store
We store the access credential that Google issues after sign-in. It sits on our own server, in a file that only the server administrator can read. It is never sent to a third party and never put in a public code repository.
Content we read through a Google API — a message, a file, a statistics row — is processed while the task runs and is not kept afterwards, unless the task's own purpose is to save it to our own storage.
6.3 Limited Use
LinkSharing's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
In plain words, this means all of the following:
- We do not sell Google user data.
- We do not transfer Google user data to anyone, except where it is needed to run the service, to follow the law, or as part of a merger that the account owner is told about first.
- We do not use Google user data for advertising, and we do not build advertising profiles from it.
- We do not use Google user data to train generalised artificial intelligence or machine learning models.
- No person reads Google user data, except to fix a fault the account owner reported, to meet a legal obligation, or when the data is aggregated and carries no personal detail.
6.4 How to withdraw access
The account owner can withdraw access at any moment at myaccount.google.com/permissions. Our tools then stop working with that account at once. To have the stored credential deleted as well, write to preventorua@gmail.com. We delete it within 7 days and confirm in writing.
7. Your rights
Under the General Data Protection Regulation you may ask us to show you your data, correct it, delete it, or stop processing it. Write to preventorua@gmail.com. If you are not satisfied with our answer, you may complain to a supervisory authority. In Portugal this is the Comissão Nacional de Proteção de Dados, cnpd.pt. You may also complain to the authority of the country where you live.
8. Security
Pages are served over HTTPS. Administrative access to the server needs a cryptographic key; passwords alone are not accepted. Credentials are kept outside the published website directory.
9. Children
The service is for businesses. It is not directed at children, and we do not knowingly collect data from children.
10. Changes to this policy
If we change this policy, we change the date at the top of the page. A change that affects Google user data is published here before it takes effect.