Privacy Policy
Effective September 5, 2026. Written in plain English and accurate to the code.
Who this covers. This policy is written by Linqry, built and operated by Ayush Parida (“we”), the operator of the cloud service at https://linqry.com. It covers two groups of people: visitors of websites that install the Linqry tracker, and account holders who use the dashboard.
1. Visitors of sites that use the tracker
The tracker is a ~1.5 KB gzipped script that the site owner adds to their pages. When you load such a page it sends a small beacon to our server. This is what that beacon leads to.
| Stored | Never stored |
|---|---|
| Page URL and path, the external referrer (if any) and UTM parameters | Cookies, localStorage identifiers or any other client-side identifier. The tracker writes nothing to your browser. |
| A visitor hash: HMAC-SHA256 keyed by a random salt that changes every UTC day, over your IP address, user agent and the site id. The first 128 bits are kept. | Your IP address. It is used in memory to compute the hash and look up an approximate location, then discarded. It is not written to the database and not written to logs. |
| Country, region and city, resolved from the IP with a local database. No lookup service is contacted. | The full user-agent string. Only device class, browser family and operating system are kept. |
| Device class, browser and operating system | Anything typed into forms, mouse movements, screen recordings or keystrokes. The tracker has no such code. |
| Time spent on a page, clicks on outbound links, and any custom event names, properties or revenue amounts the site owner chooses to send | Cross-site profiles. The hash includes the site id, so the same browser produces a different id on every site. |
The daily salt is deleted after two days. Once it is gone, past visitor hashes cannot be recomputed by anyone, including us, even with full database access. Because the hash changes every day there is no way to recognise you across days.
Site owners can send custom event properties. We instruct them not to include personal data, and truncate values, but we cannot see what they choose to send. If you believe a site is sending personal data through Linqry, contact that site’s owner; they are the controller of that data.
Requests whose user agent identifies a crawler, headless browser or HTTP client are dropped. You can exclude your own browser from a site’s analytics by running localStorage.setItem('linqry_ignore', 'true') in that site’s console.
2. Account holders of the cloud service
If you create an account at https://linqry.com, we store:
- Your email address, the display name you enter, and an Argon2 hash of your password. We never store the password itself.
- If you sign in with Google or GitHub: the email address and name the provider returns. We do not receive or store your provider password.
- Session identifiers, stored in an HTTP-only cookie so you stay signed in. This cookie is set only on the dashboard, never on sites that use the tracker.
- The sites you add (name, domain, additional hosts, timezone), their write keys, team members and roles, goals, funnels, campaigns, short links, share tokens and SEO audit results.
- Billing status per site: trial dates, subscription status, and the Razorpay subscription and payment identifiers. Card numbers are entered on Razorpay’s checkout and never reach our servers.
- Server logs for failed requests and, if error monitoring is configured, error reports containing the request path and stack trace.
The events collected on your sites belong to you. We use them only to render your dashboards and to operate the service (for example to enforce rate limits). We do not sell data, share it with advertisers, or use it to build profiles.
3. Third parties that may process data
| Who | What for | When |
|---|---|---|
| Razorpay | Payment processing for cloud subscriptions. Card details are entered on Razorpay's checkout and never reach our servers; we store the Razorpay subscription and payment identifiers. | Only when you subscribe to the cloud plan. |
| Google and GitHub | Sign-in. We receive your email address, display name and provider account id. | Only when you choose to sign in with Google or GitHub. |
| Sentry | Error monitoring for the application (stack traces and request metadata for failed requests). The tracker's beacons are not sent to Sentry. | Only if the deployment has a Sentry DSN configured. |
| Google Fonts | The dashboard and this website load their typefaces from fonts.googleapis.com, so your browser requests the font files from Google. | On every page of the dashboard and marketing site. The tracker snippet on your site does not load fonts. |
| Our hosting provider | Runs the application and the Postgres database that stores your account and your sites' events. | Always, for the cloud service. |
4. Retention and deletion
Event data is kept for as long as the site exists in your account. Deleting a site deletes its events, goals, funnels, campaigns, audits and billing record. Deleting your account (from the Account page, see section 5) deletes everything belonging to it, including every site you own. Daily salts are deleted after two days. Server logs and error reports are kept for the period configured in the respective tool and then discarded.
5. Your rights
You can delete any site you own from its settings page, which removes its events and configuration. You can delete your whole account yourself from the Account page in the dashboard, which removes the account and every site it owns. Depending on where you live you may also have the right to access, correct, export or erase personal data, to object to processing, and to complain to a supervisory authority. To exercise a right that the dashboard does not cover, contact us (section 7). Visitors of a tracked site should contact that site’s owner; we act on their behalf for that data.
6. Security
Passwords are hashed with Argon2. Dashboard sessions use HTTP-only, same-site cookies. Write keys authenticate server-side event submission. Every response carries strict transport security, content-type and referrer-policy headers. The source code is public, so you can verify all of this rather than take our word for it.
7. Contact
Email info@futuregensystems.com.
8. Changes
When this policy changes we update the effective date at the top and record the change in the changelog. Material changes affecting account holders are announced by email.
This page describes how the software and the cloud service work. It is not legal advice for your own use of analytics; consult your own counsel for that. See also the Terms of Service and the technical privacy model.