Who You Know privacy policy

For Who You Know - Recent Contacts (“Who You Know”). Effective November 1, 2026. Operator: SilverLogic, LLC. Privacy contact: support@tsl.io.

What changed from the October 21, 2026 policy: new sections on Who You Know Pro purchases, complimentary access and access codes, and invitations and referrals, and a note that some features need Pro.

Local use and your choices

You can use local contact scanning, notes and other local features without a Who You Know account. The app requests access to Contacts, camera, photos, calendar, microphone or speech recognition when a related feature needs it. You can change those permissions in iOS Settings. Some features need Who You Know Pro, described under Payments and subscriptions. Limited Contacts access restricts the cards Who You Know can see; complete contact recovery requires access to the address book.

Optional account and cloud features

Account features process your account name, email, password hash, device labels and identifiers needed for sessions and notifications. When you enable cloud backup or use account-backed synchronization, Who You Know can store the address-book cards you grant Who You Know access to, their photos, contact details, notes, tags, events, follow-up history and other app content. Contact cards can contain names, email addresses, phone numbers, postal addresses, organizations, birthdays, websites, social profiles and other fields you include.

Cloud backups are associated with your personal account. Joining an organization does not give its members access to your private backup. Who You Know also processes request and abuse-prevention records to secure the service.

Organizations and teams

Organization and team features process memberships, invitations, shared events and permitted progress information. Relationship sharing uses the notes, activity or follow-up fields and audiences you select. An established organization may retain an authorized configuration that shares full relationship history with permitted members. Organization administrators can see the detail their role permits. Consider the people represented in a contact card before sharing their information.

Services you connect

If you connect a supported CRM or messaging service, information needed for the action or synchronization can be sent to that service, including contact details, notes, activity, messages or photos. Provider access depends on your account, organization and granted permissions. The provider’s own privacy terms apply to copies it receives. Disconnecting a provider stops Who You Know’s future access; it does not automatically erase copies already stored by that provider.

Public photo sharing normally opens the iOS share sheet, where you choose a destination. An organization can retain an authorized Slack workflow. Who You Know does not grant public accounts access to another organization’s private integrations or writing samples.

Optional message logging and AI

iOS does not let Who You Know read Messages or WhatsApp directly. You can explicitly configure a Shortcuts automation to hand it individual received messages, or paste a conversation yourself. Logged received messages become contact notes; sent messages become follow-up history. These notes and follow-ups can be synchronized to your connected CRM and included in cloud backups when those features are enabled.

The optional Mac companion is offered to an authorized organization or where a companion download is available. Before it reads or forwards correspondence, the Mac asks you to enable forwarding for that server and account. Full Disk Access alone does not enable forwarding. After this choice, the iPhone can connect automatically unless you turned Mac logging off there. The companion uploads only one-to-one messages from your selected Messages and WhatsApp sources with work contacts selected by your phone, including message text, the other party’s phone number or email address, channel and date. Group chats and other contacts’ messages are not forwarded. A work contact is someone associated with an event, deal or CRM record, or given a contact type or a priority other than Ignore. You can choose sources and the initial lookback date, pause forwarding, or revoke it in the companion.

Your Who You Know server receives the work-contact watchlist and matching messages to deliver them to your signed-in phone. The raw inbox text and other-party address are removed when the phone acknowledges a message; undelivered messages and bare delivery tombstones expire after 30 days. Messages already saved as notes or follow-ups remain subject to contact, CRM and cloud-backup retention, rather than disappearing at delivery acknowledgement.

AI is optional and logged-message analysis starts off. Before sharing with AI, the app identifies the configured third-party recipient and links its privacy terms. Drafting and automatic message analysis require separate permission on this device for that account, server and provider; a changed provider or disclosure requires a new choice. If the recipient and terms are not identified, these AI actions are unavailable. You can withdraw either choice in Settings.

When you allow drafting and choose Personalize with AI, the provider receives your profile, the contact’s name, work details and your priority for them, event details, selected notes and attributed team notes, draft text and up to six earlier sent messages used for writing style. Your account’s separately configured sent-mail samples or style profile can also be included when the permission screen says so. When you allow logged-message analysis, the provider receives each logged message’s full text, direction, channel, contact name and company, your name and the date to find action items and follow-up dates. This permission also covers messages logged later by Shortcuts or your Mac without asking for every message. A direct personal API-key connection uses Anthropic; an organization’s configured gateway must identify its actual recipient in the permission screen. The recipient’s privacy terms govern copies it receives.

Calendar and keyboard

The optional keyboard uses calendar availability and app settings to propose meeting times and show selected scheduling links. It does not need access to text you type elsewhere. Calendar permission is requested by the containing app. When you choose to insert a proposal into another app, that app receives the inserted text. iOS Full Access permits a keyboard to use network functionality; enable it only if you want the related keyboard features.

Payments and subscriptions

Who You Know Pro is sold only through Apple's In-App Purchase. Apple processes your payment. We never receive your card or bank details. Apple does not give us your Apple ID email address or your name as part of a purchase.

What we receive from Apple. When you buy, renew, change, cancel or are refunded for Pro, we receive signed records from the app and from Apple's App Store Server Notifications and App Store Server API. They can include:

The app account token. When you buy Pro while signed in, the app gives Apple your Who You Know account ID (a random identifier that contains no name or email address), and Apple returns it in its records so we can link the purchase to your account. A purchase made while signed out carries no account ID. When you later sign in, the app sends that purchase to us and we link it to the account you signed in to.

How we use it. We use this information to unlock Pro in the app, in the web app and in the Mac companion; to handle renewals, expirations, billing problems and refunds; to apply trials, offer codes and referral rewards; to prevent fraud and abuse; to answer support questions; and to keep financial and tax records.

What we send Apple. We send Apple the app account token at purchase. When we apply a referral reward as a renewal-date extension, we send Apple the original transaction ID, the number of days and a reason. We may ask Apple for the current status of your transactions.

Apple's role. Apple's privacy policy governs Apple's own processing of your purchase and payment information.

Retention. We keep billing records, meaning the purchase information listed above, while your account exists. When you delete your account, its purchase records are deleted with it. We keep a record of each notification Apple sent us (the original transaction ID, the notification type and its date, without your account), so that a repeated notification is not applied twice. If your subscription keeps renewing because you did not cancel it, Apple keeps sending us its records after the deletion. We store them without linking them to any account; they still carry the account ID the purchase was made with.

Complimentary access and access codes

SilverLogic can give free Pro access to an individual account by email address, to every account with a verified email address at a domain we choose, or to every member of an organization. We record each grant: what it covers (an email address, a domain or an organization), who at SilverLogic created it, when it starts and ends, and why. To apply a domain grant, we check the verified email address on your account. To apply an organization grant, we check your membership. The access ends when you no longer have that verified email address or membership.

Access codes are redeemed on the Who You Know website while you are signed in. When you redeem a code, we record the code, your account, and the date and time. With each redeemed code we also store a one-way hash of your email address, not the address itself, so that the same person cannot redeem a code twice.

We keep grant and redemption records, including after the access ends, to answer questions and prevent abuse. Complimentary access given to your account, and the record of which codes your account redeemed, are deleted with your account. The one-way hash of your email address and the redemption date stay with each code you redeemed after your account is deleted, so that the same person cannot redeem that code a second time, for example by registering again. Complimentary access SilverLogic granted to your email address stays until we remove it.

Invitations and referrals

Your invite link. Every signed-in user has a personal invite link: https://whoyouknow.tsl-beta.com/r/ followed by a code that identifies your account to us. Anyone who opens it sees your first name and the offer, so share it only where you are happy for your first name to appear.

When someone joins through your link. We record that their account came from your link, and when. We also store a one-way hash of their email address, not the address itself, so that one email address is referred only once. We then record, from Apple's purchase records for their account, whether they made a first paid charge, which App Store purchase it was (its transaction ID and original transaction ID) and whether Apple refunded it. We use this only to decide whether you earned a reward, to run the program and to prevent abuse. Once your friend has verified their email address and claims the free month in the app or the web app, within 14 days after joining through your link and before any App Store purchase or trial, we give them a single-use Apple offer code for a 1-month trial while we have codes to give, and record which code we gave them and when. We limit how many codes are given each day for each inviter and each network address, so when many friends join at once a code can take up to a day.

Your rewards. We record each free month you earn and whether it was applied as an Apple renewal-date extension, applied as complimentary access, banked or withdrawn.

What each side sees. You see how many invited friends joined and paid, and your rewards. We do not show you their names, their email addresses or which of them paid. If you invited only a few people, you may be able to guess who joined. Your friend sees your first name on the invitation page.

Preventing abuse. To detect self-referrals and duplicate or fake accounts, we may compare records we already keep, such as email addresses and their domains, sign-in and device records, IP addresses and purchase records.

Retention. We keep referral records while your account exists. When you delete your account, your invite link and your rewards are deleted, and the referrals made with your link are no longer linked to you; each friend's side of them stays (that they were referred, and any offer code they were given). A referral you joined through stays, without your account: it keeps its dates, its status, the one-way hash of your email address, the offer code you were given and, if you paid, the transaction ID and original transaction ID of the App Store purchase that paid. We keep it so the inviter's count stays correct, a reward can still be withdrawn after a refund, and the same email address or App Store purchase is never referred or rewarded again, for example after you register again. That offer code is never given to anyone else.

How information is used

Information is used to provide the features you choose, maintain accounts, synchronize and recover your data, deliver service-related messages and protect the service. The app’s privacy manifest declares app functionality and, in versions with optional usage analytics, analytics as purposes of collected data. It declares no advertising or cross-company tracking. Service providers process information needed to operate hosting and secure network delivery (including Cloudflare), service email delivery (Resend), and push notifications (Apple). Apple may process dictation through its speech service when on-device recognition is unavailable. Connected services process the information you choose to send to them under their own terms. AI-assisted features require a configured, identified provider and your separate explicit sharing permission, as described above.

Usage analytics

This public release does not send usage analytics to PostHog. Local usage counters used to decide when to offer Apple’s review prompt stay on your device and work without an account.

Before analytics is enabled in a future release, we will identify its provider, retention period and in-app deletion process and ask for an optional choice. Account-linked analytics will not be enabled without a deletion process initiated by account deletion in the app. You can use Who You Know without allowing analytics. If your installation shows a previously used Analytics ID, contact support@tsl.io for help with that history. The app does not enable analytics screen recording, advertising identifiers or collection of contact, photo, note, message or search contents.

Reports, blocking and shared content

A basic on-server phrase filter blocks some obvious direct threats and targeted abuse in text submitted for shared publication. It does not inspect private contact cards, backups or CRM data, does not send text to an AI service, and does not detect every kind of objectionable content. Reporting, blocking and human review remain available.

You can report objectionable shared content or a member and block an unwanted member through the app’s reporting controls. A report stores your explanation, identifiers of the reporter and reported account or shared item, a limited snapshot of the reported content, timestamps and moderation status. This may include the relevant event name and location, community name and notes, shared-contact name or message, and member or organization name. Platform administrators can review reports, remove violating shared content and restrict an abusive account. Blocking choices restrict interactions supported by the service. Account deletion removes reports you submitted and reports identifying your deleted account as author or subject; independently authored reports without that identifying relationship remain for moderation. For privacy or safety help, contact support@tsl.io.

Security

Network communication with Who You Know uses HTTPS. Account and organization permissions restrict access to cloud data. The server processes data needed for account-backed features; cloud backup is not end-to-end encrypted. Exported files and copies shared to other apps are subject to the protections of the destination you choose.

Deletion, recovery copies and retention

You can initiate account deletion in Who You Know’s account settings. Deletion removes your personal cloud account data, contact backups, photos and personal provider credentials from active Who You Know storage. It also removes your authored shared events, communities, notes and related sharing records, including content you published to an organization you later left, and identifying administrative activity. Organizations, teams and other members’ independently authored content remain. It does not delete your device’s address book, another person’s independently saved local copy, exported files or copies held by connected providers.

Service-managed routine disaster-recovery snapshots are retained for 30 days and expired copies are removed through backup maintenance. A protected recovery point may be kept longer if no newer backup has been verified, or if a security incident or legal requirement requires a hold. Access to recovery copies is restricted, and they are not used for ordinary account features. Older recovery copies may contain data from before a deletion; they remain restricted and are not used for ordinary account features. Manually preserved incident, deployment and off-host recovery copies are reviewed separately. These operational copies are separate from the contact backup history you choose to keep in your active account. Contact support@tsl.io with a privacy or deletion request.

Contact and updates

SilverLogic, LLC operates Who You Know. Contact support@tsl.io with questions about this policy. A published replacement policy will identify its effective date.