Last updated September 13, 2026
This page explains, in plain language, how Ralix finds prospects and handles the data involved. It restates the rules our own build is required to follow — see Terms and Privacy for the legal terms themselves.
Prospect data comes from one of two paths, and they are kept structurally separate — never combined into one candidate set:
Public data: the open web, business-directory and places APIs, and public social posts. This is the default path every signal search uses.
Consented, logged-in data: any source that requires an authenticated login is a separate store and code path, gated behind an explicit per-tenant consent record. It is never folded into the public-data path without that consent on file.
Personal data — an individual's email address, phone number, or personal profile — is minimized to what a card actually needs, encrypted at rest, access-logged, and deletable on request in line with GDPR/CCPA. Business-level facts (a company name, its public rating, a public review or post) are not personal data and are handled as ordinary business information.
Ralix does not automate sending on LinkedIn. Where LinkedIn is the right channel for a prospect, Ralix tells you that and drafts the message — you send it yourself, from your own account.
Every data source Ralix reads from has an explicit, enforced policy covering what it may be used for and how it's rate-limited and attributed. A source without one isn't used. Robots.txt and provider terms of service are respected, and a provider API is preferred over scraping wherever one exists.
You can request deletion of prospect and contact data collected on your behalf at any time by emailing privacy@ralix.ai. Retention follows the schedule in our Privacy Policy.
Discover businesses that match your offering, understand why they may need what you sell, and turn research into actionable opportunities.