Privacy Policy
Last updated 14 October 2026
SharedLayers lets people leave comments pinned to specific places on a web page, through a Chrome extension and a web dashboard. This policy explains what we collect, why, and what you can do about it.
Who is responsible
The data controller is ANY Jacek Troszyński, ul. Stanisława Barańczaka 3a lok. 28, 60-537 Poznań, Poland. For anything in this policy, including requests about your data, write to [email protected].
What we collect
Your account
- Email address, used to sign in, to send you invitations, and to contact you about the service.
- Display name and, if you set one, a profile picture.
- A password, stored only as a cryptographic hash. We never see or store the password itself.
- If you sign in with Google, we receive your email address, name and profile picture from Google. We never receive your Google password, and we ask for no access to Gmail, Drive or any other Google service.
Your comments
- The text of comments and replies you write.
- The address of the page you commented on, and a technical description of the element you pinned it to, which is a CSS selector and coordinates. This is how a comment finds its spot again on your next visit.
- The hostname of sites you create a comment layer for.
- When comments were created, resolved, and which ones you have read.
- A picture of the part of the page you were looking at when you left a comment, drawn in your browser at that moment, so the comment still makes sense after the page changes. A site that installs the SharedLayers script can turn these pictures off.
- Images you attach to comments and replies. Your browser shrinks each one and saves it again before it is uploaded, so the original file is not kept, and neither is information stored inside it, such as where a photo was taken.
Nothing is recorded on a page unless you leave a comment on it, and then only what is listed above. We do not collect form values or your browsing history.
Improve, if you use it
On Pro, the Improve button under the comment and reply boxes rewrites what you have typed so it reads clearly. When you press it, the text in the box and the names of anyone it tags are sent to Anthropic, whose Claude model does the rewriting, and the rewrite comes back to the box. Nothing is sent unless you press it, and nothing else about the page or the layer goes with it. We keep neither the text sent nor the rewrite; what you then post is kept like any other comment. We count how many times each account uses Improve each day, to apply a daily limit. Anthropic handles the text under its commercial terms, which do not allow it to train its models on it.
Jira and ClickUp, if you connect them
On Pro, you can connect your own Jira or ClickUp account on the Integrations page and send a comment there as an issue. When you connect, Atlassian or ClickUp tells us your account's ID, name, email address and picture, and which Jira sites or ClickUp workspaces you allowed, and gives us access tokens. We keep those so we can show you which account is connected, and the tokens encrypted, so that only our server can use them. We use them only to do what you ask: list the projects and lists you can add to, create the issue you send, and check whether it is done.
When you send a comment, the issue is created in your name and contains the comment, its author's name, the replies so far, the address of the page, the element it is pinned to, the layer's name, your name, a link back to the comment and, when there is one, the picture taken of the page. Every few minutes we ask Jira or ClickUp whether issues you sent are done; when one is, the comment is resolved in your name with a reply saying so. Everyone who can read the comment can see the issue's key, title, list or project and status. For a Jira account, we ask Atlassian each week whether the account was closed or changed, as Atlassian requires, and delete what we keep about a closed one.
Disconnecting deletes the account details and tokens we keep. Issues already created stay in Jira or ClickUp, under their terms, and we keep the link to them so the comment still shows it. Atlassian and ClickUp are your providers, not ours: what is in your Jira or ClickUp is governed by your agreement with them.
Slack, if you connect it
When you connect Slack on the Integrations page, Slack tells us which workspace it is and your Slack user ID there, and gives us a token for the SharedLayers app in that workspace, which we keep encrypted. We use it only for what you or a layer’s owner turned on:
- A layer whose owner chose a Slack channel has each new comment posted there, with its author’s name, the words, the page address, the element and the layer’s name, the picture taken of the page, and a link back; its replies and whether it is resolved follow in the message’s thread. Everyone in that channel can see them, under Slack’s terms.
- A link to a comment pasted in Slack gets a preview with the author’s name, the words, the page and whether it is resolved, but only for someone whose Slack is connected to an account that can read the comment. Everyone in that conversation then sees the preview.
- For each layer where you choose Slack in the layer’s settings, your comment notifications from it are sent to you in Slack, with the same content an email would carry, as well as or instead of by email, as you choose.
Disconnecting removes your Slack user ID from your account. Removing the SharedLayers app from a Slack workspace deletes its token and every channel setting that used it. Messages already posted stay in Slack. Slack is your workspace’s provider, not ours: what is in your Slack is governed by your agreement with Slack.
Invitations
When you invite someone, we store the address you typed so the invitation can be sent and accepted. If they never accept, the invitation expires after seven days.
Guest access
You can join a layer with an access key and a display name, without an account. Guest accounts have no email address attached, and we cannot contact you.
If you buy Pro
Pro is sold by Paddle, our online reseller and merchant of record, so the purchase is made with Paddle, not with us. Paddle collects what it needs to take the payment and issue the invoice, such as your name, email address, country, billing address and payment details. It handles that data as an independent controller under its own privacy policy. We never receive your card or bank details.
From Paddle we receive and keep your Paddle customer and subscription IDs, your plan, its billing period, how many domain blocks it covers, and the dates it renews or ends. We use them to switch your plan on and to show them on your Plan page.
The Plan page in the dashboard loads Paddle's script to show prices and to open the checkout, and the checkout itself is run by Paddle. Paddle may use cookies or similar technology there to process the payment and prevent fraud.
What the extension can do, and what it does
The Chrome extension requests access to all sites. It needs this because a comment can be left on any page you choose, and the permission cannot be narrowed to a list of sites in advance. In practice the extension reads a page only when you place a comment on it: the address of the page, the element you click with a short piece of its text, and the picture of what is on screen at that moment described above.
Apart from that, it does not read page content, inject anything into pages you have not commented on, or send anything anywhere except to our own service.
Why we are allowed to hold it
| Data | Purpose | Basis (GDPR Art. 6) |
|---|---|---|
| Account details | Give you an account and sign you in | Performance of a contract |
| Comments and layers | Provide the service itself | Performance of a contract |
| Invitation emails | Deliver an invitation you asked us to send | Legitimate interest |
| Service emails | Confirm your address, reset a password | Performance of a contract |
| Subscription details from Paddle | Give you the plan you paid for | Performance of a contract |
| Text sent to Improve | Rewrite it when you ask | Performance of a contract |
| Jira or ClickUp account and the comments you send there | Create the issues you send and resolve their comments when they are done | Performance of a contract |
| Slack workspace and user ID, and the comments posted there | Post a layer’s comments to the channel its owner chose, preview comment links, send you notifications | Performance of a contract |
Who else processes it
We use a small number of providers, each acting on our instructions:
| Provider | What for | Where |
|---|---|---|
| Supabase | Database, authentication, file storage | EU |
| Cloudflare | Hosting the website and dashboard, and DNS for sharedlayers.com | Global |
| Resend | Sending email | EU/US |
| Anthropic | Rewriting text with Improve, when you press it | US |
| Sign in with Google, if you use it | US |
Paddle is not in this table because it does not act on our instructions. As the seller of Pro, it decides for itself how to handle what it collects at checkout (see If you buy Pro above).
We do not sell your data, and we do not share it with advertisers. Transfers outside the EEA rely on the European Commission's Standard Contractual Clauses.
How long we keep it
- Account data: until you delete your account, with Delete account on My profile in the dashboard. An account with no comments and no layers is deleted straight away. Any other is deleted 14 days later, and until then you can sign in and cancel. The layers you own go with it, with their comments. The comments and replies you left in other people's layers stay, shown as “Deleted user” with a number and without your name, email or picture. Your email address is free to sign up again.
- Comments: until you or the layer's owner delete them.
- Deleted layers: hidden from everyone immediately, and erased permanently once the recovery window of seven days has passed.
- Unaccepted invitations: seven days.
- How often you used Improve each day: as long as your account exists. The text itself is not kept.
- Subscription details: as long as your account exists. Paddle keeps its own records of your purchases, including invoices, for as long as tax law requires.
Your rights
You can take a copy of your data and delete your account yourself, on any plan, from My profile in the dashboard. Download my data saves your data as a JSON file. It holds your profile, the layers you own with every comment and reply in them, the comments on your sites outside any layer, and what you wrote in other people's layers. Pictures and attached images are listed by where we store them rather than included.
Under the GDPR you may ask for a copy of your data, correct it, delete it, restrict or object to how we use it, or receive it in a portable form. Write to [email protected] and we will respond within one month. You can also complain to your national supervisory authority: in Poland, the President of the Personal Data Protection Office (UODO).
Cookies
We set no advertising or analytics cookies, and use no third-party trackers. To keep you signed in, your browser stores a session token in local storage rather than a cookie. It is required for the service to work and is cleared when you sign out. Paddle's checkout on the Plan page may set cookies of its own, which Paddle's policy covers (see If you buy Pro above).
Children
SharedLayers is not intended for anyone under 16.
Changes
If we change this policy in a way that affects you, we will say so on this page and, where the change is significant, by email.