Privacy policy

Data controller

• Owner: Pedro Martínez Millán
• Tax ID (NIF): 23813517F
• Address: C/Creu Roja 1, 46014, Valencia, España
• Email: soporte@agrupa.link

Data of account holders

If you create an account, we process the following data:

• Account data: username, email address and password, which is stored transformed with a hashing algorithm and never in plain text. If you sign in with Google, Google provides us with your email address and an identifier for your Google account; we do not receive your password.
• Your page content: display name, bio, profile picture, links, cards, folders, blocks, social profiles, theme and other settings. This content is public: anyone can see it at agrupa.link/username, it may appear in search engines and, if you turn it on, in the "Explore" directory, with the category and city you choose.
• Anonymous messages: those you receive in your page's inbox, your replies, the ones you choose to publish on your page and any blocks and reports you make. Images for sharing a reply, a result or an achievement are created in your browser and we do not store them.
• Contact forms: the fields you choose to ask for, the requests you receive, whether you have marked them as handled or as spam, the blocks you make and the notifications you turn on.
• Subscriptions and bookings: your page's subscriber lists, the emails you send them, countdown reminders and the appointments people request, with their status.
• Preferences: language, time zone, light or dark dashboard mode, the template chosen when signing up and display options.
• Dashboard activity: the date of each visit and the type of change made, without IP address or browser data, and the dates of a few milestones (first link, first visit, first click and last visit).
• Subscription and gifts: plan, billing period, status, renewal dates and Stripe customer and subscription identifiers and, if you buy or redeem a gift code, the code, who bought it and who redeemed it. You enter your card details in the Stripe form and they never reach our servers.
• Support: the messages you send us from the dashboard or by email, the page you write from and the browser you use, so we can reproduce errors.
• Referral programme: which account invited you, if you arrived through an invitation link, and the Premium months you earn by inviting others.
• Sign-up source: the agrupa.link page you created your account from, the domain of the website you came from and, if you came from a campaign, its name. It is sent with the sign-up form itself, without cookies, and we only use it to learn which channels work.
• Profiles and team: the additional profiles you create from your account, the people you give access to edit a page (their username and role) and the pages of others that you can edit.
• Alerts: the devices on which you turn on alerts (the address the browser assigns for sending them).

The username, email and password (or Google sign-in) are required to create the account; without them we cannot provide the service. The rest of the information on your page is optional.

Data of visitors to public pages

To give each account holder statistics about their page, when someone visits a public page or a short link, or clicks one of its links, we record the date and time, the link clicked, the device type (mobile, tablet or computer), the referring domain and the country, which is derived from the IP address using our own database, without querying third parties.

We do not store the IP address. To count unique visitors we calculate a code (hash) from the IP and the date that changes every day, so it cannot be used to follow a person from one day to the next. Public pages do not use tracking cookies or third-party analytics tools.

Page owners only see aggregated figures (visits, clicks, countries, devices and referrers), never data about a specific visitor.

If the owner tests two titles for a link, we count how many times each version is seen and tapped, without any visitor data. If a link leads to a different destination depending on country or device, we decide it on the spot with that same data, without storing anything else.

Videos, songs and maps embedded in a page do not load until you tap them. When you do, the platform that provides them (YouTube, Vimeo, TikTok, Spotify, SoundCloud, Apple Music or Google Maps) receives your IP address and may use its own cookies.

Data of people who send anonymous messages

If a page has an anonymous inbox, anyone can write to its owner without creating an account. We store the text of the message, the date and time, and the inbox it arrives through.

To curb harassment and spam we also store two codes with the message: one calculated from the IP address (for IPv6, from the part that identifies the network) and another from a random identifier saved in your browser when you send it. They are keyed hashes that differ for each recipient: they do not reveal the IP address or allow messages sent to different accounts to be linked. We do not store the IP address.

With these codes we can limit the number of messages sent, discard repeated messages and apply the blocks decided by the inbox owner. An automatic filter sets aside messages containing insults, threats or links in a "Filtered" folder; the owner can still see that folder and the filter has no other effect.

The inbox owner sees the message text and the date, never the codes or any data revealing who wrote it. They can reply and share the message with their reply, as an image and without your data, on other networks, or publish it on their page together with their reply. If they have turned it on, they also receive the text as an alert in their browser. That is why we recommend not including personal data about yourself or others in the message.

If the owner reports a message, we review it using its text, the date, the username of the person reporting it and a fragment of the sender's code, which reach us through an internal Telegram notification or by email.

Since we do not ask for any data to write a message, we cannot tell which messages are yours without your help. If you want to exercise your rights over a message you sent, write to us at soporte@agrupa.link stating the page, the approximate date and the text.

Data of people who write through a contact form

If a page has a contact form, anyone can send a request to its owner without creating an account. We store what you write in the fields the owner has chosen (for example, name, email, phone, company or message), the date and time and the form it comes through.

The controller of that data is the page owner, who receives it to handle your request. agrupa.link processes it on their behalf, as a processor (art. 28 GDPR): it keeps it in their inbox and, if they have turned it on, notifies them by email or Telegram with the content of the request. If you give your email, the notification uses it as the reply-to address, so they can answer you directly, and the owner can also reply from agrupa.link or from Telegram: we email you their reply, with your message quoted and their email address so you can answer them.

If the owner has turned it on, we also alert them in their browser, with the name or email of the person writing.

To curb spam we also store, as with anonymous messages, two codes (hashes) with a secret key: one calculated from the IP address and another from your browser's random identifier. They do not reveal the IP and are only used to limit submissions, discard duplicates and apply the blocks the owner decides. An automatic filter sets aside in "Spam" requests with lots of links, insults or threats; the owner can review and restore them.

To exercise your rights over that data, contact the page owner. If you cannot reach them, write to us at soporte@agrupa.link stating the page, the approximate date and the email or phone number you gave, and we will forward your request to them.

Data of people who subscribe or ask for a reminder

If a page has a subscription block or a countdown with "Notify me", you can leave your email to get its news or a single reminder when the date arrives. We store your email, language, the date and the page, and send you an email to confirm; if you do not confirm within 7 days, it is deleted.

The owner of the page is the controller of that data and decides when to write to you. agrupa.link processes it on their behalf, as a processor (Art. 28 GDPR): it keeps the list, sends the emails the owner writes under their name, with their address so you can reply, and sends you the reminder you asked for. The owner sees your email in their dashboard, can export the list and, if they have turned it on, get an alert in their browser.

Every email includes a one-click unsubscribe link. After you unsubscribe, your address stays marked so you are not written to again, until the owner deletes it or you subscribe again. Countdown reminders are deleted 30 days after being sent.

To curb abuse we also store a keyed hash calculated from your IP address, which does not reveal it and is deleted after 30 days. To exercise your rights, contact the owner of the page; if you cannot reach them, write to us at soporte@agrupa.link.

Data of people who book an appointment

If a page has a bookings block, you can request an appointment without creating an account. We store your name, your email, your phone number and message if you give them, the chosen day and time, the language and the status of the booking. We email you the request, the confirmation or the decline, with a link to cancel it.

The controller is the owner of the page, who receives the booking to handle it; agrupa.link processes it on their behalf, as a processor (Art. 28 GDPR). If they have turned it on, we alert them by email, on Telegram or in their browser. Nobody else sees your booking on the page.

To curb abuse we store, as with forms, two keyed hashes: the one calculated from your IP is deleted after 30 days. Declined or cancelled bookings are deleted 30 days after the appointment date and the rest one year after it, or earlier if the owner deletes them or closes their account. To exercise your rights, contact the owner; if you cannot, write to us at soporte@agrupa.link.

Data of visitors to the agrupa.link website

On the home page, the guides and these legal pages we use Google Analytics to understand how the site is used (pages viewed, buttons clicked and how far people read), only if you accept it in the cookie notice. If you do not accept, it is not loaded. See the Cookie policy for details.

If you write to us at soporte@agrupa.link, we process your address and the content of your message to reply to you.

Purposes and legal bases

• Creating and maintaining your account, publishing your page and providing the service, including statistics and necessary emails (verification, password recovery, account notices and support replies): performance of the contract you accept when signing up (art. 6.1.b GDPR).
• Managing the Premium subscription, payments and invoicing: performance of the contract and compliance with accounting and tax obligations (art. 6.1.b and 6.1.c GDPR).
• Measuring visits and clicks on public pages to show statistics to their owners: legitimate interest of agrupa.link and of each owner in knowing the reach of their page, with minimised data that does not identify visitors (art. 6.1.f GDPR).
• Delivering anonymous messages to their recipient and protecting them from harassment and spam with the automatic filter, blocks and sending limits: legitimate interest of the sender in getting their message through and of the recipient in an inbox free from abuse (art. 6.1.f GDPR). For the account holder, the inbox is part of the service (art. 6.1.b GDPR).
• Storing the requests sent through contact forms and notifying their recipient: we do this on behalf of the page owner, who is the controller of that data and receives it to handle what is asked. Sending limits, blocks and the spam filter are based on the legitimate interest in protecting the form from abuse (art. 6(1)(f) GDPR).
• Protecting the service, preventing abuse and fraud, limiting the number of requests and detecting repeated sign-ups: legitimate interest (art. 6.1.f GDPR).
• Managing the referral programme: performance of the contract for the inviting account and legitimate interest for the invited account (art. 6.1.b and 6.1.f GDPR). The cookie that remembers the invitation is only set with your consent.
• Sending you welcome emails, tips and reminders about using your page (for example, if it has no links yet or has gone without visits for a while) and the end-of-trial notice: legitimate interest in helping you get the most out of the service you use (Art. 6.1.f GDPR). Every email includes a link to stop receiving them.
• Measuring dashboard use and testing improvements with some accounts before rolling them out to all: legitimate interest in improving the service, with internal data that is not shared with anyone (Art. 6.1.f GDPR).
• Storing a page's subscriptions and bookings, sending their emails and alerting the owner: we do this on behalf of the owner, who is the controller of that data, as with contact forms.
• Showing your page in the "Explore" directory and sending alerts to your browser: these are features you choose to turn on, as part of the contract (Art. 6.1.b GDPR).
• Website analytics with Google Analytics: your consent (art. 6.1.a GDPR), which you can withdraw at any time.
• Handling content reports and requests from authorities: compliance with legal obligations (art. 6.1.c GDPR).

We do not make automated decisions with legal effects on you, we do not build profiles for commercial purposes and we only write to you about the service itself.

Recipients

We do not sell or share your data with third parties, unless required by law. To provide the service we rely on the following providers, who only access the data needed for their function:

• Hostinger International Ltd. (Cyprus): hosting of the website, database and email.
• Cloudflare, Inc. (USA): content delivery network and attack protection, through which requests to the site pass.
• Stripe Payments Europe, Ltd. (Ireland): payment of the Premium subscription. Stripe also processes payment data as an independent controller to prevent fraud and meet its legal obligations.
• Google Ireland Limited: Google sign-in, if you choose it, and Google Analytics, only if you accept it.
• Telegram: internal notifications of new sign-ups (username and country), of support messages sent from the dashboard and of reports of anonymous messages (the reported text and the username of the person reporting it).
• Telegram, also: if a page owner turns on Telegram alerts, the content of each contact request, booking or subscription reaches their own chat with the agrupa.link bot.
• Browser notification services (Google, Mozilla, Apple or Microsoft): if you turn on alerts on a device, we send them a signal with no content; your browser then downloads the text directly from agrupa.link.

Some of these providers may process data outside the European Economic Area. In that case, the transfer is based on an adequacy decision of the European Commission, such as the EU-US Data Privacy Framework, or on the standard contractual clauses approved by the Commission (art. 45 and 46 GDPR).

Retention periods

• Account and page content: for as long as the account exists. When you delete it, your page and additional profiles, links, images, statistics, the messages, requests, bookings and subscribers received and your support messages in the dashboard are deleted immediately.
• After deletion we only keep the username, a code (hash) of the email address from which the address cannot be read, the number of links, whether the account was Premium and the sign-up and deletion dates, for internal statistics and to detect repeated abusive sign-ups.
• Individual visit and click records: 90 days. They are then aggregated into daily totals without any visitor code, which are kept for 2 years.
• Dashboard activity log: 90 days.
• Anonymous messages: until the inbox owner deletes them or deletes their account. Those set aside in "Filtered" are deleted automatically after 30 days, unless they have been reported.
• Codes of the sender of an anonymous message: the one calculated from the IP address is deleted after 30 days; the browser one is kept with the message. Blocks last until the inbox owner removes them.
• Contact requests: until the form owner deletes them or deletes their account. Those set aside in "Spam" are deleted automatically after 30 days.
• Codes of whoever sends a contact request: the one calculated from the IP is deleted after 30 days; the browser one is kept with the request. Blocks last until the form owner removes them.
• Page subscriptions: those pending confirmation are deleted after 7 days; confirmed ones and unsubscribes, when the owner deletes them or closes their account. Countdown reminders, 30 days after being sent.
• Bookings: declined or cancelled ones, 30 days after the appointment date; the rest, one year after that date. Codes calculated from the IP in subscriptions and bookings, 30 days.
• Pending browser alerts: 2 days. Devices with alerts turned on: until you turn them off or the browser stops accepting them.
• Counters used to limit the number of requests, with a code calculated from the IP address or the account: 2 days at most.
• Subscription, gift code and billing data: as long as commercial and tax law requires, up to 6 years.
• Signed-in session: 7 days at most, or until you sign out.
• Emails sent to the support address: for as long as needed to handle the request.

Your rights

You can exercise your rights of access, rectification, erasure, objection, restriction of processing and portability at any time, and withdraw any consent you have given without affecting the lawfulness of prior processing. Write to us at soporte@agrupa.link stating which right you wish to exercise; if we have reasonable doubts about your identity, we may ask for additional information. We will reply within one month at most.

You can exercise many of these rights from the dashboard: edit your data and your page, change your email or delete the account with all its content.

If you believe we have not handled your request properly, you can lodge a complaint with the Spanish Data Protection Agency (www.aepd.es).

Minors

You must be at least 14 years old to create an account (art. 7 LOPDGDD). If we detect an account belonging to someone under that age, we will delete it.

Security

We apply technical and organisational measures appropriate to the risk: encrypted connections (HTTPS), passwords stored as hashes, protected sessions, protection against forged requests and rate limiting.

Changes to this policy

If we change this policy significantly, we will say so on this page with the new update date and, if it affects account holders, we will let them know by email.