You bring data you are allowed to use. Second Ring separates direct contacts from connections-of-connections, records where each relationship came from, and recommends the shortest credible next step.
Second Ring turns a flat export into direct relationships, possible bridges, and a review queue tied to the goal you choose. It keeps uncertainty visible instead of pretending every LinkedIn connection is a close friend.
Start with LinkedIn, Facebook, Google Contacts, or a reviewed relationship file.
Choose a supported ZIP up to 25 MiB, or extract a larger LinkedIn archive locally and choose only Connections.csv. Raw bytes stay in this browser tab and are not sent to the Second Ring API; the product never asks for your social password.
Review duplicates and uncertain names. Report suspected mismatches with personal details redacted; editing source records is not available in this beta.
Reciprocity, recency, repeated meetings, and reviewed evidence help distinguish strong, weak, and dormant ties.
If an existing direct contact contributes their own export, their unique contacts become your consented second ring.
Contact direct relationships directly. For a second-ring person, ask the best-supported bridge for permission to introduce you.
If Dan Antonelli already appears in Dennis Yu's direct data, Dan stays in the first ring—even if George also knows him. A second-degree path is shown only when the target is not already direct and both hops have attributable evidence.
Each platform lets the account owner request a copy of their data. The exact fields vary, so the review step is part of the product—not an inconvenience to hide.
LinkedIn supplies first-degree connections and may include company, position, profile URL, connection date, and an email when that person permits it.
The ZIP from LinkedIn, or Connections.csvFacebook commonly supplies friend names without dependable profile IDs or contact details. Second Ring keeps uncertain identity matches separate until you confirm them.
The JSON export ZIP from FacebookGoogle Contacts can contribute names, emails, organizations, and titles. It does not prove that every contact is a strong relationship.
Google CSVWhen you choose Save, the durable product stores normalized graph records inside your authenticated workspace; raw social archives are not sent to or retained by the Second Ring API. Emails are identity keys, not labels on a public map. Contributors can revoke contribution-dependent graph data. Workspace owners can remove their workspace and graph records from the active application database; infrastructure backups may follow the provider's retention schedule.
No social password. No scraping. No surprise messages to your contacts.
Only the signed-in workspace owner can retrieve the private workspace through the app.
Every saved edge is tied to an import or snapshot; evidence strength can remain unresolved.
Second Ring recommends a next action; it never messages contacts for you.
A contributor can withdraw their edges without deleting the owner's independent records.
LinkedIn's Connections API is restricted and does not provide connections-of-connections. Choosing an official account-owner export in the browser is the dependable route.
No. Facebook's supported friends API does not return a complete friend list, and automated collection is not the foundation for a trustworthy product.
No. It proves first-degree membership. Strength requires additional evidence such as reciprocity, recency, repeated interaction, or owner confirmation.
One LinkedIn export normally produces a ranked map of your direct contacts. A true second ring requires a consented contributor export or reviewed relationship evidence supporting both hops.
If the ZIP is over 25 MiB, extract it locally and choose only Connections.csv. If that file is missing, confirm that the requested archive included Connections and download it again. Do not email the archive or private normalized backup for support.
Include your source, device and browser, the step you reached, what you expected, what happened, and the exact on-screen error after redacting personal details. Never attach a raw archive, private normalized backup, or unredacted network screenshot.
It should use metadata such as participant, message counts, direction, and meeting cadence—not message bodies or subjects. The owner chooses whether to add it.
Profile URL, email, company, location, aliases, and human confirmation help resolve identity. Ambiguous matches stay separate until reviewed.
Product decisions, methods, tests, and aggregated lessons. Private contact lists, addresses, and message content do not belong in public documentation.