Privacy notice

1. Controller and contact

Leadlund, a Finnish private trader based in Vantaa (Business ID 3627560-4), is controller for accounts, service operation, security and its own business relationships. Registered details are available from YTJ. Privacy requests: privacy@leadlund.com.

2. Customer campaign roles

The customer chooses recipients, purpose, content and lawful basis and is controller for its campaigns. Leadlund acts as processor under the DPA. Leadlund may independently control collection from public business sources for its searchable service.

3. Data and sources

• Account, organization, authentication and service-preference data.
• Encrypted email credentials and sender configuration.
• Public company and professional contact data from registries, company websites and public job listings.
• Campaign content, recipients, delivery, reply, bounce, unsubscribe and engagement events.
• IP, request, security, diagnostic and usage logs.

4. Purposes and legal bases

We provide and secure the service under the customer agreement and legitimate interests; build proportionate B2B search from public professional information under legitimate interests; enforce suppression and legal duties; and handle support and accounting. We do not sell personal data or use prospect data for consumer advertising.

Through its data API, Leadlund also discloses public company data – company name, address, business phone numbers, business email addresses, and public tax and employer information – to business clients for their own B2B sales and those of their customers, under legitimate interests. Data on natural persons, such as sole traders, is not disclosed this way.

5. Providers and transfers

Providers include Clerk, Supabase, Inngest, AWS, Vercel, customer-selected email providers, Google Cloud Translation for optional translation of registry text, Sentry for error monitoring, and residential network proxy providers used to reach some public registries. The primary database is in Frankfurt and the worker in Stockholm, but some providers process data outside the EEA. Applicable adequacy decisions, the EU–US Data Privacy Framework or Standard Contractual Clauses are used where required.

Data API clients receive this data as independent controllers. They are bound by agreement to use it only for business-to-business sales, not to sell, publish or pass it on as a list, and to honour objections and forward them to Leadlund.

6. Retention and tracking

Saved leads that have not been found again, clicked or used in a campaign for 12 months are deleted, and recipient data and engagement events from a campaign are deleted 12 months after the campaign was created once it is no longer sending. Other account and customer records remain while active or until deleted, subject to backups and legal duties. Credentials remain until disconnected; suppression and objection records are kept to preserve opt-outs. AWS worker logs are retained for 14 days.

Leadlund uses functional authentication and locale storage, not advertising cookies. Campaign emails contain click tracking unless the sender turns it off; open tracking is off by default and is added only when the sender turns it on for a campaign.

Records delivered through the data API are kept by Leadlund for 90 days after the search.

7. Your rights

You may have rights to access, correct, delete, restrict or port data and to object to legitimate-interest processing. Contact privacy@leadlund.com or complain to the Finnish Data Protection Ombudsman or your local authority. If you object to Leadlund, we record it so that no workspace saves or emails you again. For a customer campaign, contact the identified sender first; Leadlund assists the customer and honors unsubscribe requests.

An objection to Leadlund also stops your data from being delivered through the data API: it is no longer delivered, and we inform the data API clients that have already received it.

8. Security and Google user data

Credentials for connected mailboxes - OAuth access and refresh tokens, SMTP passwords - are encrypted with AES-256-GCM before they are written to the database, under a key held only in the application's secret configuration and never stored alongside the data. Traffic to the service and to every provider runs over TLS. Credentials are never sent to the browser, are reachable only by the workspace that connected them, and are deleted from the database when you disconnect the mailbox or close the account. Access to the production environment is limited to authorized administrators.

Leadlund requests only the narrowest Google permissions its features need. gmail.send is used solely to send the campaign and follow-up emails you write, from your own Gmail address. gmail.metadata is used solely to read the From, In-Reply-To, References and X-Failed-Recipients headers of incoming mail, so a reply or a bounce can be matched to the right recipient and marked in your campaign. Message bodies, subject lines and attachments are never requested, fetched or stored; from a matched message Leadlund keeps only the recipient it maps to and when it arrived.

Leadlund's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is never sold, never used for advertising, and never used to develop, improve or train generalized artificial intelligence or machine learning models. Humans do not read it, except with your explicit consent, to resolve a support issue you have reported, for security purposes, or where required by law.

9. Changes

Material changes will be communicated where appropriate. The date and version above identify the current notice.