Privacy policy
Last updated:
This policy covers the personal data Ledion handles: what it is, why Ledion needs it, how long it’s kept, who else gets it, and what you can ask for.
Who runs Ledion
Ledion is an app for HubSpot. Its workflow step, Send conversion, sends conversions from HubSpot to the ad networks a customer connects. Ledion is run by Ledion LLC, a Florida limited liability company, at 10461 SW 204th Ter, Miami, FL 33189, USA, independently of HubSpot, Inc. In this policy, “Ledion” means that company and the app.
For questions and requests, email Santi at santi@ledion.io, or write to the address above.
Ledion handles personal data in two roles:
- As a controller for its customers’ account data, for beta signups and for visits to ledion.io.
- As a processor for the data of its customers’ contacts. Ledion acts only on the customer’s instructions, under the data processing agreement. If you’re one of those contacts, the business that uses Ledion decides what’s sent, and its own privacy policy applies too.
What Ledion processes
Customer accounts
When a company installs Ledion in HubSpot, Ledion stores:
- the HubSpot account ID, and the user ID and email address of the person who installed Ledion
- the email addresses added as alert recipients in Ledion’s settings
- the setup the customer creates: conversions, network connections (their access tokens encrypted) and settings
- a log of each send, described in the next section
Billing goes through Stripe. You enter payment details on Stripe’s pages, and Ledion doesn’t store them. Ledion keeps the Stripe customer and subscription IDs and the subscription’s status.
Your contacts and customers, on your instructions
When a HubSpot workflow runs the Send conversion step, Ledion reads the record’s identifiers from HubSpot: email address, phone number, name, address fields and ad click IDs. It normalizes them, hashes them where the network requires it, sends them to the ad networks selected for that conversion, and then drops them. Ledion doesn’t store them. They never go into its database, its queues, its logs or its error messages.
For each send, Ledion keeps the HubSpot record ID, the conversion’s time, value and currency, each network’s result, and a yes or no for each kind of identifier that was present (for example, email yes, phone no).
The optional capture script runs on the customer’s website. It keeps ad click IDs in a first-party cookie and in the browser’s local storage, and puts them into the site’s HubSpot forms. It makes no network requests, so nothing it reads reaches Ledion’s servers.
Visitors to ledion.io
- Analytics. ledion.io uses Cloudflare Web Analytics. It sets no cookies, uses no local storage, and doesn’t fingerprint visitors by IP address or browser.
- The beta form. What you enter (email, company website, HubSpot plan, ad networks, monthly ad spend, notes, and whether the founding partner offer interests you), the page you signed up on, and any UTM tags in the link you followed. Cloudflare Turnstile checks that a person, not a bot, sent the form. Ledion passes your IP address to Turnstile for that check and doesn’t store it.
- One cookie, only while you connect a network. When a customer signs in to an ad network to connect it, Ledion sets one cookie on api.ledion.io that ties the sign-in to the browser that started it. It’s strictly necessary, holds a random value, and is deleted when the sign-in finishes, or after 10 minutes.
Why Ledion processes it
| Purpose | Data | Legal basis |
|---|---|---|
| Running the service: sends, results, alerts | Customer account data | Performance of the contract with the customer |
| Sending conversions for a customer | Contacts’ identifiers, as processor | The customer’s instructions, under the DPA |
| Billing | Customer account data, Stripe IDs | Performance of the contract |
| Support | Customer account data, and what you write to Ledion | Performance of the contract; legitimate interest in answering questions |
| Security: checking requests, blocking spam and abuse | IP address and Turnstile result when the beta form is sent (not stored) | Legitimate interest in keeping Ledion and its customers safe |
| Site analytics | Page view counts | Legitimate interest in knowing which pages people read |
| The beta: replying to signups and inviting people | Beta form data | Your request, and your consent, which you can withdraw at any time |
You don’t have to give Ledion any personal data. Without the installing user’s email address Ledion can’t run an account or send its alerts, and without an email address the beta form can’t be sent.
Ledion makes no decisions about people based only on automated processing, including profiling, that have legal or similarly significant effects on them.
How long Ledion keeps it
| Data | Kept for |
|---|---|
| Send log (record IDs, values, results; no identifiers) | 90 days |
| The list of records already sent to each network, which stops duplicates (IDs only) | 400 days |
| Tracking-health daily totals (counts only) | 400 days |
| Account data: users, alert emails, setup | Until 30 days after uninstall |
| HubSpot access tokens | Deleted as soon as Ledion detects the uninstall |
| Network credentials | Deleted as soon as the network is disconnected |
| Beta signups | Until you ask for removal, or 24 months |
| Ledion’s operational logs (IDs and codes only) | 7 days |
| Emails you send Ledion | As long as needed to answer you, and as long as tax and business-record laws require |
Uninstalling Ledion stops all processing at once. 30 days after uninstall, everything Ledion stores for that HubSpot account is deleted, including the send log and the duplicate list. Deleted data can stay in the database’s point-in-time backups for up to 30 days more.
One exception: if a paid plan is still billing when Ledion is uninstalled, Ledion keeps that account’s data until the subscription is canceled, so the subscription isn’t lost or charged twice. Santi gets an alert from the day after the uninstall to cancel it with you. Once it’s canceled, the data is deleted within a day, or 30 days after the uninstall if that’s later. To avoid this, cancel your plan before you uninstall.
Who else gets it
Ledion shares personal data only with:
- Its subprocessors, listed on the Subprocessors page: Cloudflare (hosting, database, queues, email, web analytics) and Stripe (payments).
- The ad networks a customer connects (Google Ads, Meta, Microsoft Ads, Reddit). They receive that customer’s conversions on the customer’s instruction, and use them under their own terms with the customer.
- Authorities, when the law requires it.
Ledion doesn’t sell personal data, and doesn’t use it, or anything else it reads from HubSpot, to train AI or machine learning models. Ledion doesn’t share personal data for cross-context behavioral advertising either.
International transfers
Ledion LLC is in the USA, Ledion runs on Cloudflare’s global network, and Stripe is in the USA, so personal data can be processed outside the country where it was collected. Where data leaves the EEA or the UK for a country without an adequacy decision, Ledion relies on the European Commission’s Standard Contractual Clauses (SCCs), with the UK addendum for UK data. The data processing agreement sets them out, and Ledion sends a copy on request.
Your rights
You can ask Ledion for a copy of your personal data, and ask it to correct or delete that data. You can also ask it to restrict how it uses your data, object to a use based on legitimate interest, get your data in a portable format, and withdraw consent you gave, without affecting what was done before. US state privacy laws give similar rights, and you can use them the same way. Ledion won’t treat you differently for using them. Email santi@ledion.io. Ledion answers within 30 days, and may ask you to confirm who you are first.
- Customers can also ask for everything Ledion stores for their HubSpot account to be deleted, with Request data deletion in Ledion’s settings. Santi confirms by email first, then deletes it within 30 days.
- Contacts of Ledion’s customers: Ledion doesn’t store your identifiers, so it usually has nothing to look up. Ask the business that holds your data in HubSpot. Ledion helps it answer.
If you’re in the EEA or the UK, you can also complain to your data protection authority.
Security
Ledion doesn’t store contacts’ email addresses, phone numbers, names, addresses or click IDs at all. Access tokens are encrypted, every request from HubSpot must carry a valid signature, and Ledion asks HubSpot and the ad networks for the fewest permissions it needs. The details are on the Security page.
Google user data
When a customer connects Google Ads, Ledion receives this data from Google’s APIs:
- Google Ads account details: account IDs, names, currency and time zone
- conversion action names, IDs and settings
- the upload results Google returns for each conversion
Ledion uses it only to list the customer’s accounts and conversion actions, so the customer can choose where conversions go, and to upload the customer’s conversions and show whether Google accepted them. The account and conversion action details are kept while the connection exists, and deleted with the rest of the account’s data. Upload results are part of the send log, kept for 90 days. People at Ledion don’t read this data, except to investigate a bug or abuse, to comply with the law, or when the customer asks for help with their account. Ledion never uses it for advertising, never sells it, and never uses it to train AI or machine learning models. If Ledion ever wants to use Google user data in a new way, it asks for your consent first.
Ledion's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Children
Ledion is a business tool. It isn’t directed at children.
Changes to this policy
When this policy changes, the new version goes on this page with a new date at the top. If a change affects how Ledion uses data it already holds, Ledion emails customers before it applies. This version takes effect on October 21, 2026.