It just works.Heyou is built on user-owned sources, employee network ownership, and view-oriented use. This page is the public version of the same governance pack we send legal and security reviewers under MNDA — the philosophy, the boundaries, the controls, and the documents.
Each principle is a stand-alone commitment. Click a card to jump to the supporting detail in the public trust overview below.
Heyou Research and Development Ltd. maintains an ISO/IEC 27001:2022 Information Security Management System, audited by SII-QCD and recognized internationally through IQNET. The SOC 2 Type II audit is in flight — engagement letter signed and observation period underway; the letter of intent is available now and the final report will follow under MNDA.
Scope: Development and provision of a cloud platform for data processing to generate relationship-based engagement recommendations for humans and agents.
Download SII certificate (PDF)Scope: Same scope as the SII certificate. IQNET recognition lets non-Israeli reviewers verify the attestation against their own national IQNET member.
Download IQNET certificate (PDF)Scope: Examination of Heyou's controls relevant to security, availability, and confidentiality over an observation period, against the AICPA Trust Services Criteria. Audit engagement letter signed; observation in flight. The final SOC 2 Type II report will be available under MNDA on completion.
Download letter of intent (PDF)To verify the SII certificate independently, scan the QR code on the PDF or look up certificate number 1127825 at sii.org.il. To verify the IQNET attestation, use registration number IL-1127825 against any IQNET member.
How Heyou activates relationship intelligence while respecting the boundaries between company-owned systems, employee-controlled sources, and personal professional context.
Heyou helps organizations activate relationship intelligence while respecting the boundaries between company-owned systems, employee-controlled sources, and personal professional context.
Professional relationships often exist across many places: company systems, work applications, communication tools, professional communities, calendars, inboxes, and other sources an employee may use in the ordinary course of their professional life.
Heyou is designed to help employees organize relevant professional context without turning employee-owned sources into company-operated systems.
An employee's professional network is a valuable relationship asset built over years through work, trust, conversations, communities, shared experience, and personal credibility.
Heyou is built on the principle that employees should remain in control of their own professional network and the sources that reflect it.
Companies benefit when employees can activate trusted relationships for business purposes, but that benefit should not require treating employee-owned accounts, communities, or relationship history as company-owned property.
Heyou is designed to help organizations benefit from relationship intelligence while respecting the employee's ownership and control over their professional network.
Heyou is built around a clear separation of control:
Employees control employee-owned sources. Customers control what source categories are permitted for their organization. Heyou provides privacy, security, and governance controls.
When a source is controlled by the employee, Heyou does not treat it as a company-owned system. The employee decides, at their sole discretion, whether to connect, enable, export, upload, or contribute that source, subject to the customer's tenant-level policies.
Where enabled by the customer and authorized by the employee, Heyou may process professional relationship context available to that employee for the purpose of helping them understand, organize, and act on their professional network.
Heyou applies data-minimization principles and limits processing to professional relationship signals and related metadata needed to generate relationship intelligence.
Where source providers offer native export, download, permission, or authorization mechanisms, Heyou is designed to prefer those mechanisms where practical and appropriate.
Heyou's purpose is to help users understand relationship context and make better human decisions. Heyou is not designed to operate external accounts or replace user judgment.
Heyou is designed to minimize the amount of source information processed and retained by Heyou's cloud systems.
Where practical, source information may be transformed locally into normalized relationship signals and related metadata before being processed by Heyou. Heyou's goal is to generate relationship intelligence, not to store, reproduce, or redistribute third-party source content.
Where relationship intelligence can be generated from metadata, derived signals, or locally transformed information, Heyou prefers those approaches.
For messaging and similar sources, Heyou processes metadata only and does not collect conversation content.
Heyou is designed as a relationship-intelligence platform, not an external-account engagement automation platform.
Where employee-owned sources are enabled by the employee, Heyou's use is view-oriented and purpose-limited. Heyou may help analyze professional context available to the authorized user, but it does not perform externally visible engagement actions on third-party services.
Heyou does not automatically send messages, connection requests, comments, likes, follows, posts, profile changes, or similar actions on behalf of users.
This distinction is central to our approach: Heyou helps users understand relationships; users decide what actions to take.
Heyou does not collect passwords.
Heyou does not collect or store third-party platform credentials.
Heyou does not collect or store third-party session tokens.
Heyou does not bypass login, privacy settings, paywalls, or technical access controls.
Heyou does not continue source access after a user or customer disables that source.
Heyou does not give AI unrestricted or unauthorized access to employee-owned accounts or external services.
Heyou does not automatically perform externally visible engagement actions on behalf of users.
Heyou does not operate employee-owned accounts.
Heyou does not provide administrators with access to employee-controlled conversation content.
Heyou uses AI to analyze authorized relationship context within customer-configured boundaries.
AI may help identify relevant relationships, trusted paths, relationship strength, business context, and suggested next steps. AI may also identify where additional context could improve accuracy.
However, additional source access requires appropriate user authorization and must remain within the customer's configured source permissions. Heyou does not give AI unrestricted or unauthorized access to employee-owned sources or external services.
Human review remains central. Heyou may recommend actions, but users decide what to do at their sole discretion.
The use of Heyou is always subject to our Privacy Policy. For messaging and similar sources, Heyou does not collect conversation content.
Heyou processes metadata only, such as participants, timestamps, interaction frequency, and other non-content signals needed to understand relationship context.
Conversation context will not become company-visible.
Employees should understand and control what is connected, what is processed, and what may be visible to their organization.
Employee-owned sources are authorized at the individual user level. Authorizing one source does not give Heyou access to other employees' external accounts, customer-owned systems, or unrelated company assets.
Heyou does not centrally operate employee-owned accounts, does not collect credentials or session tokens, and does not give administrators direct access to employee-controlled conversation content.
This user-level authorization model is designed to preserve clear boundaries between employee-controlled sources, company systems, and other users' accounts.
Customers can decide which source categories are enabled for their organization.
A customer may choose to allow company-owned systems only, such as CRM, work email metadata, calendar metadata, meeting transcripts, and approved business applications.
A customer may also choose to allow employee-authorized professional sources, communities, messaging sources, or other source categories, subject to its internal policies and specific employee consent.
Source-level controls allow customers to:
Heyou is designed as a multi-source relationship-intelligence platform. No single employee-owned source is required for Heyou to operate.
Customers can enable, limit, pause, or disable source categories based on their internal policies, employee preferences, or third-party service requirements. If a specific source is unavailable, disabled, or no longer appropriate for use, Heyou can continue operating using other customer-approved sources, such as CRM data, work email metadata, calendar metadata, meeting transcripts, approved business applications, native exports, and other authorized inputs.
Where a third-party service provides a user-facing notice, warning, restriction, or other indication related to source activity, Heyou does not control that notice or the service's enforcement decisions. The user or customer can pause or disable the relevant source connection at any time.
Heyou is not designed to bypass or ignore third-party access controls, restrictions, revocation signals, or customer disablement settings.
This source-level control model is intended to reduce dependency on any single external service and allow customers to manage source usage according to their legal, security, and governance requirements.
Different services have different terms, technical controls, export options, authorization models, notice mechanisms, and permitted-use requirements.
Heyou is designed to support responsible use through customer-configured source controls, user authorization, data minimization, local transformation where practical, platform-provided export or authorization mechanisms where practical, no credential collection, no session-token storage, no access-control bypassing, no unrestricted AI access, and no automated external engagement.
Heyou does not control how third-party services interpret or enforce their own terms or policies.
Customers are responsible for configuring Heyou in accordance with their internal policies and applicable third-party service requirements.
Customers and employees can enable, limit, pause, or disable employee-owned source categories at any time. Where a customer chooses to avoid employee-owned external-source access, Heyou can operate using company-approved sources only.
Heyou is built around a user-owned source model.
Employees own and control their professional network assets.
Customers control which source categories are permitted in their tenant.
Heyou is view-oriented, minimizes raw source data, and does not automate external engagement.
Where practical, Heyou transforms source information into relationship signals and metadata before cloud processing.
Heyou does not collect credentials, store session tokens, bypass access controls, ignore revocation signals, or operate external accounts.
Conversation content is not collected.
Messaging and similar sources are metadata-only.
Customers can disable employee-owned source access and rely only on company-approved systems.
Heyou is multi-source by design and does not depend on any single employee-owned source.
Our goal is to help organizations activate relationship intelligence while preserving clear boundaries between employee-owned sources, company systems, and personal professional context.
No. Heyou is view-oriented by design. It helps users analyze professional relationship context, but it does not automatically perform externally visible actions on third-party services.
Heyou does not automatically send messages, connection requests, comments, likes, follows, posts, profile changes, or similar engagement actions on behalf of users.
No. Heyou does not collect passwords, third-party platform credentials, or third-party session tokens.
Heyou also does not bypass login, privacy settings, paywalls, or technical access controls.
No. For messaging and similar sources, Heyou processes metadata only, such as participants, timestamps, interaction frequency, and other non-content signals needed to understand relationship context.
Conversation content is not collected.
Heyou does not provide employers and administrators with direct access to employee-controlled content.
Employee-owned sources are authorized at the individual user level. Authorizing one source does not give Heyou access to other employees' external accounts, customer-owned systems, or unrelated company assets.
Yes. Customers and their employees can enable, limit, pause, or disable source categories at the tenant level.
Customers that prefer to avoid employee-owned external-source access can configure Heyou to operate using company-approved sources only.
No. Heyou is a multi-source relationship-intelligence platform.
If a specific employee-owned source is unavailable, disabled, or not permitted by customer policy or by a certain employee, Heyou can continue operating using other customer-approved sources, such as CRM, work email metadata, calendar metadata, meeting transcripts, approved business applications, native exports, and other authorized inputs.
Different services have different terms, technical controls, export options, authorization models, notice mechanisms, and permitted-use requirements.
Heyou is designed to support responsible use through user authorization, customer-configured source controls, data minimization, local transformation where practical, platform-provided export or authorization mechanisms where practical, no credential collection, no session-token storage, no access-control bypassing, no unrestricted AI access, and no automated external engagement.
Customers are responsible for configuring Heyou in accordance with their internal policies and applicable third-party service requirements.
What the CISO, Legal, and Privacy reviewer needs first — Heyou's data scope, control boundaries, AI posture, subprocessors, and incident commitments.
Heyou is a relationship intelligence platform that helps organizations understand existing professional relationships and identify relevant, human-led paths into target accounts.
Heyou analyzes authorized professional relationship context to help users answer questions such as:
Heyou is designed to improve professional engagement by helping users understand context before they act. It is not designed to replace user judgment or operate external accounts on a user’s behalf.
Heyou is designed as a decision-support and engagement-assist platform.
The system may analyze relationship and business context, recommend next-best actions, summarize relevant signals, and prepare draft messages for user review. External actions remain under human control.
Heyou does not automatically send messages, connection requests, comments, likes, follows, posts, profile changes, or similar externally visible engagement actions on behalf of users.
Heyou also does not use automated processing to make decisions that produce legal or similarly significant effects on individuals. AI-generated recommendations, relationship scores, summaries, and drafts are assistive outputs. Users remain responsible for reviewing, validating, editing, approving, and executing any action.
Control summary
This public overview is supported by a broader contractual and policy framework.
Master Services Agreement / Terms of Service governs commercial use of Heyou, including access rights, permitted use, customer responsibilities, confidentiality, data export and deletion, warranties, indemnities, liability, insurance, and order-form structure.
Data Processing Addendum governs Heyou’s processing of Customer Data where Heyou acts as a processor on behalf of the customer. It covers processing purposes, data categories, data-subject categories, subprocessors, international transfers, breach notification, audit rights, deletion and return obligations, and technical and organizational measures.
Privacy Policy explains Heyou’s public-facing privacy posture, including how Heyou organizes data, the distinction between organizational and personal tiers, sharing practices, international transfers, retention, data-subject rights, government requests, and automated-decisioning limits.
Supporting policies and schedules include the Responsible AI Policy, Acceptable Use Policy, Data Retention and Deletion Schedule, Cookie Policy, Subprocessor List, and Security Overview.
Where there is a conflict between this overview and a signed agreement, the signed agreement and applicable DPA control.
Heyou separates processed data into two primary tiers based on source, visibility, and control.
Organizational data includes professional relationship and business context that the customer or authorized users make available for use within the customer workspace.
Examples may include:
Organizational data is available within the customer tenant according to the customer’s internal permission model and Heyou’s role-based access controls.
Personal-tier data includes data an individual user explicitly chooses to connect from intrinsically personal or user-controlled resources.
Examples may include:
Personal-tier data is private by default. It is not visible to customer admins, managers, or other workspace users unless the individual user affirmatively chooses to share specific data with the organization.
For private messaging and similar sources, Heyou processes metadata only, such as participants, timestamps, interaction frequency, and other non-content signals needed to understand relationship context. Heyou does not ingest, store, or analyze the content of personal messages connected as personal-tier data.
A user may identify a person they want to reach who is not already present in the customer’s connected systems. In these cases, Heyou processes only the minimum information needed to surface a relevant relationship-path recommendation.
Heyou does not contact such individuals on the customer’s behalf. Any outreach is initiated by the user through the user’s own approved channels.
Heyou distinguishes between company-owned systems, customer-approved business sources, and user-authorized sources that an individual user may choose to connect, enable, export, upload, or contribute.
Heyou is designed around a clear separation of control:
Where user-authorized sources are enabled, Heyou’s access is view-limited and purpose-limited. Heyou reads the professional relationship context required to analyze the user’s network and provide relationship intelligence, subject to the customer’s tenant configuration, user authorization, lawful basis, and applicable product controls.
Heyou does not write back to third-party services or perform externally visible actions on behalf of users. Heyou does not automatically send messages, connection requests, comments, likes, follows, posts, profile changes, or similar engagement actions.
Heyou does not collect passwords, third-party platform credentials, or reusable third-party session tokens. Heyou does not bypass login, privacy settings, paywalls, technical access controls, restrictions, revocation signals, or customer disablement settings. Heyou does not continue source access after a user or customer disables that source.
Customer admins do not receive access to private user-controlled content unless the user has explicitly chosen to share specific data under the customer’s configured policy.
Customers can enable, limit, pause, or disable user-authorized source categories at the tenant level. Customers that prefer to avoid user-authorized external-source access can configure Heyou to operate using company-approved sources only.
Heyou is multi-source by design. No single user-authorized source is required for Heyou to operate. If a specific source is unavailable, disabled, restricted, or no longer appropriate for use, Heyou can continue operating using other customer-approved sources, such as CRM data, work email metadata, calendar metadata, meeting transcripts, approved business applications, native exports, and other authorized inputs.
Where a third-party service provides a user-facing notice, warning, restriction, or other indication related to source activity, Heyou does not control that notice or the service’s enforcement decisions. The user or customer can pause or disable the relevant source connection at any time.
Heyou is designed to minimize the amount of source information processed and retained by Heyou’s cloud systems. Where practical, source information may be transformed locally into normalized relationship signals and related metadata before being processed by Heyou.
Heyou’s goal is to generate relationship intelligence, not to store, reproduce, or redistribute third-party source content. Where relationship intelligence can be generated from metadata, derived signals, or locally transformed information, Heyou prefers those approaches. For private messaging and similar sources, Heyou processes metadata only and does not collect private conversation content.
Heyou does not collect or store the following as part of its standard service:
Heyou also does not source contact details from data brokers or third-party enrichment databases. When Heyou presents contact details, those details come from customer-authorized systems or user-authorized resources.
Heyou’s trust model includes strict limits on data reuse.
Heyou does not operate a shared contributor database, contact marketplace, or people-search product. Customer Data and User Data are not used to enrich a cross-customer contact directory. Heyou does not use one customer’s relationship graph, contact records, or user-authorized sources to generate recommendations, contact details, or relationship intelligence for another customer.
Heyou does not:
Customer data remains scoped to the customer or user context from which it was authorized.
Heyou is designed to give customers control over how the platform is deployed in their environment. Depending on product configuration and plan, customers may control:
These controls help customers align Heyou with their internal security, privacy, employment, and third-party service policies.
Heyou runs on Google Cloud Platform using managed cloud services and a tenant-isolated application design.
The current production architecture includes:
Customer data is logically isolated at the application, database, and object-storage layers. Personal-tier data is further scoped at the user level within a tenant.
Architecture and data-flow diagrams are available for enterprise security review.
Heyou maintains access-control and operational-security controls designed for enterprise environments.
Controls include:
Heyou uses AI to generate relationship summaries, recommendations, draft messages, and related assistive outputs. AI processing is governed by data minimization, tenant isolation, and human oversight.
Heyou uses Google Gemini via Vertex AI as its approved third-party generative AI provider. Heyou’s AI features operate against authorized customer or user context. They are not designed to give AI unrestricted access to the open web, user-owned accounts, or external services.
Controls include:
Heyou does not use Customer Data or User Data to train third-party generative AI foundation models.
Heyou may use Customer Data and derived relationship signals to improve proprietary non-generative relationship-scoring, classification, calibration, and path-ranking models, subject to the customer agreement and DPA.
This use is purpose-limited to improving the Services and is governed by tenant isolation, access controls, and data minimization safeguards. Heyou does not use Customer Data to build a cross-customer contact directory, people-search database, or resold data product.
Heyou’s default posture is customer-scoped model improvement: business-specific relationship intelligence is learned and applied within the customer or user context from which the data was authorized. Heyou does not use one customer’s business-specific relationship graph, messaging patterns, account strategy, outreach performance, sales motion, or GTM process to generate business-specific recommendations for another customer.
Heyou may derive aggregated, de-identified, or statistical insights to improve service reliability, safety, calibration, and quality, provided those insights cannot reasonably identify a customer, user, data subject, or customer-specific business process. Any broader use of Customer Data for cross-customer model improvement is subject to the customer agreement, DPA, and applicable Order Form restrictions. Enterprise customers may address customer-specific model-improvement restrictions or opt-outs in the Order Form or DPA.
Heyou maintains a security and privacy program aligned with enterprise customer requirements and relevant regulatory frameworks.
ISO/IEC 27001:2022** **Heyou Research and Development Ltd. is ISO/IEC 27001:2022 certified. SII Certificate No. 1127825 (ANAB-accredited), IQNET registration IL-1127825, valid 23 Apr 2026 → 23 Apr 2029. Download SII certificate · Download IQNET attestation. See the Certifications section for the full scope and verification instructions.
SOC 2 Type II. The SOC 2 Type II audit is in flight. The engagement letter with our auditor has been signed and the observation period is underway. Download the letter of intent. The final SOC 2 Type II report will be available under MNDA on completion.
Privacy and data protection laws** **Heyou’s privacy and security program is designed to support compliance with applicable privacy and data-protection obligations,.
Heyou uses a limited set of third-party subprocessors required to provide, operate, secure, support, and bill for the service.
| Subprocessor | Purpose | Typical Data Categories | Status |
|---|---|---|---|
| Google Cloud Platform / Vertex AI | Cloud hosting, infrastructure, storage, logging, monitoring, and approved AI processing through Vertex AI / Gemini | Customer Data, service metadata, logs, prompts and outputs where AI processing is used | Required for core service |
| Descope | Identity, authentication, SSO, user management, and access-control workflows | User account identifiers, authentication metadata, access-control metadata | Required for authentication |
| Customer.io | Customer communications, product notifications, lifecycle emails, and service-related messaging | Business contact information, product-notification metadata | Used for communications |
| Stripe | Billing, subscription management, invoicing, and payment-related workflows | Billing contact information, subscription and invoice metadata, payment-related records | Used for billing |
| Attio | CRM and customer relationship management | Business contact information, account records, sales notes, commercial relationship data | Business operations |
| Fathom | Meeting recording, transcription, call summaries, and meeting intelligence for customer or prospect interactions, where used | Meeting participant information, recordings, transcripts, summaries | Used where meetings are recorded or summarized |
Heyou does not use subprocessors to create cross-customer datasets or use one customer’s data to benefit another customer.
Subprocessors that process customer data or personal data on Heyou’s behalf are governed by contractual data protection obligations, including confidentiality, security, and breach-notification commitments. Heyou provides customers with advance notice of material subprocessor changes in accordance with the DPA.
User-authorized third-party platforms that a user chooses to connect are not subprocessors of Heyou. Those platforms operate the user’s account independently and are governed by the user’s direct relationship with the platform.
Heyou is designed around clear security boundaries: limited browser-extension permissions, tenant isolation, controlled AI processing, and strict limits on data reuse.
Extension supply-chain compromise** **Publisher and release risk is mitigated through restricted access, secure publishing procedures, code review, limited extension permissions, and Manifest V3 extension controls. The extension does not request high-risk permissions such as cookies, debugger, or broad request-interception permissions.
Credential or session exposure** **The extension is not designed to collect passwords, browser cookies, or reusable third-party session tokens. Activity occurs in the user’s active browser context, and Heyou’s backend does not receive credentials that would allow independent impersonation of the user.
Cross-tenant access** **Heyou applies tenant isolation across application, database, and object-storage layers. Internal access is role-based, logged, and limited to approved operational purposes.
Third-party AI data exposure** **Third-party AI processing is limited to approved providers. Heyou applies provider controls to prevent foundation-model training on customer data, uses region-aware processing where supported, and minimizes direct identifiers before model calls where identifiers are not required.
Improper data reuse or data-broker drift** **Heyou does not sell customer data, create shared contact databases across customers, or use one customer’s relationship data to benefit another customer.
Subprocessor exposure** **Heyou maintains a limited subprocessor list and requires contractual privacy and security commitments from subprocessors. Data shared with each subprocessor is limited to what is necessary for the applicable service purpose.
Subject to applicable law, individuals may have rights to access, correct, delete, port, restrict, or object to processing of their personal data. Where Heyou processes data as a processor on behalf of a customer, Heyou supports the customer in assessing and responding to those requests.
Heyou may maintain suppression mechanisms to help prevent re-introduction of individuals who validly object to processing or opt out, subject to applicable law and customer controller obligations. Where personal data remains in a customer source system, customers are responsible for removing or filtering the data at the source to prevent re-synchronization where required.
Heyou maintains an incident-response process designed to support timely investigation, escalation, customer notification, and regulatory coordination following a confirmed security incident involving customer data.
Where GDPR applies, Heyou supports notification without undue delay and, where applicable, within 72 hours of becoming aware of a qualifying personal data breach.
For incidents involving personal information subject to US state breach-notification laws, Heyou supports notification in the most expedient time possible and without unreasonable delay, consistent with applicable legal requirements, law-enforcement needs, and the time required to determine the scope of the incident and restore system integrity.
Heyou will notify affected customers without undue delay after confirming a security incident involving customer data. Notifications include available information reasonably needed to support the customer’s assessment, including the nature of the incident, affected data categories, impacted systems, containment actions, remediation steps, and recommended customer actions.
Customers are responsible for configuring and using Heyou in accordance with applicable law, internal policies, and applicable third-party service requirements.
Customer responsibilities include:
Heyou provides documentation and implementation guidance to support customer assessments, but customers remain responsible for their own compliance obligations.
For security review, vulnerability disclosure, or trust-center access:
These are the contractual and policy documents that back the trust posture above. NDA-gated artifacts (SOC 2 report, pen-test summary, signed DPA copies) are available on request through the trust desk at security@heyou.com.
Some artifacts stay behind an MNDA. Email the trust desk and we'll send them the same day during business hours.