Privacy

Scope

AFIE (Agentic Founder Intelligence Exchange) is a product of Augmentation Company (“AFIE,” “we,” “us”). This notice covers the AFIE website and information processed through enabled AFIE services. AFIE supports venture capital firms, founders and professional communities through messaging, permission-based knowledge access and consensual introductions.

Service access is invitation-only. Features and connections vary by workspace and release. The descriptions below apply when the relevant feature is enabled and used; listing a connection does not activate it or authorize access to an account. Public website access does not require connecting a third-party account.

Information we process

• Account and workspace information. Names, email addresses, phone numbers, firm or community affiliations, invitations, membership roles, verification records, connection identifiers and permissions. Authentication and connection systems also process credentials or tokens needed to maintain authorized access.
• Conversations and preferences. Messages sent to AFIE, responses, conversation history, saved personal context, communication preferences and feedback you provide. Messaging records may include sender and recipient identifiers, timestamps, delivery status, phone-linking records and consent or opt-out events.
• Knowledge and connected records. Information you submit or authorize AFIE to retrieve, including documents, extracted text, relevant excerpts and searchable representations of that text (“embeddings”). Sources may contain information about colleagues, contacts or other individuals. Access depends on source permissions and the workspace audience assigned to the information.
• Actions and introductions. Messages prepared for approval, selected recipients, meeting details, introduction requests and reasons, approvals, responses, action results and transaction or delivery references. These records support review, consent and reliable execution of requested actions.
• Technical and support information. IP addresses, requested URLs, browser information, timestamps, error and security events, service-usage measurements and correspondence. Usage records may include model identifiers, token counts and processing costs.

Information comes from you, your workspace or its authorized members, connected services you authorize, and interactions with AFIE. Provide only information you are entitled to use and disclose. Do not include passwords or access tokens in messages or support requests.

Connected services

Connecting an account authorizes the access described in its consent flow. Permissions can differ by provider and account. AFIE processes records within those permissions to answer requests or prepare and execute authorized actions.

• Google Calendar. Relevant event details may include titles, times, locations, attendees, recurrence and meeting links. Availability requests may use free/busy information for other calendars. Supported event creation, changes and cancellations require action approval. Google Meet links created through Calendar do not grant access to meeting recordings or transcripts.
• Gmail. The sending connection uses account identity, recipients, subjects and message bodies to send emails you approve and record the result. This connection does not request inbox-reading access. Follow-ups through this feature relate to messages initiated through AFIE.
• Slack. The connection uses member identity, user and channel information, and messages in a channel you request and can access. Approved messages may be sent to a channel or direct-message recipient. Connecting Slack does not authorize unrestricted access to every workspace conversation.
• HubSpot. Authorized CRM records may include contacts, companies and deals, including business contact details and associated record fields. Notes and tasks are created through supported actions after approval and subject to the connected member’s permissions.
• Community and company systems. Where a workspace enables a connection, AFIE may retrieve permitted profiles, founder or investor information, fundraising details, resources and request statuses, and submit approved introduction or support requests. The connected system determines the records and operations available to that member.

Additional permissions require the applicable authorization. Google user data use and transfer are subject to the Google API Services User Data Policy, including its Limited Use requirements, and applicable Google Workspace API requirements.

Purposes of processing

AFIE processes information to authenticate members, maintain workspace permissions, retrieve relevant knowledge, generate responses, personalize assistance, coordinate introductions, carry out approved actions and communicate service updates. Operational records support troubleshooting, security, abuse prevention, service evaluation, usage administration, request handling and applicable legal obligations.

Saved memory retains selected context for future assistance. It is separate from conversation history and from training a model. Deleting a conversation does not, by itself, delete saved memory.

No model training and zero data retention

AFIE does not use customer content to train or fine-tune AI models and does not permit its AI providers to do so. This commitment covers messages, connected-account data, documents, retrieved excerpts, saved memory and content derived from that information, including model inputs and outputs.

AFIE uses zero data retention arrangements for AI model and embedding processing. Under these arrangements, AI providers process customer content to fulfill the request and do not retain that content or the resulting output after processing. These protections apply to Google user data as well as other customer content supplied to AI providers.

Provider zero data retention is separate from AFIE’s storage of information needed to provide the service. AFIE retains conversation history, saved memory, knowledge records and operational records as described under Retention and deletion. The AI-provider commitment does not erase those records or copies held in connected services.

Service providers and other recipients

Information is processed by providers needed for the features you use, including hosting, databases, authentication, model processing, connection management, messaging and email delivery. The relevant service configuration determines which providers receive information.

• AI processing. The OpenAI integration processes prompts and relevant conversation, saved context or retrieved source excerpts to generate responses. Its embedding service may process text for knowledge retrieval. This processing is subject to the no-training and zero data retention commitments above.
• Authentication and connections. Supabase supports configured authentication and database services. Nango manages credentials, connection metadata and token refresh for connections that use it; those connections retrieve service content directly. Other supported connections use AFIE-managed credential storage.
• Messaging. Where text messaging is enabled through Linq, message content, addressing information and delivery events pass through that provider and the relevant messaging network. Emails and approved connector actions also pass to the selected provider and recipient.
• Workspaces and introductions. Workspace administrators manage memberships, roles, shared knowledge and connection status. Information assigned to a shared audience is available according to that audience’s permissions. Introduction requests disclose the requester’s identity and reason to the relevant recipient; internal contact exchange follows acceptance. External introductions also depend on the connected system’s consent process.

Authorized personnel may process information for support, security, administration or legal requirements. Information may be disclosed where legally required or necessary to protect rights and address fraud or security incidents. Sending information to an external recipient creates a copy subject to that recipient’s own practices.

Website storage, cookies and tracking

The public website does not set analytics or advertising cookies or include cross-site advertising tracking. Authenticated service sessions use cookies for sign-in and account-connection security. Browser storage may retain interface preferences and dismissed notices.

Local setup forms retain entered phone, firm, source references, notes, selected filenames and member email addresses in the tab’s session storage. Member lists are parsed on the device; these local forms do not upload selected files or connect accounts. An invitation submission sends its code to the website server for an access response.

The public website does not respond differently to Do Not Track signals. It does not sell personal information or share it for cross-context behavioral advertising through its website functionality. Applicable Global Privacy Control signals must be honored where required by law. External sites have their own privacy practices.

Retention and deletion

Retention depends on the information category, the service purpose, workspace settings and applicable legal or security requirements. Conversation history is subject to workspace retention settings. Saved memory remains separate until removed; knowledge records, connection records, approvals, delivery receipts and consent records have distinct lifecycles. Some audit and consent records may remain after membership ends.

Where available, service controls let members remove conversations, manage saved memory and disconnect accounts. Removing membership or disconnecting a provider does not necessarily erase all previously processed information, shared workspace records or copies held by recipients. Requests concerning retained records, logs and backups are assessed separately under applicable obligations.

Local setup data remains in the browser session until cleared or the session ends; browser restoration behavior may vary. See Delete data for local removal, connection revocation and deletion-request instructions.

Privacy requests and California residents

For access, correction or deletion requests, contact founders@theaugmentation.co with the subject “AFIE data request.” Identify the relevant account, workspace and requested action. Identity and authority may need to be verified before information is disclosed or changed. Do not send passwords, tokens or identification documents with an initial request. If your organization controls the relevant records, its participation may be required to address the request.

California’s online privacy-notice requirements are distinct from the California Consumer Privacy Act (CCPA). To the extent the CCPA applies, eligible residents may have rights to know and access personal information, correct inaccuracies, request deletion, opt out of sale or sharing, limit certain uses of sensitive personal information and exercise their rights without unlawful discrimination. Authorized agents may submit qualifying requests. These rights are subject to applicable conditions and exceptions.

Children, changes and contact

AFIE is intended for adult professional users and is not directed to children. Contact founders@theaugmentation.co if you believe a child has provided personal information.

Updates appear on this page with a revised date. Material changes require any additional notice or consent required by applicable law. Questions about this notice may be sent to founders@theaugmentation.co.