Privacy
This service counts likes on blog posts. It is intentionally minimal, and so is the data it keeps.
Visitors who click a like button
- We store only the liked domain and normalized path, the time, and a salted one-way hash of your IP address. URL query strings, fragments, and userinfo are discarded. The hash is only used to prevent duplicate likes and cannot be reversed into your IP.
- The public likes API sets no cookies and does not track you across sites.
- IP addresses are used transiently for rate limiting and are not kept.
Registered users (blog owners)
- We store your username, email address and a hash of your password.
- Your email is used to operate the service (e.g. notifications you opt into). It is never shared.
- The dashboard uses a session cookie strictly for login.
Deleting your account
When signed in, choose Delete account under your username in the navigation. Export any projects you want to keep from the dashboard first. Type DELETE to permanently remove your account, all owned projects, domains and likes, your Pro interest, and your account-linked verification diagnostics. You will be signed out on all devices. You can cancel before submitting.
Old sessions lose access immediately. The current browser cookie is expired; other devices' cookies are expired when they next contact the service. Unused session records remain until normal session cleanup. Shared IP-based abuse controls keep their normal expiry.
Deletion affects live account data. Routine database backups rotate after 14 days when backups run successfully. Separately retained manual backups have no automatic expiry. Application and hosting logs follow operator retention, and delivered email/XMPP notifications remain with their recipients; account deletion does not recall them. Contact the site owner about historical copies. Verification diagnostics for other accounts normally expire after 30–31 days.
Website analytics
We use Google Analytics to measure use of this website. On the production website, we also use Microsoft Clarity to understand page interactions through usage metrics, heatmaps and limited session recordings. These analytics are not included in the embeddable like button or added to your website.
Clarity receives page and device information and interaction events, such as clicks and scrolling. We mask page content, including account details, and Clarity masks form inputs. We send no custom user identifiers to Clarity.
We configure Clarity with analytics and advertising storage denied, so it operates without Clarity cookies or persistent cross-page session identifiers. This limits its session recording features. This setting applies to Clarity; login cookies and Google Analytics are separate. For details about Microsoft's processing, see the Microsoft Privacy Statement.
Contact
To ask about or request deletion of your data, contact the site owner through aaron.com.es.