# Hamou Group Privacy Policy **Effective date: 17 November 2026. Version: 2026-11-17.** Service operator: Hamou Group, Israel. Website: https://hamougroup.com Privacy, support and legal contact: support@hamougroup.com This policy explains how Hamou Group ("Hamou", "we", "us") handles personal information through the Hamou app, website, event experiences and administration dashboard. It applies to members, speakers, organisers, workspace administrators and people who contact us. The service is intended for adults aged 18 and over, initially in Israel and Canada. ## Your privacy at a glance - Your account, professional context and event choices help us provide the service and introduce people in the context of events. - A match card can hide your direct identity before a mutual connection. This is not anonymity from Hamou or authorised administrators, and details you share may still identify you. - Ordinary dashboard reporting shows conversation activity, not private-message text. Reporting a message shares the selected evidence with authorised safety reviewers. - Speaker feedback is linked to your account in our systems. Ordinary organiser feedback reports do not include your account identity or email, but what you write may identify you. - We use service providers, including Supabase and Vercel. Information may be processed outside Israel and Canada, including in the United States. - You can manage available profile and notification settings, request access or correction, and request deletion. Some records and independently held copies may require separate handling. - Enabled dashboard AI tools can send submitted documents and relevant workspace context to OpenAI. Voice, new AI uses and paid features require the information and choices described below before they are enabled. ## 1. Who is responsible Hamou Group is responsible for the purposes and means of handling personal information for its own accounts, networking service, platform administration, security and support. Contact our privacy team at support@hamougroup.com with questions, requests or complaints. This is also our contact for notices concerning these services. An independent event organiser, employer, course provider or other organisation may separately decide how to use information for its own activities. Its notice applies to that separate processing. Where Hamou handles information solely on an organisation's documented instructions, the applicable service agreement must identify that relationship. This policy does not remove Hamou's own responsibilities or give organisers unrestricted access to member information. ## 2. Information we collect and where it comes from ### Account and sign-in information We process information used to create and secure your account, such as your name, email address, account identifier, sign-in method, verification and recovery records, session information, and account settings. Our authentication service processes passwords and other authentication credentials. Do not send your password to support or an organiser. When a supported external sign-in method is available and you choose it, the provider supplies the identity information authorised in its consent screen. Basic Google sign-in is intended to provide an account identifier, name, email address and profile picture. It does not grant Hamou access to Gmail, Google Drive, your calendar or your contacts. ### Profile and professional context We process the information you enter or deliberately import, including your photograph, city, professional category, goals, interests, expertise and other profile fields available to you. Optional fields may include your company, role, education, professional history, contact details, website, LinkedIn profile and documents you choose to share. Connecting an identity provider does not automatically give Hamou a complete employment or education history. If a professional-history import is offered, we identify its source and allow you to review the imported information before saving it. Do not upload another person's private information or confidential business material without authority to do so. ### Events, recommendations and connections We process event registrations, registration cancellations, waitlist entries and offers, event and session identifiers, matching choices, connection status and associated timestamps. We also process the profile information used to determine participation eligibility or display a recommendation. Where a feature derives interests, relevance indicators or suggested connections from your information, those inferences are information about you too. A suggestion is not a verified fact about you or the other person. ### Messages, feedback and safety reports We store the messages you send through Hamou, their participants, associated connections or events, timestamps and delivery or read information supported by the feature. We process speaker ratings, written feedback and their session and event context. If you report someone, we process your report, its reason, any details you provide, the message evidence you select, and the resulting review or enforcement records. Blocks and other safety choices are also recorded. ### Organiser and administrator information We process event and speaker information supplied by organisers; administrator invitations, access roles and actions; shared tasks, assignments and comments; audience selections for notifications; and operational reports. These records may contain information about members, invitees, speakers or other people supplied by an authorised administrator. A speaker profile can exist before that speaker creates a member account. Its source may be the organiser or the speaker rather than an account registration. If a listing concerns you, you can ask us about its source and request correction or removal, subject to applicable law. ### Support, website and technical information We process information you send to support@hamougroup.com or through an available contact form, together with the context needed to answer you. An enquiry can include your name, email address, optional company, selected topic and message. Form protection may use a request identifier and a hashed IP address to limit repeated or abusive submissions. A hashed identifier is not necessarily anonymous. Sending an enquiry does not subscribe you to marketing. Our systems and providers may process IP addresses, browser and device information, request times, security events, errors and service logs to deliver and protect the service. The website may display illustrative product demonstrations. Interacting with a demonstration does not by itself create an account, register you for an event or submit its illustrative content as your own. We use a city or other location information you provide where the feature calls for it. Opening an event address in a maps service is different from granting Hamou continuous access to your device location. Features that need additional device permissions must request them separately. ## 3. Why we use information We use information for the following purposes, to the extent relevant to the features you use: - **Accounts and security:** authenticate you, maintain sessions, recover accounts, verify sensitive changes, prevent unauthorised access and respond to abuse. - **Profiles and networking:** maintain your professional context, determine event eligibility, display appropriate match information, record your choices and enable mutual connections. - **Events:** administer registrations and waiting lists, deliver event information, communicate material changes or cancellations, and provide agenda and speaker experiences. - **Communication:** deliver member messages, maintain conversation state, and provide the notification categories you select where available. - **Feedback and reporting:** receive speaker ratings and comments, prepare organiser reports, and measure event participation and connection activity. - **Workspace administration:** manage authorised staff, invitations, assignments, shared tasks and operational reporting. - **Support and reliability:** answer requests, diagnose failures, investigate incidents and assess whether service functions work as intended. - **Legal responsibilities:** respond to valid legal requests, maintain records required by law and establish or defend legal claims. We do not treat these purposes as permission for unrelated advertising, unrestricted profile enrichment or a new AI use. A materially different use requires an appropriate legal basis and any additional notice or consent required by law. Providing information is voluntary unless we identify a specific legal requirement. Some information is necessary to provide a requested feature: without account credentials we cannot maintain an account; without registration details we cannot register you; and without message content we cannot deliver your message. Optional profile fields are not a condition of unrelated services. Less context can make suggestions less useful. This policy is a notice, not blanket consent. We obtain consent where required and rely on a legal exception only where it actually applies. You can ask us to explain the basis for a particular use. ## 4. Who can see your information ### Other members Before a mutual connection, an anonymous matching view limits direct identifiers such as your name and photograph. It can still show professional context relevant to a potential introduction. A distinctive role, experience or goal can make you recognisable. Information you publish elsewhere, including a speaker biography, is not made anonymous by this feature. After both people choose to connect, the feature reveals the profile information intended for that connection, such as name, photograph, professional details and available profile links. Information you voluntarily send in a message is visible to its recipient. Connecting is not permission to copy, sell or use another person's information for unrelated purposes. ### Authorised dashboard users Authorised Hamou workspace administrators can access the member and event information made available through the dashboard, including completed profiles, contact details, onboarding information, registrations, matching and connection activity, and operational reports. Attendee exports can include names, email addresses and contact numbers where supplied. This access is broader than another member's view and is not limited by whether an administrator personally matches with you. Do not assume that each organiser has a technically isolated view of only one event. Administrators must use this information only for authorised, disclosed purposes. Conversation activity reports can identify participants, the associated event or connection, message counts and activity times. They do not provide ordinary administrators with a transcript of your private chat. ### Private messages and safety review Private messages are stored on the service; they are not end-to-end encrypted. The normal messaging interface limits message content to the participants. Restricted technical access may be necessary to operate the service, respond to an incident or comply with law. It is not a general entitlement for staff to read conversations. When you submit a report containing a selected message, dashboard administrators authorised to handle reports receive that evidence and the report details. The current dashboard uses administrator access for this review, rather than a separate safety-only role. This does not automatically provide the rest of the conversation. A recipient may independently copy or disclose information you sent, and a legal request may require disclosure beyond an in-app report. ### Feedback and event reports Organisers can review speaker ratings and comments and export the reports available to them. Ordinary feedback reports omit the reviewer's account identity and email. Feedback is nevertheless associated with your registration in our systems for access control, updating and deletion. Do not include identifying details in a comment if you do not want its reader to infer who wrote it. An exported report becomes a separate copy controlled by its recipient. We cannot guarantee that withdrawing feedback from Hamou will erase a copy already downloaded by an organiser. Applicable privacy obligations still apply to that recipient. ### Service providers and external services We use providers to deliver hosting, authentication, database storage, communications, security and other specifically enabled functions. The app uses Supabase for authentication and data services and Vercel for hosting. Our marketing website is published through OpenAI Sites on Cloudflare infrastructure. Email services process correspondence you send to our support address. Providers receive information necessary for their role, subject to applicable arrangements and law. Website hosting through OpenAI does not mean that your app profile or private messages are automatically submitted to an AI model. External sign-in providers, maps services, linked websites and externally hosted images may receive connection information when you use or load their services. Their own notices govern processing they undertake independently. A link is not an endorsement, and an external service does not receive unrestricted access to your Hamou account. ### Legal requests and business transfers We may disclose information where legally required or otherwise permitted by law to protect safety, investigate unlawful activity or establish or defend rights. We assess the request and limit disclosure as appropriate. If a reorganisation, acquisition or transfer of the service involves personal information, disclosure must be limited to the transaction's lawful purposes and protected appropriately. A change of ownership is not permission to disregard this policy. We provide notice and obtain additional consent where required. ## 5. Matching, AI and future features Matching uses information available to the relevant feature and your participation choices. A recommendation does not create a connection without the required mutual choice, certify a person's credentials, or determine employment, admission, credit or investment eligibility on your behalf. The member app's current context interview and Copilot interactions do not capture microphone audio or send those interactions to an external AI model. Animated listening or thinking states do not mean that a recording is being made. Availability and data use can differ between the member app and administrator tools. Where configured and used, the dashboard's AI Consultant sends the administrator's request, conversation history, relevant workspace member and event context, and requested tool results to OpenAI to generate a response. AI agenda import can send the uploaded document, including its text or file contents, and relevant event and speaker context to OpenAI to propose an agenda. Administrators should supply only information they are authorised to use for the stated task, avoid unnecessary sensitive information, and review outputs before publishing or acting on them. These provider requests are configured not to store a retrievable response through the response-storage setting. That setting does not guarantee zero provider retention or remove security, abuse-monitoring or other processing that may apply under the provider arrangement. Contact support@hamougroup.com for information about a particular enabled AI workflow. Before enabling a feature that processes audio, presentation material, company context or other information through AI, we will identify the information used, its purpose, the relevant providers or recipients, retention arrangements and available controls. Required consent and device permissions must be obtained before the processing starts. Users must not record or upload other people's speech or confidential material without the necessary rights and permissions. Accepting the Terms does not authorise the use of private messages, voice recordings, company documents or personal context to train a general-purpose AI model. Any proposed training or other materially different use requires a separate assessment, clear disclosure and any legally required choice. Do not assume a particular AI provider or zero-retention arrangement until the feature notice identifies it. ## 6. Notifications and marketing choices Available notification settings let you control categories such as messages, connections, event reminders, event changes and member updates. We also send communications necessary for account security, verification or a service you request. Promotional messages require the permission or other lawful basis applicable to the message and recipient. Joining an event, connecting with another member or leaving a general notification toggle enabled is not unlimited consent to marketing. Where we send marketing, we identify the sender and provide the legally required way to unsubscribe. Withdrawing marketing consent does not prevent essential non-promotional account communications. The current account app provides in-app notifications; device push delivery is not connected. If device notifications are enabled later, they will require your browser or device permission and a supported delivery service. Enabling them can process a subscription endpoint, delivery keys, browser information and notification content. You can change available notification categories in the app and revoke permission in your device or browser settings. An in-app notification inbox does not by itself enable device alerts. Lock-screen previews may expose content to anyone with access to your device. ## 7. Cookies and device storage The service uses cookies or similar device storage for authentication, security, preferences, drafts and continuity between screens. Some interface state and saved work can be held in local or session storage on your device. Removing essential storage can sign you out, discard local work or prevent features from working. Signing out or deleting an account does not necessarily clear every browser-stored item on every device; use your browser's site-data controls on shared devices. Optional analytics, advertising technologies or cross-service tracking require a separate inventory and the notice and consent controls applicable to them before activation. This policy does not grant permission for undisclosed trackers. Any sale of personal information or disclosure for third-party targeted advertising would require a separate legal assessment and appropriate notices and choices; it is not authorised by these Terms or this policy. ## 8. Processing outside your country Hamou operates from Israel. Information may also be processed in the United States and other countries where an identified provider operates. The currently configured Supabase project uses a United States region. This does not mean all logs, support access or other provider processing occur in that same region. Foreign privacy laws and government-access powers may differ from those in your country. Overseas processing can make information subject to lawful access by authorities in that country. We remain responsible for the protections required of us and must use appropriate contractual, organisational and technical safeguards for service-provider processing. You can ask our privacy contact for information about relevant providers and safeguards. ## 9. Retention and account deletion We retain information for the purpose for which it was collected and for any further period lawfully necessary for a specific obligation or claim. Retention is assessed by category, not by treating every account record as permanent. Account and profile information supports your active account. Registrations, matching choices, connections, messages and feedback support the associated member and event functions. We assess retention using the duration of your account or relationship, the purpose and sensitivity of the record, pending support or safety issues, applicable legal requirements, and the need to establish or defend a claim. Enquiries are kept as needed to answer and follow up on them and meet any applicable recordkeeping obligation. We do not apply a single fixed retention period to all categories. Backups, service logs, exported reports and files can have different lifecycles from the active database. Expiry depends on the applicable provider configuration and purpose. We do not promise immediate erasure of every backup or independently held copy. Contact support@hamougroup.com for information about the retention applicable to your data or to request deletion; where information must be retained, we will explain the reason, subject to lawful restrictions, and limit further use to that purpose. You can use the account deletion controls available in Settings or contact support@hamougroup.com. We may need proportionate identity verification to prevent someone else deleting your account. The current self-service flow asks for your password; if you use Google without a Hamou password, contact us for assistance. A sole workspace owner may need to transfer ownership, and some stored files may require assisted removal. If an in-app restriction prevents you from completing a lawful deletion request, contact us; it does not remove your legal rights. Deleting an account is different from signing out, uninstalling the app, cancelling one event registration or blocking someone. Account deletion removes the account and associated records according to their relationships in the service. A published speaker profile supplied separately by an organiser may remain after its link to the account is removed; you may request separate review of that content. We cannot erase copies already kept independently by message recipients, organisers or external services through an account deletion alone. Backups and records subject to a valid retention obligation may also require separate handling. Such retained information must not become a source for unrelated ongoing use. We will explain applicable limitations when responding to a request rather than promise that every copy disappears immediately. ## 10. Security We use access controls, authentication safeguards and service-provider protections intended to reduce unauthorised access, loss and misuse. Access should be limited to people and systems with a legitimate operational need. No internet service or storage system can guarantee absolute security. Use a strong password, protect your devices, do not share verification codes and tell us promptly if you suspect misuse. If a security incident affects personal information, we will investigate and notify the relevant authorities and affected people where required by applicable law. ## 11. Your requests and rights Depending on applicable law, you may request access to personal information we hold about you, information about its source and use, correction of inaccurate or incomplete information, withdrawal of consent, deletion, or other available restrictions. We will facilitate a portable copy where a right to portability applies. These rights have legal limits and are not identical in every jurisdiction. You can make a request at support@hamougroup.com. Tell us enough to locate the relevant account or information, but do not send a password, payment details or unnecessary identification documents. We may request proportionate verification. If you act for someone else, we may need evidence of your authority. We respond within the period required by the law applicable to your request. Where PIPEDA applies to an access request, the ordinary response period is 30 days, subject to permitted extensions and notice. If an exception limits access or deletion, we will explain the basis and available next steps, subject to lawful restrictions. Access must also respect other people's privacy. Withdrawing consent may prevent a feature from continuing where that information is necessary. It does not invalidate lawful processing already completed or require deletion of information that must lawfully be retained. We will explain the practical consequences relevant to your request. You may raise a concern directly with us and may also contact the competent regulator. In Israel, this includes the Privacy Protection Authority. In Canada, it may be the Office of the Privacy Commissioner of Canada or the relevant provincial privacy authority. You do not have to waive regulatory or court remedies to use our complaints process. ## 12. Adults only Hamou is not intended for people under 18, and they must not create accounts. If we learn that an account belongs to someone under 18, we will assess the information, restrict the account as appropriate and address deletion or any lawful retention requirement. Contact support@hamougroup.com if you believe a child has provided information to us. Local rules about legal capacity may require an older age for entering a contract. ## 13. Changes to this policy We will publish the effective date of an updated policy and give appropriate notice of material changes. Where a change requires consent, we will obtain it before applying the new use. Continuing to use the service is not blanket consent to a new purpose, sensitive processing or previously undisclosed sharing. The current policy is available at https://hamougroup.com/privacy and in the Hamou app under Settings, Privacy and terms. Contact support@hamougroup.com for an accessible copy or help understanding a particular practice.