This page explains what Ruvio does, who it is built for, why people sign in with Google, and how the limited Google account information we request is used. Full details are in the Privacy Notice.
Purpose of the application
Ruvio builds a reusable company index from business registries, licenses, and other appropriate public sources. It resolves duplicate records, classifies business activity from those filings, and preserves the evidence behind each company profile so teams can work the whole market instead of rebuilding a spreadsheet or hunting a chat thread.
With Ruvio, users can:
- describe the trade and place that define the market;
- see licensed and registered companies that Maps and people databases often miss;
- review company identity, fit, location, sources, and available contact routes as enrichment accumulates;
- keep status, prospect notes, interaction history, and open follow-ups visible to the team;
- research owners and decision-makers selectively without inventing unsupported people;
- verify available work emails and keep unresolved or likely-invalid results clearly separated; and
- move the prospects that can still move without losing the context behind the next action.
Who Ruvio is for
Ruvio is built for the person responsible for a territory: owner-managers, territory managers, and field sellers covering licensed trades and local operators — building materials, equipment, insurance, staffing, and similar teams selling into contractors, manufacturers, trucking companies, industrial services, and locally rooted businesses. The primary workflow is market coverage and a working view of the territory — not route optimization, rep management, or a people database you buy first. The point is that the owner or manager can see the whole patch, and pipeline stops leaking out of the gaps.
Why Ruvio uses Google sign-in
People create a Ruvio account and sign in with Google so we can authenticate them securely, create or restore their workspace, and protect access to saved leads, verification history, and campaign workflows. Google sign-in is used for account authentication only. It is not used to operate Gmail, read inbox content, send mail, or access Google Drive, Calendar, or Contacts for login.
Google user data Ruvio requests
When you sign in with Google, Ruvio requests only basic OpenID profile information needed to create and maintain your account:
- Name — to display your account and personalize the workspace;
- Email address — to identify your account, restore access, and communicate about the workspace; and
- Profile picture — to show your account avatar in the product interface.
Ruvio does not request Gmail content, Google Drive files, Calendar events, or other sensitive Google user data for sign-in. We do not sell Google account information.
How that Google data is used, stored, and shared
The name, email address, and profile picture returned by Google sign-in are used to authenticate you, create or restore your Ruvio workspace membership, show your identity in the product, and protect access to workspace data you save in Ruvio. That information may be processed by our infrastructure and authentication providers as needed to run the service. More detail on retention, providers, and your choices is in the Privacy Notice.
Privacy policy and terms
Please review the Privacy Notice, Terms, and Acceptable Use Policy before using Ruvio. The Privacy Notice linked here is the same privacy policy referenced on Ruvio’s Google OAuth consent screen configuration.
Start using Ruvio
You can create a free account or sign in to use Ruvio, or return to the Ruvio homepage to learn more about the product.