Privacy Notice

Operator: IWYK, Inc., 1660 International Drive, Suite 600, McLean, Virginia 22102 · Contact: privacy@iwyk.ai

This Notice explains what information IWYK ("we," "us") collects through iwyk.ai (the "Service"), why we collect it, what we deliberately do not collect, how long we keep it, and what choices you have. It applies to Members, Connectors, and site visitors.

1. Summary

IWYK is designed so that matching can happen without us holding a readable copy of your professional network. Company names from your network are converted to one-way hashes in your browser before they reach us, and we store coverage scores rather than a list of companies.

Being precise about what that means: these hashed records are pseudonymous, not anonymous. Because we hold the secret used to compute them and the universe of company names is finite, we could in principle test whether a particular company appears in a particular vault. We therefore treat vault records as personal information and give them the same protection and the same deletion rights as everything else in this Notice. What the design does achieve is real: we cannot browse or export a plaintext list of your connections, and a database compromise would not yield one.

We do not sell personal information. You can delete your account at any time.

2. Information We Collect

2.1 Account and authentication

Email address; password (stored by our authentication provider as a salted hash — we never see it); federated identity if you sign in with Google, Apple, Microsoft, or LinkedIn; role (Member / Connector / administrator); account timestamps.

2.2 Profile and intake

2.3 Transactions

IWYK does not collect card numbers. If you book a session, Stripe collects and stores your payment card; IWYK stores the Stripe customer and payment-method identifiers, session times, rates, charges, and dispute outcomes. If a Connector connects a Stripe account, Stripe collects the payout and identity details it requires; we receive account status (for example, whether payouts are enabled), not bank or card numbers.

2.4 Technical and usage

IP address (used for rate limiting and abuse prevention), device and browser signals, pages viewed, referral and UTM parameters, a first-party attribution cookie linking marketing touches to a rotating identifier, and product-analytics events.

We do not use a third-party error-monitoring service. When something goes wrong, the diagnostic detail is written to our own server logs and to no one else's system.

2.5 Communications

Messages you send us, and the delivery metadata for transactional emails we send you.

2.6 What we do not receive

The contents of a network archive you analyze — for example, a LinkedIn connections export — are processed entirely in your browser and are not uploaded to us. See Section 4.

3. Why We Process Information

To provide the Service you asked for (matching, routing, and introductions); to keep accounts secure and prevent abuse and fraud; to comply with legal obligations and respond to lawful requests; to send transactional messages; and, where you consent, to measure marketing performance.

Where a "legal basis" analysis applies to you, contract performance and our legitimate interests cover most processing, legal obligation covers records we must keep, and consent covers optional analytics and marketing measurement. You may withdraw consent at any time without affecting processing already carried out.

4. How Network Matching Data Is Handled

This describes our actual architecture.

  1. Processing happens in your browser first. When you build your Network Vault, any source archive is read and processed by client-side code. The archive itself is never transmitted to or stored by IWYK.
  2. Company names become hashes. Company names are normalized and hashed with SHA-256 using a salt that ships in the browser bundle. On receipt, our servers apply a second, server-only secret (a "pepper") before anything is stored. The value at rest therefore cannot be reversed by someone who obtains only our database, or only the public salt.
  3. What is stored is a score, not a list. For each hashed company we store two coverage scores (depth and strength) and a provenance label (IMPLIED, derived from a parsed resume; DECLARED_RECALL; or DECLARED_MANUAL). We do not store the plaintext company names from this process, the source archive, or contact details of anyone in your network.
  4. Honest limit on this design. We hold the pepper. Anyone with access to it — meaning us, or someone who compromised both our database and our secret store — could compute the hash of a candidate company name and check it against a vault. We do not do this, and access to the pepper is restricted, but we will not tell you the records are anonymous when they are not. They are treated as personal information throughout this Notice.
  5. Resume parsing for coverage. If you generate coverage from a resume, the text is parsed in memory to derive employment history, and the resume text from that flow is not persisted. An excerpt of at most 8,000 characters may be sent to Anthropic's API to correct parsing errors.
  6. Introductions are double-blind until acceptance. Your free-text context, rationale, outcome, name, email, and resume are withheld from a Connector until that Connector accepts your request. Before acceptance, a Connector sees only a brief with direct identifiers removed.
  7. Member resumes are stored. Unlike Connector coverage parsing, a Member resume you upload is stored in a private storage bucket reachable only by our application, parsed once with the structured result attached to your profile, and disclosed to a Connector only after that Connector accepts your request.

5. Service Providers

We share personal information only with vendors needed to operate the Service, each bound by a written data-processing agreement.

ProviderPurposeNotes
SupabaseAuthentication, database, private file storageResumes in a private bucket; credentials stored as hashes
Stripe (incl. Identity and Connect)Identity verification; Connector account onboarding; session paymentsCard data, if any, handled by Stripe under its own privacy policy
AnthropicAI-assisted parsing of text you submitTransient excerpts; see Section 4(5)
Resend (Plus Five Five, Inc.)Transactional email deliveryOur processor for message content and recipients; an independent controller for its own service activity logs. Certified under the EU-U.S. Data Privacy Framework and UK Extension
VercelHosting, edge network, product analytics
UpstashRate limitingReceives hashed rate-limit keys

Where a provider acts as an independent controller for some of the data it holds — as our email provider does for its own service activity logs — that processing is governed by the provider's own privacy policy rather than by our instructions, and we say so rather than implying we control it.

Advertising measurement. We maintain first-party attribution and server-side conversion integrations that could transmit hashed event identifiers to advertising platforms when campaigns run. These are inactive. If we activate them, we will update this Notice, provide the opt-out mechanism described in Section 8 before activation, and honor Global Privacy Control signals.

We may also disclose information to comply with law or legal process, to protect rights and safety, or in connection with a merger, financing, or sale of assets, in which case this Notice continues to apply until superseded by notice to you.

We do not use personal information to make automated decisions producing legal or similarly significant effects. Matching produces a routing suggestion; every routed match requires a human Connector to accept or decline.

6. Cookies and Similar Technologies

We use a small set of technologies:

CategoryWhat it doesConsent
Authentication session cookieKeeps you signed inStrictly necessary — always on
Security and rate-limitingPrevents abuseStrictly necessary — always on
First-party attribution cookieRecords which marketing touch preceded a signupNon-essential — set only after you accept
Product analytics (Vercel)Aggregate page and funnel metricsNon-essential — set only after you accept

Our consent banner offers two choices: Accept all or Decline non-essential. Non-essential technologies are not set until you accept. You can change or withdraw your choice at any time from the "Cookie preferences" link in the site footer, and we retain a record of what you chose and when. We honor Global Privacy Control signals sent by your browser as a decline of non-essential technologies and as an opt-out of sharing.

7. Retention

The Data Retention & Deletion Policy sets out each record class, its retention period, and the reason for it, and is incorporated into this Notice. In summary: account content persists until you delete it; on deletion, identifiers are removed, vault records are purged, and resume files are destroyed; a minimized set of financial, security, and consent-evidence records is retained on the schedule in that Policy; short-lived technical logs age out on operational cycles.

8. Your Choices and Rights

We offer the rights below to every user, wherever you live. We do this as a matter of policy. Whether a particular comprehensive state privacy statute currently applies to IWYK depends on thresholds that turn on our revenue and the number of consumers whose data we process — figures that are below most of those thresholds today. We will not imply that a statute governs us when it does not, and we will update this Section as our footprint changes.

We verify requests against your account credentials and respond within 45 days, extendable once by a further 45 days with notice.

If you are in the EEA or UK, you additionally have rights of restriction and objection, and the right to lodge a complaint with your supervisory authority.

9. International Transfers

IWYK operates in the United States and our providers process data in the United States and, for some vendors, elsewhere. If you use the Service from outside the United States, your information is transferred to the United States. Where EEA or UK law applies to a transfer, we rely on the European Commission's Standard Contractual Clauses and the UK International Data Transfer Addendum as incorporated in our vendor agreements. Standard Contractual Clauses address the transfer only; they do not by themselves establish a lawful basis or satisfy other obligations.

10. Security

We use TLS for data in transit, AES-256-GCM encryption for designated sensitive fields at rest, keyed hashing for matching data, restricted database roles, validation of production secrets at startup, rate limiting, and audit logging of sensitive actions.

No system is perfectly secure and we do not claim ours is, nor do we hold any security certification. Report a suspected vulnerability to security@iwyk.ai.

11. Children

The Service is for adults 18 and older and is not directed to children. We do not knowingly collect personal information from anyone under 18, and we delete it if we learn we have.

12. Changes

We will post changes with a new effective date and, for material changes, notify registered users by email and in-product notice. Prior versions are retained and available on request.

13. Contact

privacy@iwyk.ai · IWYK, Inc., 1660 International Drive, Suite 600, McLean, VA 22102.


END OF PRIVACY NOTICE