Privacy Policy

1. Overview and Scope

This Privacy Policy explains how [Company Legal Name], of [Company Address] ("LinkProfit", "we", "us"), handles personal data in connection with the LinkProfit link management platform, its dashboards, its application programming interfaces and the short links it serves.

Our role depends on whose data is involved. For the data of partners, workspace administrators and other account holders who contract with us directly, we act as a controller: we decide why and how that data is processed. For the click data of visitors who follow a short link, we act as a processor on behalf of the partner or workspace that created the link. That partner or workspace is the controller and is responsible for informing its own users and obtaining any consent required. Partners must publish their own privacy policy covering the links they operate.

Where a partner provisions a workspace for an end customer, our relationship is with the partner.

2. Information We Collect

Account data. Name, email address, password hash, organisation name, role, workspace and partner memberships, brand and custom domain settings, and support correspondence.

Billing data. Plan, subscription status, invoices, billing address and tax identifiers. Payments are processed by Stripe. We never receive or store full card numbers or bank credentials, only a payment method token and metadata such as card brand, last four digits and expiry.

Technical logs. Request timestamps, requested paths, response codes, application error reports and diagnostic traces. For the dashboard and API these may contain an IP address, needed for authentication, abuse prevention and troubleshooting.

Click data. Information derived when a short link is requested, described in Section 3: the link and workspace, the timestamp, the referrer, the browser and device family, an approximate location, and a daily visitor hash.

Content you configure. Destination URLs, link titles, tags, custom domains and any parameters or pixels you attach to your links.

3. Click Analytics and How We Handle IP Addresses

We do not store raw IP addresses of short link visitors. When a request reaches our edge redirector, the address is used only in memory, for two derivations, and is then discarded.

First, we derive an approximate location - country, region and city - from the IP address. Only that coarse location is stored; the address itself is not written to any database, analytics store, log or backup.

Second, to count unique visitors without identifying anyone, we compute a daily visitor hash: a SHA-256 hash of the visitor IP address, the user agent string, the link domain and a secret salt held by us. The salt rotates every day at 00:00 UTC, and the previous value is discarded. Because the hash is one-way and salted with a value that no longer exists after rotation, the original IP address cannot be recovered from a stored hash, and hashes for the same visitor cannot be linked across days.

We do not use click data to build cross-site advertising profiles, we do not sell it, and we do not enrich it with data purchased from third parties.

3a. Sources of Location and Network Data

The approximate location described above, and the classification of a visitor's address range (data centre, commercial VPN, public proxy, TOR exit node, web anonymiser), are derived from licensed third-party databases that we operate inside our own infrastructure. Those databases are keyed by address range, not by person: a lookup returns properties of a range of addresses, never an identity.

City, region and country names, together with their identifiers, come from the GeoNames geographical database, used under the Creative Commons Attribution 4.0 International (CC BY 4.0) licence. GeoNames is credited here as that licence requires. Range classification data is licensed from a commercial IP intelligence provider.

The database files themselves are never published, redistributed, shared with third parties or shipped inside our applications, our edge worker or any client-side bundle. They are held in private storage under our control, and only derived answers about a single address leave that boundary — the country, region and city of a visit, and the type of the address range.

A workspace may reduce this further at any time. The privacy settings of a workspace decide what is recorded when a click happens: full location, city without coordinates, or country only, with separate switches for the visitor's network, the full referring address and traffic-type detection. Those settings apply at the moment of writing, so what they disable is never stored rather than merely hidden from reports.

4. Cookies and Similar Technologies

When a short link is redirected we set cookies only where a feature the link owner enabled requires it. A link protected by a password sets a short-lived cookie after the correct password is entered, so the visitor is not asked again; it expires after fifteen (15) minutes. A link with conversion tracking enabled sets a first-party cookie on the link owner's own redirect domain, holding the signed click identifier for up to ninety (90) days, so that a later order can be attributed to the click that produced it; the identifier contains no personal data. A link whose traffic rules distinguish first-time from returning visitors sets a marker cookie on that domain, and only when a rule actually asks the question. A rotator with a sticky window sets a cookie so that the same visitor keeps reaching the same destination. Links without those features set no cookies at all.

In the dashboards we use strictly necessary cookies for session authentication and protection against cross-site request forgery. We set no advertising or cross-site tracking cookies of our own.

Partners, workspaces and their end customers may add third-party tracking or retargeting pixels to the links they operate. Where that happens, the pixel and any cookie or identifier it sets belong to the link owner and the third party, not to us. The link owner is the controller for that processing and is solely responsible for disclosing it and for obtaining any consent required by law.

5. How We Use Information

We use account and billing data to create and administer accounts, authenticate users, provide support, process payments and calculate partner payouts. We use technical logs to operate, secure and debug the service, to detect abuse such as phishing or malware distribution, and to enforce rate limits. We use click data to produce the analytics shown in the dashboards of the relevant workspace and partner. We use contact details for service messages such as security, billing and change notices, and, where permitted, product updates you can opt out of. We also use information to comply with legal obligations and to establish, exercise or defend legal claims.

6. Legal Bases

Where the General Data Protection Regulation or the UK GDPR applies, we rely on the following legal bases. Performance of a contract, for creating and running accounts, providing the platform, billing and support. Legitimate interests, for securing the service, preventing fraud and abuse, producing aggregate analytics, and improving the product, balanced against the rights of the individuals concerned. Consent, where required for optional communications or for technologies that are not strictly necessary, which you may withdraw at any time. Legal obligation, for tax, accounting, sanctions screening and responses to lawful requests.

Where we act as a processor for click data, the legal basis for that processing is determined by the partner or workspace acting as controller.

7. Sharing and Subprocessors

We do not sell personal data. We share it with service providers who process it on our behalf under contract, with professional advisers, with authorities where legally required, and with a successor entity in the event of a merger, acquisition or sale of assets.

| Subprocessor | Purpose | Processing region | | --- | --- | --- | | Vercel | Hosting of the marketing site and dashboards | United States, European Union | | Neon | Managed PostgreSQL database for account, link and domain data | European Union | | Cloudflare | Edge redirect delivery, DNS and custom domain certificates | Global edge network | | Tinybird | Click analytics storage and aggregation | European Union | | Upstash | Redis cache for link resolution, sessions and rate limiting | European Union | | Stripe | Subscription billing, payment processing and partner payouts through Stripe Connect | United States, European Union | | Resend | Transactional email such as sign-in, billing and security notices | United States | | Sentry | Application error monitoring and diagnostics | United States, European Union |

Processing regions reflect the configuration in force on the date of this policy. Partners acting as controllers may treat this table as our subprocessor list and request notice of additions.

8. International Transfers

Personal data may be transferred outside the European Economic Area or the United Kingdom, in particular to providers established in the United States. Where that happens, we rely on the European Commission's Standard Contractual Clauses, together with the UK International Data Transfer Addendum where applicable, and on supplementary measures such as encryption and data minimisation. Copies of the relevant transfer mechanism are available on request.

9. Data Retention

Account data is retained for the life of the account and a limited period afterwards, so it can be restored and legal claims handled, before deletion or anonymisation. Billing records are retained for the period required by tax and accounting law, typically several years.

Click analytics are retained for a period that depends on the plan applicable to the workspace, up to a maximum of 730 days, after which the underlying records are deleted and only aggregated counts may remain. A workspace may set a shorter retention of its own: that value is written into each event and the storage engine deletes the row when it expires, independently of what any plan would allow it to view. Technical logs and error reports are retained for a short operational window, normally not more than 90 days. Daily visitor hashes cease to be linkable once their salt is rotated, and expire with the analytics retention period of the workspace.

10. Your Rights

Subject to applicable law, you may request access to your personal data, correction of inaccurate data, deletion, restriction of processing, and portability of data you provided in a structured, machine-readable format. You may object to processing based on legitimate interests, and withdraw consent at any time without affecting processing carried out before withdrawal. You may also lodge a complaint with your supervisory authority.

If you are a California resident, you may request disclosure of the categories and specific pieces of personal information collected, request deletion or correction, and exercise these rights without discrimination. We do not sell personal information and do not share it for cross-context behavioural advertising, so no opt-out of sale is required.

If your data was collected through a partner's branded service or a workspace you belong to, that partner or workspace is the controller and your request is best directed to it. If you contact us instead, we will forward the request to the responsible controller and support it in responding.

11. Children's Privacy

The platform is intended for business use and is not directed to children. We do not knowingly collect personal data from anyone under 16 years of age. If we learn that we have collected such data, we will delete it promptly. Anyone who believes a child has provided us with personal data should contact privacy@linkprofit.com.

12. Security

We encrypt data in transit using current versions of TLS and encrypt data at rest in our database, analytics and cache providers. Passwords are stored only as salted one-way hashes, never in readable form, and link passwords are handled the same way. Access to production systems is restricted to authorised personnel on a need-to-know basis, protected by multi-factor authentication and reviewed regularly. Tenant data is separated by workspace and partner identifiers enforced at the data access layer. We keep audit logs of administrative actions, run automated dependency checks, and maintain an incident response process, including notification to affected controllers without undue delay.

No system is completely secure, and you are responsible for protecting your credentials and granting access carefully.

13. Changes to This Policy

We may update this policy to reflect changes in the platform, our providers or the law. The date at the top shows when it was last revised. For material changes we will notify account holders by email or through the dashboard before the change takes effect, and where the law requires it we will seek consent.

14. Contact and Data Protection Requests

For privacy questions, data protection requests and requests relating to our subprocessors or transfer mechanisms, contact:

• [Company Legal Name]
• [Company Address]
• Email: privacy@linkprofit.com

General legal correspondence should be sent to legal@linkprofit.com. We respond to rights requests within the period required by law, normally one month, and may ask for information to verify your identity.