Privacy Policy

Last updated: October 20, 2026

This policy explains what Yellow Lion Apps does with personal information. It covers the Radius Search application for HubSpot, our website at yellowlionapps.com, our partner portal, and the support and billing tools we provide with them (together, the "Service"). The Service is operated by Yellow Lion Solutions LLC ("Yellow Lion", "we", "us"), of Bushkill, Pennsylvania, United States.

The short version

• We do not store your contacts or companies. The app reads records from your HubSpot account, works out their coordinates, writes the coordinates back into HubSpot, and keeps none of the record data on our servers. No names, email addresses, phone numbers, or address text from your CRM are written to our database.
• We keep a shared cache of coordinates, keyed by a one-way fingerprint of the address. The address text itself is not stored. Section 6 explains this in full, because it is the one place where data from one customer benefits another.
• We send addresses to one third party — Geocodio, our geocoding provider — and nothing else about your records.
• We do not sell or share personal information as those terms are used in California law, and we run no advertising or cross-site tracking.
• To ask about your information, email us with "Privacy request" in the subject line. Contact details are at the end.

1. Two different kinds of data, and two different roles

It matters which of these we are talking about, because our responsibilities differ.

Your CRM data. The contact and company records in your HubSpot account. You decide what is in them and why. Under the GDPR and similar laws you are the controller of that data and we are your processor: we handle it only on your instructions, only to provide the Service, and we do not use it for our own purposes. Your own privacy notice, not this one, is what tells the people in your CRM how their data is used.

Our own account data. Information about you as our customer, partner, or support contact — your name, your email address, your billing records, your support messages. For that data we are the controller, and this policy is the notice for it.

2. What we do not collect

We think this is worth stating plainly, because it is unusual and because it is the question most people have about an app with read and write access to a CRM.

Our database contains no contact or company records. There is no table of your records, no copy of your CRM, and no export of it. When the app geocodes your records it reads a page of them from HubSpot's API, extracts the address fields, obtains coordinates, writes the coordinates back to HubSpot, and moves on. The record data is held in memory for the length of that operation and is not written to disk.

We also do not collect: payment card numbers or bank details (Stripe handles those and we never see them), government identification numbers, biometric data, precise device location, or any special category data as defined by the GDPR.

3. What we do collect and store

This is the complete list.

About your installation

• Your HubSpot account ID (portal ID), your HubSpot account domain, and the data hosting region HubSpot reports for it
• The OAuth access and refresh tokens that let the app work with your account, encrypted at rest
• The permissions you granted at install, the install and update timestamps, and the referral code, if any, that the install came through

About geocoding work

• Job records: which object types were processed, in which mode, the progress position, counts of records succeeded, skipped, and failed, and timestamps
• A truncated error message when a job fails, kept for diagnosis
• No record identifiers, and no record contents, are kept in these job records

About lists you create

• The HubSpot list ID, the object type, and the name you gave the list, so the app knows which lists are its own and will not overwrite a list you curated by hand. If you type an address into a list name, that name is stored as you typed it.

About your subscription

• Your Stripe customer, subscription, payment, and charge identifiers, the plan you are on, amounts, currency, tax amounts, and invoice status
• The event records Stripe sends us about your subscription, which we keep so that a payment is never processed twice

About support requests

• Your name, email address, company, the HubSpot account ID you typed in if you provided one, your subject line and message, and our replies

About referral partners (only if you apply to or join the partner programme)

• Your name, email address, company and website, and the contents of your application
• Sign-in records: single-use login tokens, session records, and the IP addresses from which a login was requested, issued, and used
• Your referral codes, the clicks attributed to them with a hashed IP address rather than the address itself, the installs and subscriptions attributed to you, commissions earned, payouts made, and the status of your tax form
• An append-only audit log of administrative actions on your partner record, which by design cannot be edited or deleted

4. What the app writes into your HubSpot account

The app creates a property group called Radius Search on contacts and companies, and writes to the properties in it: the latitude and longitude derived from the record's address, a status indicating whether geocoding succeeded or why it did not, an indication of how precisely the address matched, and a fingerprint of the address last geocoded, which lets the app skip records whose address has not changed.

It also creates and updates HubSpot lists when you ask it to, and only lists it created itself.

Everything it writes stays in your HubSpot account and belongs to you. If you uninstall the app, those properties and lists remain, and it is up to you whether to keep or delete them.

5. How we use the information

We use it to run the Service and nothing else: to authenticate your installation and keep it working; to geocode records and return radius results; to create the lists you ask for; to bill you and keep billing records; to answer your support requests; to run the partner programme and pay commissions; to keep the Service secure, diagnose faults, and prevent abuse; and to meet our legal, tax, and accounting obligations.

We do not use your CRM data to train models, build datasets, or develop products. We do not profile you or the people in your records. We do not use your data for advertising, and we do not permit anyone else to.

If you are in the UK or EU, the legal bases we rely on for our own account data are: performance of our contract with you, for providing and billing the Service; our legitimate interests, for security, fault diagnosis, and preventing abuse; your consent, where we ask for it; and compliance with legal obligations, for tax and accounting records. For your CRM data we act on your instructions as your processor, and the legal basis is yours to establish.

6. The shared address and coordinate cache

This is the part of the Service that deserves the most explanation, so here it is in detail.

Geocoding the same address twice is slow and costs money, so we cache the result. The cache works like this: the address text is normalised and run through a one-way cryptographic hash (SHA-256, truncated), and that fingerprint becomes the key. Stored against it are the latitude and longitude, how precise the match was, and whether a match was found at all.

The cache is shared across all customers of the Service. If another customer has already geocoded the same address, your records are resolved from the cache, and the address is never sent to our geocoding provider at all. The reverse is also true: addresses your account causes us to geocode may later resolve another customer's records.

What a cache entry does not contain: the address text, any name, email address, or phone number, any record identifier, any HubSpot account identifier, and anything else that ties it to you, to your account, or to the person it describes. Entries cannot be traced back to the customer whose records produced them.

We should be precise about one thing rather than overstate it: because the fingerprint is a hash of the address, someone who already knows a specific address could compute the same fingerprint and look up its coordinates. The entry reveals nothing about who is at that address, which customer's records it came from, or that anyone's record mentions it at all — but it is a pseudonym for the address rather than anonymous data, and we treat it accordingly.

We retain cache entries after a subscription ends, because an entry is not attached to any subscription. Deleting your account does not and cannot remove them, since there is nothing in them identifying which account they relate to.

7. Who else handles the data

We keep this list short deliberately. These are the only third parties involved in running the Service, and each one receives only what it needs.

• HubSpot, Inc. (United States) — the platform itself. Your CRM data lives in your HubSpot account, under your agreement with HubSpot, in the hosting region you chose with them.
• Geocodio (Dotsquare LLC, United States) — geocoding. It receives the address text only, over an encrypted connection, and returns coordinates. It receives no name, email address, phone number, record identifier, or account identifier, and has no way to tell which customer or which person an address relates to. Addresses are sent only on a cache miss.
• Stripe, Inc. (United States) — subscriptions and payments, and partner payouts. Stripe collects your payment details directly and we never receive or store them. For partners, Stripe collects the identity and tax information it needs to make a payout.
• Brevo (Sendinblue SAS, European Union) — transactional email, such as support acknowledgements, partner invitations, and billing notices. It receives the recipient's name and email address and the contents of the message.
• IONOS — hosting for our servers and database, in the United States.

We do not sell personal information, and we do not share it for cross-context behavioural advertising, as those terms are defined in California law. We may disclose information if the law requires it, to enforce our terms, to protect someone's safety, or to a buyer or successor if the business is sold — in which case this policy continues to apply to information transferred, or you will be told before it does not.

8. International transfers

We are based in the United States and our servers are in the United States. If you are outside the United States, using the Service means your account data, and any addresses sent for geocoding, are transferred to and processed in the United States. Where we transfer personal data out of the UK or EEA, we rely on the European Commission's Standard Contractual Clauses, or another lawful transfer mechanism, with the providers listed above.

If you are subject to the GDPR and need a data processing agreement incorporating those clauses, email us and we will provide one.

9. How long we keep things

What	How long
Installation records and OAuth tokens	While the app is installed, and until you ask us to delete them or we remove them after you cancel
Geocoding job records and error messages	For diagnosis, then deleted on request
List ownership records	While the app is installed
Billing records, invoices, and Stripe event records	Seven years, for tax and accounting
Support requests	Two years after the request is resolved
Partner records, commissions, and payouts	Seven years, for tax and accounting
Partner sign-in records and IP addresses	Twelve months
Administrative audit log	Retained; it is append-only by design
Address and coordinate cache entries	Retained indefinitely; they identify no person or account (section 6)

If you ask us to delete your data, we will do so within 30 days, other than records we must keep for the reasons above and the cache entries described in section 6.

10. How we protect it

All traffic to the Service travels over encrypted connections. The OAuth tokens that grant access to your HubSpot account, and partner multi-factor secrets, are encrypted at rest in our database rather than stored in readable form. Administrative pages are not reachable from the public internet without authentication. Payment details never reach our systems. Access to production systems is limited to those who need it.

No service can promise perfect security, and we do not. If a breach affects your personal data, we will notify you and any regulator as the law requires, without undue delay.

11. Your choices and your rights

Depending on where you live, you may have the right to know what personal information we hold about you, to get a copy of it, to have it corrected, to have it deleted, to limit how we use it, to object to our using it, to withdraw a consent you gave us, and not to be treated differently for exercising any of these rights.

Residents of California, Colorado, Connecticut, Utah, Virginia, and other states with similar laws have these rights under their own state law, including the right to appeal if we refuse a request. Residents of the UK and EEA have them under the GDPR, and may also complain to their data protection authority.

How to make a request. Email us with "Privacy request" in the subject line, from the address associated with your account, and tell us what you would like. Because we operate entirely online and deal with you directly, email is our designated method for these requests. We will acknowledge within 10 days and respond within 45 days, and will tell you if we need longer. We may need to verify who you are before acting, and will ask only for what is necessary to do so. An authorised agent may make a request for you with written permission.

If your personal data is in one of our customers' HubSpot accounts and you want it accessed, corrected, or deleted, we are the processor and not the controller, so we cannot act on that ourselves. Please contact the company whose CRM holds your details. If you contact us instead, we will tell you so, and will help that company respond.

You can also stop all processing at any time by uninstalling the app from your HubSpot account, which immediately revokes our access to it.

12. Our website, cookies, and forms

Our website runs on WordPress. It sets only the cookies needed for the site to work and to keep a form submission secure. We do not run advertising cookies, and we do not track you across other websites. We do not currently respond to "Do Not Track" browser signals, as there is no common standard for doing so.

When you submit the support form or the partner application form, the details you enter are sent to our servers and emailed to us. Form submissions are not stored in the website itself.

Our server logs record the usual technical details of a request, including IP address, for security and fault diagnosis.

13. Children

The Service is a business tool and is not directed at children. We do not knowingly collect personal information from anyone under 18. If you believe a child has given us personal information, email us and we will delete it.

14. Changes to this policy

If we change this policy we will update the date at the top. If a change materially affects how we handle personal data, we will tell customers by email or in the app at least 30 days before it takes effect.

15. How to contact us

Yellow Lion Solutions LLC
Bushkill, Pennsylvania, United States

Privacy and data requests: info@yellowlionsolutions.com, subject line "Privacy request"
Support: yellowlionapps.com/support
Terms of Service: yellowlionapps.com/terms-of-service