Privacy Policy

Last updated: September 27, 2026

Linkly (“the App”, “we”) is a Shopify application that adds buy-anywhere external link buttons to product pages and product cards. This policy explains what data the App stores, why, how long we keep it, and how it can be deleted.

1. Data we store

The App stores configuration that the merchant enters, plus an anonymous daily click counter. We do not collect customer names, email addresses, phone numbers, shipping or billing addresses, IP addresses, user agents, or any payment information. We do not use cookies or any tracking identifier for customers.

FieldWhat it isWhy
Product referenceShopify product ID, product title and handleShow which products already carry buttons in the app admin
Button configurationButton label and destination URL you enter, plus display options (new window, position, style)Render the buttons on your storefront
Anonymised click countsA per-day counter for each button position (for example “button 1 on 2026-09-27: 14 clicks”)Show click statistics in the app admin (Pro)

Click counts are aggregated by day and contain no identifier of any kind — we cannot tell two visitors apart, and we cannot link a click to an order, a session or a person.

2. How we use it

Configuration data is used solely to render your buttons on your own storefront. Click counts are used solely to display statistics to the merchant who installed the App. We do not sell data, do not use it for advertising, and do not share it with third parties.

3. Link masking and redirects

If you enable link masking (Pro), the App renders an internal /go/<token> address and redirects visitors to the destination URL you configured. Those redirect responses are marked noindex and no-store, are not logged with any visitor identifier, and are only counted in the daily aggregate described above. Destinations are restricted to http and https URLs.

4. Retention

Configuration and click counts are kept for as long as the App remains installed. There is no separate customer profile to retain, and no analytics identifier that outlives the merchant’s configuration.

5. Deletion

6. Security

Data is transmitted over HTTPS and stored in a PostgreSQL database with access restricted to the App servers. Button destinations are validated against a protocol allow-list on the server, and rendered links use rel="noopener noreferrer".

7. Changes

We may update this policy. Material changes will be reflected in the “Last updated” date above.

8. Contact

Questions or deletion requests: junitzhen@gmail.com