Privacy Policy
Last updated: 16 November 2026
This policy explains what personal data VELJASMELE LTD ("we") processes when you use Glintscout, in Glintscout's business directory and when you ask us to remove your data, why, and what your rights are. We are a company registered in England and Wales (company number 15570351) with our registered office at 128 City Road, London, EC1V 2NX, United Kingdom, and we operate Glintscout. We are the controller of your account data, of Glintscout's business directory and of removal requests. For the contacts in your projects we act on your behalf, as your processor under the Data Processing Agreement (section 2). Questions and requests: support@glintscout.com.
1. Data about our customers
- Account: name, email address, password (stored only as a hash), and your Google account id if you sign in with Google.
- Usage: your projects, searches, the steps you run, your credit balance and its history, API keys you create (stored as hashes).
- Payments: amounts, status and dates of purchases; card payments are handled by Stripe, which gives us no full card numbers; for crypto payments, the coin, amount and deposit address.
- Technical: the IP address and browser used to sign up and sign in, and server logs, to protect the service and prevent abuse (for example duplicate accounts collecting welcome credits; see Fraud prevention below).
- Marketing source: how you found us (campaign tags in the link, the referring site, ad click ids), stored once when you create your account.
We use this data to provide the service and take payments (contract), to keep the service secure and prevent fraud (legitimate interests), to understand which of our marketing works (legitimate interests), and to meet legal and accounting obligations. We send you service emails (verification, password reset, receipts, important changes) and, depending on where you live and what you choose, a few others; section 7 says which, and how to stop them.
To comply with sanctions rules we check the name and email domain you sign up with, the country your connection comes from (as reported by our network provider, Cloudflare) and your billing country and city against the countries and regions we cannot serve and against the public sanctions lists of the EU, the UK and the US. We keep a record of these checks for 5 years.
Fraud prevention. To stop abuse of welcome credits and plan trials, such as one person collecting them with several accounts or cards, we use:
- Network: the IP address and approximate country (as reported by our network provider, Cloudflare) of your sign-up and of each checkout.
- Device identifier: a random identifier that the web app creates and keeps in your browser's local storage and sends with its requests to Glintscout, which reads it at sign-up, Google sign-in and checkout. It is not a cookie, it says nothing about your device, it is never used to follow you across other sites, and it is reset when you clear this site's data in your browser.
- Bot check: the Cloudflare Turnstile check on the sign-up form, when the form shows it, which tells us whether a sign-up comes from a person or from an automated program.
- Card: from Stripe, the card's brand, last four digits and country, and the card's fingerprint (a token Stripe derives from the card that identifies the same card again without revealing its number), so that each card gets one trial.
- Stripe's own checks: Stripe screens card payments for fraud (Stripe Radar) and asks your bank to confirm a payment with 3D Secure where the card supports it.
The legal basis is our legitimate interest in preventing fraud and the abuse of our offers (Article 6(1)(f) GDPR). We keep this data while your account exists and for up to 24 months after it is closed, so that the same offers cannot be collected again with a new account, and then delete it. It is never sold or used for advertising.
2. Business data in your projects
When you run a search, Glintscout collects business information from public sources (business names, addresses, categories, phone numbers, websites and the Google Maps place id) and business email addresses, and checks whether those addresses accept mail. This data is stored in your projects so you can export it. You decide what to search for and how you use the results, and for that use you act as the controller of the data; see the Terms and the Acceptable Use Policy.
Every business email address that email discovery finds is checked automatically right after, by BounceVerify (section 4), with a connection to the address's mail server that sends no email. When the address was checked in the last 90 days for Glintscout's business directory (section 3), the result of that check is used instead: the address is then not sent to BounceVerify, and nothing of your project is sent anywhere for it. For this data we process on your behalf, the Data Processing Agreement applies.
Glintscout also keeps its own directory of businesses, described in section 3. Deleting a project deletes your copy of its results; it does not delete the facts about businesses in the directory. If your business email address or phone number appears in Glintscout and you do not want it used, you can have it removed at glintscout.com/remove.
3. Glintscout's business directory
Glintscout keeps a directory of businesses so that it can find, describe and check businesses for searches and keep that information accurate. For this directory VELJASMELE LTD is the controller.
What it holds. Facts about businesses: name, address, postal code, city, country, category, business phone number, website, Google Maps place id and Overture place id; general business email addresses published on the business's own website or in open business listings, such as info@ or office@ on the business's own domain; for each fact, its source and when it was first and last seen; and the results of our own checks of whether those addresses accept mail. This includes businesses run by a single person (sole traders), for which the directory holds the same business information they publish.
What it does not hold. Any other email address, such as the addresses of named people (firstname@); ratings and reviews; email addresses found through Hunter and Icypeas; listings from Yellow Pages; and anything about our customers: who ran a search, what a customer searched for, their projects or what they upload. To measure our coverage we count searches per day by source, country, city and category, without recording who ran them.
Sources. Google Maps listings, read for us by Apify; the businesses' own websites, read by Apify or by our own crawler, GlintscoutBot, which obeys robots.txt; open data from the Overture Maps Foundation (business listings published under open licences, see Data sources), of which we keep only businesses and their general business email addresses on their own domain; and our checks of email addresses. We check the directory's business addresses ourselves, from our own mail check server (verify.glintscout.com, see glintscout.com/verify): it asks the address's mail server whether the mailbox exists, without sending any message, and we keep only the result and the day of the check. Checks also come from BounceVerify, run on Apify's platform (earlier checks also used an older mail server check of ours and MillionVerifier). Searches and email checks that Glintscout runs itself add these facts. Searches and email checks run by our customers will add the same kind of facts only after we have given them 30 days' notice.
Purposes and legal basis. We use the directory to find and describe businesses for searches, to avoid searching the same sources again, to keep the information accurate (for example by checking email addresses again and marking businesses that have closed), and to measure our coverage. We do not sell or rent the directory as a list. The legal basis is our legitimate interest in running a business search service with accurate data (Article 6(1)(f) GDPR). We have weighed this interest against the rights of the people concerned: the directory holds only information that businesses publish so that they can be contacted about their business, and our own checks of it; for a business run by a single person it holds only that business information and never personal email addresses; every fact carries its source and date; and anyone can have their data removed at any time.
How long we keep it. Facts about businesses have no fixed end date; we keep them current instead. We record when each fact was last seen, mark facts that have not been seen for a while as out of date and check them again before we use them, and mark businesses that have closed so that they are no longer used. A removal request deletes data as soon as it is confirmed, as described below.
Your right to object and to have data removed. You can object at any time to the use of your business email address, of every address on your domain or of your phone number, and ask us to delete it, at glintscout.com/remove or by writing to support@glintscout.com. We confirm a request with a link sent by email (for a domain, to an address on that domain) and check requests for a whole domain or for a phone number by hand. We then delete the address or number from the directory, from every customer project and from our working files (search results and logs), ask customers who downloaded it or sent it to an outreach tool to delete it too, and keep only a coded fingerprint of it on a suppression list (a keyed hash that cannot be turned back into the address or number), so that it is never collected again. To handle a request we keep the address or number, the email address we answer to, your language and a coded form of the network the request came from, to prevent abuse; section 5 says for how long.
Complaints. You can also complain to the data protection authority where you live or work, or to the UK Information Commissioner's Office (ico.org.uk), which supervises us.
4. Who we share data with
Only with service providers that help us run Glintscout, under contracts that protect the data:
- hosting, network and security providers (servers, content delivery, DDoS protection);
- payment providers (Stripe for cards, our crypto payment gateway);
- Google, if you choose to sign in with Google;
- email delivery providers for the emails we send you;
- internal alerting tools we use to watch sign-ups and payments (for example Telegram), which receive account and payment numbers and the kind of event, never names, email addresses or phone numbers;
- data and verification providers that power searches, email discovery and email verification: Apify (Google Maps and Yellow Pages searches, and the platform the email check runs on), Hunter and Icypeas (email discovery, only while we have them switched on; both are off at present) and BounceVerify (email checks for lead projects, through its actor on Apify; recent results may be reused as described in section 2). MillionVerifier, used for an optional second check that is no longer offered, receives no new data;
- Instantly, only when you send contacts to your own Instantly account;
- Replyze, the live chat on our site, a service that VELJASMELE LTD also runs on its servers in Germany: it receives what you write in the chat, the page you write it from and your browser's language and type. To write an answer, your recent messages are sent to Anthropic (United States), whose Claude models write it, under Anthropic's commercial terms.
We do not sell customer account data or the business directory. We are in the United Kingdom, for which the European Commission has adopted an adequacy decision, and our servers are in the European Union (Germany and Finland). Some providers process data in other countries, such as the United States. For our hosting, network, payment, sign-in, data and verification providers, a transfer that needs a safeguard is covered by an adequacy decision, by the recipient's certification under the EU-U.S. Data Privacy Framework and its UK Extension, or by the standard contractual clauses (with the UK International Data Transfer Addendum for data from the United Kingdom) in their data processing terms. Apify is an EU company; its data processing addendum allows transfers to the United States or any other country in which Apify or its sub-processors operate, under the standard contractual clauses. The sub-processors for data we process on your behalf are listed in the Data Processing Agreement.
5. How long we keep data
Account and project data: while your account is active and for a short period after it is closed. Deleting a project deletes your copy of its results: its companies, its contacts, the files and logs its steps produced and the record of what it searched. The business directory keeps facts about businesses as described in section 3. Removal requests: the address or number is kept while the request is open and cleared from it once the request is done, rejected or has expired, and the rest of the request is deleted 90 days after it is closed; the coded fingerprint stays on the suppression list. Payment records: as long as accounting law requires. Security logs: for a limited time, then deleted.
- Email verification results of your projects: stored with the contact in your project and deleted with it; the check's run at our provider is deleted after the run.
- Sanctions checks: 5 years.
- Fraud prevention data (section 1): while your account exists and up to 24 months after it is closed.
- Live chat conversations: 24 months after their last activity.
- Server backups: copies are deleted when the backups expire.
6. Your rights
Depending on where you live, you can ask for access to your data, correction, deletion, restriction, portability, and object to processing based on legitimate interests. You can also complain to your data protection authority or to the UK Information Commissioner's Office, which supervises us. Write to support@glintscout.com. For the business directory, see section 3; removal requests can be made at glintscout.com/remove. For the emails we send you, see section 7.
7. Emails we send
- Service emails: about your account and its security, receipts, plan and trial reminders, and notices about your account. They are part of providing the service you signed up for (our contract with you), so they cannot be turned off while your account exists.
- Search notifications and the low balance email: they tell you when a search you started has finished and when your credits run low. You can turn each of them off in Settings.
- Tips, onboarding and offers about Glintscout plans: in the United Kingdom and outside the European Union, we send them on the basis of our legitimate interests to people who signed up for Glintscout and did not opt out when they signed up (the "soft opt-in" for similar services). In the European Union, the European Economic Area and Switzerland we send them only with your consent, given when you sign up or in Settings; in Germany you confirm it with the link in the email that confirms your address. Accounts created before 16 November 2026 do not get them unless they turn them on in Settings.
- Product news: only to people who turn it on in Settings.
Every optional email has an unsubscribe link, and your email program can also unsubscribe you in one click. Unsubscribing takes effect at once, and we keep a record of it so that an address that has unsubscribed is not added back. We do not use tracking pixels to see whether you open our emails.
Your right to object. You can object at any time to receiving marketing emails from us. Use the unsubscribe link in any such email, the switches in Settings, or write to support@glintscout.com.
8. Cookies and local storage
Glintscout does not use advertising cookies. The web app keeps your sign-in session and the first page you arrived from in your browser's local storage; this is needed for signing in and for counting where our customers come from, and it never leaves your browser except when you create an account. It also keeps a random device identifier there (gs_dev), which it sends only to Glintscout, with its requests, for fraud prevention (section 1). The live chat keeps its conversation in your browser's storage so that it continues from page to page; it does not track your visit.
9. Security
Passwords and API keys are stored as hashes, connections are encrypted, and access to production systems is restricted.
10. Changes
We may update this policy; the date at the top shows the current version, and material changes are announced by email or in the app.