Digiri Privacy Policy

Effective date: August 18, 2026 Last updated: August 18, 2026

Who this is for

Digiri ("we," "us," the "App"), operated by Digiri, LLC, a Georgia limited liability company, is a relationship-intelligence app. This policy covers the mobile app, its web version at trydigiri.com, and the backend API both talk to — same account, same data, same rules regardless of which one you use. It does not cover third-party sites you might reach by tapping a link out of the app.

What we collect

Account information. Email, a hashed password (we never store your password itself), your display name, and two settings you control: a visibility level (Open, Connections-Only, or Private) and your subscription tier.

Your network. For every connection you add: their name, who introduced you and why ("provenance"), the date, tags you assign, and any notes you write. This information is about people in your life — much of it, by nature, is information about people who may not be Digiri users themselves. We treat it as your private data: it is never shown to anyone else, including the person the note is about.

Contact claiming. If you add someone who isn't yet on Digiri and optionally give us their email so we can recognize them later, we check that email against new and existing accounts. If they join (or already have an account) and confirm that same email address, we automatically link your entry to their real account — the same as if you'd searched for and added them directly, which never requires their permission today either. We tell you when this happens; we don't tell them, and we never act on an email we haven't confirmed belongs to a real, verified account.

Invite-code connections. When someone signs up using your invite code, we automatically record a connection between you and them — provenance ("Invited you to Digiri" / "Joined Digiri using your invite") filled in the same way you'd fill in provenance for any connection you add yourself. Both of you can see this connection immediately; there's no separate confirmation step, since redeeming a specific person's invite code is itself the act we treat as mutual.

Circles. The names and color-groupings you create to organize your connections (e.g. "Work," "Travel"). Circles are private to your account and are never visible to other users, including people in your circles.

Relationship topology. When you connect with someone who is also a registered user, we record that a connection exists (and, separately, when you tell us two of your contacts know each other) so the app can compute paths and mutual connections. This topology data is what powers the Degrees search feature.

Introduction requests. If you request an introduction to someone through a mutual connection (a "bridge"), we store the request, your optional message, and its status. Consistent with how the app is designed to work: the target of an introduction is never shown that a request exists unless the bridge agrees to make the introduction.

Messages. If you and a connection have added each other (a "mutual" connection), either of you can start a direct message thread inside the app. We store the messages you send — only the two people in a conversation can read it; we don't use message content for anything else, and no one on our team reads it except as needed to investigate a report of abuse or a legal request. If one participant deletes their account, the conversation stays visible to the other participant (the same way an email you sent doesn't disappear from the recipient's inbox if you close your email account) — their messages remain attributed to their name, but are no longer linked to a live account.

Reminder preferences. How often (if at all) you'd like to be nudged to reach out to someone, and when you last did.

Push notification token. If you grant notification permission, we store a device token so we can deliver reminder and introduction notifications. You can revoke this at any time in your device settings.

Invite codes and waitlist. If you're invited, we track which code was used and by whom. If you join the waitlist without a code, we store only the email address you give us.

Contacts (only if you choose to import). The app can optionally read your device's contact list to help you add people you already know — this only happens if you tap "Import from your contacts" and grant the permission your device asks for. We read contact names to show you a selection list; nothing is sent to our servers or stored by us until you actively select a specific contact to import, at which point it becomes a connection like any other (see "Your network," above). You can decline or revoke this permission at any time in your device settings, and the app works fully without it — contact import is a convenience, not a requirement.

Subscription tier. Whether your account is on the Free or Pro tier. As of this writing, Digiri is free for all users during the beta and no payment information is collected. When paid subscriptions launch, this section will be updated to describe what a payment processor (e.g. Apple, Google, or RevenueCat) shares with us — typically limited to subscription status, not full payment details, which those platforms handle directly.

Product analytics. We use PostHog to understand how the app is used in aggregate (e.g., how many people complete signup, use path search, or act on a reminder) — never for advertising, and never shared with or sold to third parties. Autocapture is off: only a small, deliberate set of app events is tracked, tied to your account so it merges with anything logged server-side, not an anonymous cross-app identifier.

Beta feedback. If you use "Report a problem" to send us feedback, we store the message you write and, if you choose to attach one, a screenshot. Screenshots are stored privately (not publicly accessible by URL) and are only ever viewed by our team when reviewing your report. Because a screenshot of the app can show your own network data on-screen — connections, circles, or notes — please only attach what you're comfortable with us seeing while reviewing the report. Deleting the feedback report (or your account) also deletes any attached screenshot from storage, not just the report text.

What we don't collect. We don't collect location data, and the app does not include advertising SDKs or third-party ad tracking.

How we use it

We do not sell your data, and we do not use your connections' information for advertising.

Who we share it with

We use the following infrastructure providers to run the app. Each processes data on our behalf under their own security and privacy terms — we don't sell or share your data with them for their own purposes:

We maintain a more detailed internal register of these subprocessors — including each one's data processing agreement status and hosting region — which we can provide on request; contact us at team@trydigiri.com.

We do not share your data with data brokers or advertisers. We will disclose information if required by law.

Your choices

Data retention

Active account data (your circles, connections, provenance, reminders, and everything else described above) is retained for as long as your account exists — there is no automatic expiry while you keep using Digiri. If you delete a connection, its provenance and any intra-circle "knows each other" facts tied to it are removed. If you delete a circle, the people in it are not deleted — they're simply no longer grouped under that circle. If you delete your account, your account data is removed immediately and cannot be recovered.

Security and audit logs — records that exist to keep the service secure and accountable, not to provide app features (login sessions, password-reset and email-verification links, and our internal admin action log) — are automatically deleted after 90 days, regardless of whether your account is still active.

Deleted-account records: even though your account data is removed immediately on deletion, our internal admin action log is designed to keep a record of that an action happened (e.g., "an account was deleted") for accountability, separately from the 90-day rule above. Any of your identifying information still visible in that internal log (e.g., your email address, if an administrator had previously taken an action involving your account) is wiped within 30 days of your account's deletion, even if the log entry itself persists longer for the accountability reasons described above.

Children's privacy

Digiri is not directed at children under 13 (or the minimum age required by your country), and we don't knowingly collect data from them. Contact us at team@trydigiri.com if you believe a child has created an account.

Security

We use industry-standard measures (encrypted connections, hashed passwords, short-lived access tokens) to protect your data. No system is perfectly secure, and we can't guarantee absolute security.

When you set or change a password, we check it against Have I Been Pwned's public database of passwords exposed in known data breaches, so we can reject one that's already compromised elsewhere. This uses a privacy-preserving technique (k-anonymity) that never sends your actual password anywhere — only a short, non-reversible partial fingerprint that thousands of other passwords could also share, not something that identifies you or your password specifically.

One honest difference between the mobile app and the web version: on your phone, your login session is stored in the device's own secure hardware-backed storage (Keychain on iOS, Keystore on Android). In a browser, that same protection doesn't exist, so the web version currently stores your session the way most web apps do — a tradeoff we're noting plainly rather than glossing over, not something we consider settled long-term.

Changes to this policy

If we make material changes, we'll notify you in the app or by email before they take effect.

Contact

Questions about this policy or your data: team@trydigiri.com

This policy is reviewed and updated as Digiri changes — particularly when we add a new feature or third-party service that touches user data. We'll update the "Last updated" date above whenever we do, and notify you in the App or by email for material changes, per the "Changes to this policy" section.