Skip to main content
Hybrid App Logo

Legal

Privacy Policy

Hybrid is a business workspace for independent workers. This policy explains what data we use, why we use it, and how users can control optional tracking, integrations, and privacy requests.

Effective Date

November 7, 2026

Submit privacy requestTermsCookies

Privacy requests are support-led

Submit a privacy request using the contact form and keep the case ID shown after submission. Support will review your request, verify your identity or authorization where needed, and explain any records we must keep. The form does not automatically change or delete your data. If you do not hear back, contact support with your case ID.

Hybrid runs on work context

We use account, client, project, invoice, proposal, payment, AI, and integration data to operate the workspace you ask Hybrid to run.

AI use and product improvement

Hybrid does not sell personal information or share it for cross-context behavioral advertising. Hybrid does not train its own foundation AI models. When you use an AI feature, Hybrid sends only the content that request needs, and only to AI providers that have agreed not to keep it or train on it.

You control optional tracking

Necessary storage keeps the product working. Optional analytics and attribution respect your cookie choice, Do Not Track, and Global Privacy Control signals.

Google data stays purpose-bound

Google Sign-In and Google Calendar access are used only for visible sign-in and calendar features, and can be disconnected.

AI stays approval-led

Hybrid can use scoped business context to draft or summarize, but consequential client, money, tax, legal, and payment actions still require human review.

Scope And Operator

This Privacy Policy explains how Hybrid.app handles personal information for visitors, account holders, clients who receive Hybrid-hosted documents, and people who connect third-party integrations.

Hybrid.app is operated by Xenium, LLC, 3343 Peachtree Rd NE Ste 145-2038, Atlanta, GA 30326. References to Hybrid, we, us, or our mean Xenium, LLC operating the Hybrid.app product and related services.

Questions or privacy requests can be sent to support@hybrid.app. If you use Hybrid for an organization, your organization may also control or restrict some workspace data and integration choices.

Data We Collect

Hybrid collects the information needed to provide a freelancer business workspace, secure the account, and support client-facing workflows.

  • Account and profile data, including name, email, avatar, username, authentication state, plan, preferences, and support history. Email/password sign-in and session handling are provided through Supabase Auth or another configured authentication provider; Hybrid does not store plaintext passwords.
  • Workspace data, including contacts, client records, projects, tasks, proposals, contracts, invoices, time entries, expenses, documents, notes, settings, and uploaded or generated content.
  • Data from documents and pages shared with clients, including hosted invoice, proposal, contract, public profile, booking, document-access, payment-status, and response metadata.
  • Hosted proposal response records, including accepted, declined, or requested-changes responses submitted on a secure link, response timestamps, recipient delivery or engagement metadata, and recipient-verification metadata where enabled.
  • Hosted contract response records, including typed-name responses submitted on a secure link, response timestamps, recipient delivery metadata, and technical metadata such as IP address and browser user agent when a recipient signs or declines a contract.
  • Payment and billing data, including Stripe customer, checkout, subscription, invoice, payment, connected-account, credit, add-on, tax, fee, and reconciliation identifiers. Hybrid does not store full card numbers.
  • AI and automation data, including prompts, messages, generated drafts, tool requests, approval records, usage events, model routing metadata, and the scoped business context needed to complete requested actions.
  • Storage usage and access metadata, including stored object size, quota usage, upload/download route events, signed-link activity, and related diagnostics used for security, support, abuse prevention, billing, and provider-cost monitoring.
  • Integration data, including provider connection state, provider account identifiers, provider connection tags, sync status, calendar event details, and other data the user authorizes Hybrid to access.
  • Device, log, security, analytics, attribution, and cookie data, including IP-derived coarse location, browser/device details, referrer and UTM data, error logs, audit records, and product usage events.
  • Communications data, including transactional email delivery, marketing consent, suppression records, bounce or complaint records, open and click events only where a tracked-send channel is enabled, inbound email and reply content where enabled, support requests, contact forms, and product feedback.

California Notice At Collection

This section summarizes the categories of personal information Hybrid collects and has collected in the preceding 12 months, why we collect them, how long we keep them, and whether they are sold or shared for cross-context behavioral advertising.

Hybrid collects personal information from the following categories of sources: directly from you, automatically from your devices and product usage, from clients and recipients who interact with hosted documents you send, from integrations and providers you authorize such as Google or Stripe, and from service providers that support security, payments, email delivery, and product operations.

Hybrid discloses these categories to service providers, contractors, processors, and integration providers for the business and operational purposes described in this policy. Hybrid does not sell personal information or share it for cross-context behavioral advertising.

Where sensitive personal information is collected, Hybrid uses it for expected service, security, payment, integration, support, compliance, and legal purposes. Hybrid does not use sensitive personal information to infer unrelated characteristics or for advertising.

Hybrid uses approximate location (city, region, or country from your profile or your connection) to localize features such as holidays, weather, news, and nearby search. Hybrid does not ask for precise device location and does not use location for advertising or unrelated profiling.

CategoryExamplesPurposeRetention PostureSold/Shared?
IdentifiersName, email address, account ID, username, authentication/session identifiers, support contact details.Account creation, authentication, support, security, personalization, and communications.Account life plus the period needed for legal, security, support, backup, and business-record needs.No.
Commercial recordsInvoices, subscriptions, credits, payments, connected-account identifiers, fees, refunds, disputes, and reconciliation records.Billing, checkout, payment workflows, accounting, tax, fraud prevention, dispute handling, and support.The legally or operationally required accounting, tax, dispute, fraud-prevention, provider-reconciliation, and legal period.No.
Professional or employment-related informationOccupation, professional intro, bio, skills, work availability, portfolio/profile fields, services, project history, and freelancer-business context you choose to provide.Profile setup, client trust, portfolio display, discovery, workspace personalization, support, and freelancer-business workflows.Account life plus the period needed for public-profile controls, legal, security, support, backup, and business-record needs.No.
Internet or activity dataIP-derived coarse location, browser/device data, cookies, referrers, UTM data, usage events, error logs, and audit records.Security, reliability, abuse prevention, optional analytics, attribution, product quality, and troubleshooting.Short operational periods unless needed longer for security, audit, fraud prevention, support, legal, or backup purposes.No.
Sensitive personal information and compliance-related dataAuthentication credentials handled by providers, payment-related identifiers, integration tokens, and tax and compliance data collected by payment providers.Authentication, account security, payment workflows, connected services, compliance, fraud prevention, and support.Limited to the applicable feature, provider, security, legal, compliance, and business-record need.No.
Integration and calendar dataGoogle account profile information, Google Calendar event fields, Google event links, connection metadata, Google API scopes, sync status, and webhook/error logs.User-authorized Google Sign-In, calendar context, scheduling-related workflows, integration support, connection health, and troubleshooting.Connection life plus limited logs, metadata, prior synced workspace records, and legal/security records as described in this policy.No.

How We Use Data

We use personal information to run Hybrid, make work records useful, protect accounts, and improve the product.

  • Provide, personalize, troubleshoot, and improve Hybrid features.
  • Authenticate users, manage sessions, prevent abuse, enforce rate limits, and investigate security events.
  • Create and deliver client-facing invoices, proposals, contracts, public profiles, payments, receipts, notifications, and workflow updates.
  • Record hosted proposal and agreement responses, notify the sender, preserve response records, recover interrupted response flows where possible, and prepare accepted-proposal follow-up documents or workspace setup without treating proposal acceptance alone as agreement acceptance, payment, or kickoff.
  • Process subscriptions, usage credits, add-ons, platform fees, payouts, failed-payment recovery, refunds, taxes, and billing support through Stripe and related service providers.
  • Power AI assistance you approve, draft generation, summaries, recommendations, and user-requested follow-up workflows.
  • Sync connected integrations such as Google Calendar when a user authorizes that connection.
  • Measure product usage, attribution, conversion paths, reliability, and feature quality using first-party telemetry and trusted service providers.
  • Comply with legal obligations, enforce our terms, protect rights and safety, and maintain business records.

Data Roles, Transfers, And Regional Rights

Hybrid's role depends on the data and workflow involved, especially when a freelancer uses Hybrid to manage client or recipient information.

For account, subscription, billing, security, analytics, support, product-improvement, and direct Hybrid relationship data, Xenium, LLC generally acts as the business or controller.

For client, recipient, project, proposal, invoice, contract, booking, and workspace data that a user enters or imports to run their own business, Hybrid generally acts as a service provider or processor for that user, while the user remains responsible for the notices, permissions, and lawful basis needed for their own clients and recipients.

For hosted-flow access logs, payment-status records, recipient-verification metadata, delivery or engagement records, and contract-signing metadata that Hybrid automatically collects to secure, operate, audit, support, or resolve disputes about hosted flows, Xenium, LLC may act as the business or controller for those operational records while also processing user-provided client and recipient content for the sender.

Where an organization needs a data processing agreement or similar privacy addendum for a supported business use, it can contact support. Hybrid may require identity, authority, and account verification before acting on organization-level privacy requests.

Hybrid is operated from the United States and uses providers that may process data in the United States and other countries. Where required, Hybrid relies on appropriate transfer safeguards, such as contractual commitments, data processing terms, standard contractual clauses, or other lawful transfer mechanisms. You can contact support to request more information about the transfer safeguards used for a specific service.

If Hybrid denies or limits a privacy request, you may contact support to ask for review. Eligible users may also have the right to complain to a local privacy regulator or supervisory authority.

Google Sign-In And Google Calendar

Hybrid uses Google data only when you choose Google Sign-In or connect Google Calendar.

For Google Sign-In, Hybrid may receive basic account information such as your email address, name, and profile image through our authentication provider so we can create or sign you into your Hybrid account.

For Google Calendar, Hybrid uses the authorized calendar connection to show calendar context in Hybrid and support scheduling-related product workflows. Current calendar event data used by Hybrid can include event title, description, status, start and end time, and the Google event link.

Hybrid may send integration connection details such as the Hybrid user ID, email, and display name to its integration provider so the connection can be created, supported, refreshed, validated, monitored, and disconnected. The Google consent screen shows the exact scopes before authorization.

For some OAuth integrations, Hybrid uses an integration provider to store authorized credentials, refresh access tokens while the connection remains active, validate connection health, and send webhook events back to Hybrid when access succeeds, fails, expires, or requires reconnection.

After a successful disconnect, Hybrid stops using the connection and removes or disables its stored credentials where supported. This does not delete your account or data at the connected provider. Some provider account identifiers, connection metadata, webhook logs, sync logs, error logs, and prior synced workspace records may remain where needed for security, audit, troubleshooting, billing, legal compliance, or to preserve workspace records you chose to keep.

You may also revoke access directly from the third-party provider's account settings. Provider-side revocation may stop Hybrid's future access even if Hybrid still keeps limited connection metadata, logs, or prior workspace records under this policy.

Hybrid does not use Google user data for advertising, does not sell Google user data, and does not transfer Google user data to data brokers or advertising platforms. Human access is limited to cases such as support you request, security investigation, abuse prevention, legal compliance, troubleshooting, and operating or maintaining the Google-connected feature you authorized.

Hybrid's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

  • You can disconnect Google Calendar inside Hybrid settings when available or revoke Hybrid's access from your Google Account permissions. Disconnecting or revoking access stops future authorized access, though connection metadata, logs, and prior synced records may remain where needed for security, support, audit, or legal retention.
  • If Hybrid needs to use Google data in a materially different way, we will update this policy and request any required consent before using that data for the new purpose.

AI And Automation

Hybrid AI features are designed to help users draft, summarize, organize, and act with approval, not to replace professional judgment.

Hybrid may route AI requests through Vercel AI Gateway and the AI, search, and media provider categories described in the When We Share Data section when a requested feature is configured to use them. Not every provider or provider category is active for every account or feature. The specific provider used may depend on the model, feature, availability, cost controls, and safety controls.

AI outputs can be incomplete or incorrect. Users are responsible for reviewing outputs before signing agreements, relying on financial or tax estimates, initiating payments, or taking other consequential actions. Some user-configured follow-up settings may send operational or client-facing communications, such as invoice or proposal follow-ups, when enabled by product settings and disclosures.

Hybrid does not use your account content, messages, files, or workspace data to train Hybrid-owned AI models unless you explicitly opt into a future training or evaluation program.

Hybrid only uses AI providers that have agreed not to keep your prompts or AI responses after answering and not to train on them. A provider may keep a request only where the law requires it or for limited safety and abuse checks. AI features that can't meet this standard stay turned off.

Hybrid does not use Google user data from Google APIs to train AI models, build unrelated AI products, serve advertising, retarget users, sell data, transfer data to data brokers, or make unrelated model-provider transfers. Hybrid does not send Google Calendar data or other Google API data to AI model providers by default. If you choose an AI feature that uses Google-connected calendar context, such as asking Hybrid to help prepare for a calendar item, Hybrid uses the minimum practical event context for that requested feature and only uses provider routes permitted by Google policy and your authorization.

Hybrid does not use raw payment identifiers, analytics identifiers, or unrelated private workspace records as AI context except where that data is necessary for the feature you requested or for operational support you initiate.

Hybrid may use authorized personnel review of existing usage, approval, outcome, reliability, and product-quality records to improve the service, but not to create hidden cross-user prompt context. Hybrid also keeps coded records of AI replies, actions and suggestions that didn't work out, never their text, and looks for patterns across accounts to find what to fix. Hybrid does not use raw prompts, client-message content, privacy requests, support complaint narratives, cancellation narratives, payment identifiers, tax identifiers, OAuth tokens, secrets, or Google API data for undisclosed product improvement, pricing or eligibility decisions, or unrelated AI training.

When Hybrid personnel discuss product feedback directly with you, summarized notes may inform product planning. Hybrid does not include identifying client, payment, or private workspace facts in those planning notes unless you separately authorize that exact use.

Some AI records may be stored by Hybrid as chat history, generated drafts, tool request logs, approval records, credit usage, delivery records, or audit/security logs. These records stay in Hybrid. AI providers don't keep a copy of your requests, apart from the legal and safety exceptions above.

When a chat gets too long, Hybrid may save a summary of its earlier messages for use in that chat. Summaries expire 90 days after they were last updated, and you can review or delete them in Settings > Preferences > Memory & context. Messages you send while saved memory is paused are never added to a summary.

Unless a reviewed product setting expressly says otherwise, Hybrid's AI assistance is approval-led for high-impact legal, tax, financial, payment, destructive, or money-movement actions. External communications may be automated only where the product setting and disclosure allow that workflow.

Hybrid does not make solely automated decisions about you that produce legal or similarly significant effects. If a future feature changes that, Hybrid will provide the required notice, human-review, and contest or correction path before that feature applies to you.

AI Data TypeSent To ProvidersStored By HybridUser Control
Prompts, messages, and selected workspace contextMay be sent when needed to produce the requested AI response or tool action.May be stored as chat history, generated content, tool context, or support/audit records depending on the feature.Use only the context needed for the request; contact support for access, export, correction, or deletion requests subject to retention limits.
Generated drafts and outputsMay be processed by model infrastructure as part of the requested generation.May be saved when users keep, send, approve, or attach the output to workspace records.Review before relying on or sending. Delete or edit product records where the product allows, or contact support.
Tool requests, approvals, usage, and credit eventsOnly the data needed for the selected model/tool route is sent.May be stored for billing, credit settlement, safety, audit, reliability, and abuse-prevention records.Subject to product settings and legal retention limits; consequential actions require approval unless expressly configured otherwise.
AI quality and product-improvement aggregatesNot sent as raw account content for hidden cross-user prompt context or model training.Coded records of AI replies, actions and suggestions that didn't work out, plus any amount at stake. Never message or reply text.Submit a privacy request to object to non-operational product-improvement use where applicable; operational, security, billing, audit, and legal records may still be retained.

Payments, Billing, And Money Workflows

Hybrid uses payment data to make invoicing, checkout, subscriptions, credit usage, and billing support work.

Stripe processes payment cards, checkout sessions, subscriptions, connected accounts, add-ons, and payment-related compliance. Hybrid stores Stripe identifiers, billing state, reconciliation records, plan and credit state, invoices, payment attempts, and settlement details needed to operate and support those features.

When users create Stripe connected accounts, manage payouts, or accept client payments through Stripe-powered flows, Stripe may collect identity, bank, tax, risk, dispute, and compliance information directly under Stripe's own terms and privacy policy.

When you provide personal data in connection with Stripe-powered payment or connected-account services, Stripe receives that personal data and processes it in accordance with Stripe's Privacy Policy.

Hybrid is not a bank, payment card network, custodian, exchange, investment adviser, tax preparer, or accounting firm, and does not provide escrow, buyer protection, chargeback insurance, or merchant of record coverage for client invoice payments. Optional crypto-native tools require user-controlled wallet authorization and may be unavailable in some jurisdictions.

Wallet, Blockchain, And Public-Ledger Data

Optional crypto-native features involve user-controlled wallets, third-party providers, public ledgers, and irreversible network behavior.

If you connect a wallet or use crypto-native tools, Hybrid may process wallet addresses, chain identifiers, transaction hashes, token symbols, balance or transaction metadata, gas-fee information, and provider connection metadata needed to show or support the feature.

Blockchain transactions and wallet activity may be public, permanent, irreversible, and visible to anyone through the relevant network or block explorer. Hybrid cannot delete or reverse public-chain records.

Hybrid does not custody wallet assets or guarantee wallet, smart-contract, bridge, swap, DeFi, escrow, or third-party protocol outcomes. Crypto-native features may be restricted, unavailable, or subject to additional compliance checks based on jurisdiction, sanctions, provider policy, or product status.

Escrow, dispute-resolution, token-reward, or smart-contract features are unavailable unless the product expressly presents them as launched for your account and jurisdiction.

Cookies, Analytics, And Attribution

Hybrid separates necessary product storage from optional analytics and attribution.

Necessary cookies and browser storage support sign-in, security, checkout returns, hosted document access, app state, and core product behavior.

If allowed, Hybrid uses Vercel Analytics and first-party telemetry to understand product usage, attribution, conversion paths, reliability, and feature quality. Optional telemetry is disabled when this browser rejects it, sends Do Not Track, sends Global Privacy Control, or when Hybrid environment settings disable it.

Optional telemetry choices do not turn off necessary service records for hosted invoice, proposal, contract, delivery, access, hosted-document open and response, payment, security, or audit workflows. Email open/click engagement is handled only as described in Email And Communications.

Email And Communications

Hybrid separates account, transactional, notification, lifecycle, and marketing messages.

Hybrid sends account and security email for authentication, login, password reset, email-change, and similar safety workflows; transactional money-path email for invoices, proposals, contracts, payments, billing, and support; notification and digest email for workspace updates; and marketing or newsletter email only through separate marketing controls. Lifecycle or product-education email for onboarding and feature guidance is a future or limited channel unless Hybrid exposes the required controls for that use.

Transactional and account/security messages are sent to provide, secure, or support the service and may continue even if marketing messages are disabled. Marketing and newsletter messages require a separate consent or unsubscribe path. Notification and digest messages follow the preferences available for those channels. Lifecycle and product-education messages require the relevant preference, unsubscribe, disclosure, or consent path before broad use.

Hybrid and its email providers process email address, sender and recipient metadata, subject, body content, templates, attachments where included, delivery events, bounces, complaints, and provider suppressions. Current public transactional email sends have open and click tracking disabled; Hybrid collects open/click engagement only for a channel when that tracked-send channel has been reviewed, enabled, and disclosed or consented to where required. Auth email delivery that runs through Supabase Auth custom SMTP is separate from Hybrid's in-app email log surfaces.

By default, email delivery and engagement records are used for operational purposes such as delivery troubleshooting, bounce and complaint suppression, abuse/security review, support, and message-performance diagnostics. Hybrid will not use open/click engagement for AI follow-up suggestions, lifecycle scoring, marketing analytics, or other non-operational analysis unless the relevant product setting, disclosure, or consent path allows that use.

Access to email records is limited to authorized people and service providers who need it for support, security, delivery or the other purposes described here. During scheduled cleanup, Hybrid removes stored message bodies from eligible delivery records once they are more than 90 days old and from eligible finished drafts once they are more than 30 days old, measured from when each record was created. Hosted proposal and contract documents are excluded. This cleanup does not delete message subjects, addresses, attachments, delivery records, suppression records or copies held by email providers.

Message TypePurposeControl
Account and securityAuthentication, login, password reset, email-change, security, and account-safety notices.Required for account operation; support can help investigate delivery issues.
Transactional money-pathInvoices, proposals, contracts, payment, billing, support, and related client-workflow messages.Required for the requested workflow; marketing unsubscribe does not disable these messages.
Notifications and digestsWorkspace alerts, summaries, reminders, and status updates based on product settings.Managed through notification, digest, quiet-hours, and channel preferences where available.
Lifecycle and product educationOnboarding, activation, feature guidance, winback, and service education.Requires the relevant lifecycle preference, unsubscribe, or objection path before broad use.
Marketing and newsletterPromotions, newsletters, launch updates, and other marketing communications.Can be unsubscribed from independently without disabling transactional product email.

When We Share Data

Hybrid shares data only when needed to provide the service, support a user-requested workflow, protect the platform, or meet legal and business obligations.

Hosted invoices, proposals, contracts, public profiles, booking pages, and client-workspace views can expose selected information to people who receive or access those links. Some access links are tokenized or time-limited, but forwarded links can still be seen by unintended recipients.

Hybrid does not sell or share personal information as those terms are defined by the CCPA/CPRA. Hybrid does not use Google user data for advertising, retargeting, personalized ads, credit-worthiness decisions, or lending decisions.

Hybrid may update service providers and subprocessors as the service changes. Material new processing categories will be reflected in this policy or a linked subprocessor notice before use where required.

  • Service providers and subprocessors, such as Supabase, Vercel, Stripe, Resend, Nango, Upstash, Reown/WalletConnect, Moralis, OpenStreetMap/Nominatim, Vercel AI Gateway and the AI model and web search providers it routes to, such as OpenAI and Anthropic, Sentry and other security, monitoring, and support providers.
  • People you intentionally interact with through Hybrid, such as clients, collaborators, recipients of hosted invoices, proposal recipients, contract recipients, public profile visitors, or payment counterparties.
  • Connected integration providers when you authorize Hybrid to send or receive data for that integration.
  • Legal, safety, and compliance recipients when disclosure is required by law, needed to protect rights or security, or necessary to enforce our terms.
  • Business transfer parties if Xenium, LLC is involved in a merger, acquisition, financing, restructuring, or sale of assets, subject to appropriate confidentiality and consent requirements where applicable.
Provider / GroupPurposeData CategoriesChange Notice
SupabaseAuthentication, database, storage, edge functions, and security policies.Account, workspace, client, hosted-artifact, security, and operational records.Provider changes that materially alter processing categories will be reflected in this policy or a linked notice where required.
VercelHosting, deployment, routing, reliability, and optional analytics.Device, log, routing, performance, cookie, and telemetry records.Provider changes that materially alter processing categories will be reflected in this policy or a linked notice where required.
StripeCheckout, subscriptions, Connect, payouts, tax, disputes, fraud, and compliance.Customer, connected-account, transaction, payout, dispute, tax, fee, and compliance records.Provider changes that materially alter processing categories will be reflected in this policy or a linked notice where required.
Resend and email providersAccount/security email via configured auth SMTP, transactional email, lifecycle or marketing email where enabled, inbound/reply handling, delivery events, bounces, complaints, suppression, and engagement tracking only where a tracked-send channel is enabled.Email addresses, sender and recipient metadata, subject, HTML/text body content, templates, attachments where included, inbound email content where enabled, auth-email delivery metadata, delivery events, open/click events only where a tracked-send channel is enabled, support, and suppression records.Provider changes that materially alter processing categories will be reflected in this policy or a linked notice where required.
Nango, Google, and integration providersAuthorized integration connection, token refresh, sync, disconnect, webhooks, and troubleshooting.Provider account identifiers, scopes, connection metadata, calendar fields where authorized, and sync logs.Provider changes that materially alter processing categories will be reflected in this policy or a linked notice where required.
AI, search, and media providersRequested AI, search, drafting, summarization, media, and tool-routing features.Prompts, selected workspace context, generated outputs, tool requests, usage, provider metadata, and available coarse city, region, or country as AI request context or when a requested search feature uses provider localization.Provider changes that materially alter processing categories will be reflected in this policy or a linked notice where required.
Wallet, blockchain, map, monitoring, and support providersOptional wallet/blockchain features, maps, error monitoring, security, and support.Wallet addresses, chain metadata, coarse location and map data where used, logs, errors, and support records.Provider changes that materially alter processing categories will be reflected in this policy or a linked notice where required.

Retention And Security

We keep data for as long as needed to run Hybrid, meet legal duties, resolve disputes, support users, and protect the service.

Retention periods vary by data type. Account and workspace records are generally kept while an account is active. Billing, tax, commercial, audit, abuse-prevention, security, and legal records may be retained longer where required or reasonably necessary.

Billing, payment, and tax records may be retained for the legally required accounting, tax, dispute, fraud-prevention, provider-reconciliation, and legal period, which may extend after account closure.

Some categories do not have a fixed public deletion deadline. The longest-lived exceptions can include billing, tax, payment, dispute, hosted-document audit, security, abuse-prevention, legal-hold, provider-reconciliation, backup, and fraud-prevention records.

When we close your account at your request, we turn off sign-in and delete your account data, except the records your clients or the law still need, such as invoices, proposals and contracts you sent and their payments, Hybrid's billing records, and security and privacy-request records. Those stay with a closed account that no one can sign in to.

Hybrid uses technical and organizational safeguards such as HTTPS, authentication controls, role-based access, database security policies, audit logging, provider security controls, encryption-supported infrastructure, and operational monitoring. Providers such as Supabase, Stripe, Vercel, and other subprocessors maintain their own security and compliance programs, but no online service can guarantee perfect security.

If we become aware of a security incident affecting personal information, we will investigate and provide notices where required by applicable law.

Data CategoryCurrent Retention Approach
Account and workspace recordsKept while the account is active. When we close it, we delete everything except records your clients, Hybrid's billing or the law still need, which stay with a closed account no one can sign in to.
Client, project, proposal, invoice, and contract recordsRetained while needed to provide the workspace and preserve accurate business records, unless deleted by the user where supported and legally allowed.
Payment, billing, tax, dispute, and reconciliation recordsRetained for the period reasonably needed for accounting, tax, dispute, fraud-prevention, provider, and legal obligations.
AI prompts, generated outputs, tool logs, approval records, and credit eventsRetained according to the feature, user controls, audit needs, billing needs, and legal retention limits.
AI quality and product-improvement aggregatesCoded records are deleted after 180 days, or sooner if you close your account.
OAuth connection records and tokensAfter a successful disconnect, Hybrid stops using the connection and removes or disables its stored credentials where supported. This does not delete your account or data at the connected provider.
Email delivery, engagement, and suppression recordsEligible message bodies are removed during scheduled cleanup after 90 days for delivery records and 30 days for finished drafts, measured from record creation. Hosted proposal and contract documents are excluded. Subjects, addresses, attachments, delivery records, suppression records and provider-held copies are reviewed separately for service, security and legal needs. Open and click tracking is disabled for current public transactional email.
Raw signed webhook delivery payloadsRetained for 30 days by default. An exact provider event may remain longer only under a documented legal, regulatory, dispute, privacy, or security hold. Derived business records follow their own retention periods.
Security, abuse-prevention, and audit logsRetained as long as reasonably needed to protect Hybrid, users, clients, providers, and the service.
BackupsDeleted on a delayed cycle according to backup and disaster-recovery operations.

Your Privacy Choices And Rights

Some privacy choices are available directly in-product. Rights requests without a current self-serve control are handled manually through Hybrid's support-led privacy request process.

  • Update account, profile, workspace, client, and billing information from Hybrid settings or the relevant part of Hybrid.
  • Manage optional analytics and cookies through Cookie settings on the Cookie Notice page or in Settings > Preferences > Optional analytics.
  • To object to product-improvement use of your data, submit a privacy request. Essential security, billing and service records are not affected.
  • If your browser sends a recognized opt-out preference signal such as Global Privacy Control, Hybrid treats that signal as a request to disable optional telemetry or sale/share-style processing where applicable. Hybrid does not currently sell or share personal information for cross-context behavioral advertising, but privacy controls remain available through Cookie settings and signed-in privacy preferences.
  • Disconnect integrations such as Google Calendar in Hybrid when available, and revoke access through the provider account.
  • Unsubscribe from marketing emails without disabling transactional product emails.
  • Manage notification, digest, lifecycle, marketing, read-receipt, and email-engagement preferences where Hybrid exposes those controls. If a self-serve control is unavailable, submit a privacy request to object to or request disablement of non-operational email engagement use; transactional delivery, suppression, audit, security, and legal records may still be retained.
  • Use the privacy request form to ask about access, correction, export, deletion or restrictions for AI memory, conversation summaries and other personal information. Support will explain which records can be changed or removed and which must remain.
  • Use the privacy request form to request access, correction, deletion, export, objection or restriction of personal information. The form records your request; it does not automatically fulfill it. Support may need to verify your identity or authorization. We will explain the response timing that applies, any permitted extension and any records we must retain. Requests involving signed webhook delivery evidence are reviewed under applicable privacy rights and retention obligations. The retention table describes the default 30-day storage period and documented holds.
  • Withdraw consent at any time for processing that is based on consent, such as optional telemetry, marketing email, or authorized integrations, without affecting processing that happened before the withdrawal.
  • Eligible California users may use the privacy request form to request access, deletion, correction, opt out of sale/share-style processing where applicable, limitation of sensitive personal information use where required, and non-discrimination for exercising privacy rights, subject to identity verification and legal retention limits.
  • If a request is submitted by someone acting on a user's behalf, Hybrid may require proof of authorization, account ownership, identity verification, and direct confirmation from the user where allowed by law before acting on the request.
  • California residents, residents of other U.S. states with comprehensive privacy laws, and EEA, UK, and Swiss users may have additional rights under applicable privacy laws.
  • Eligible users may appeal a denied privacy request by replying to Hybrid's decision or contacting support with the original request details.

Children And International Use

Hybrid is built for independent workers and is not directed to children.

Hybrid is intended for users who are at least 18 years old, or the age of majority in their jurisdiction if higher. We do not knowingly collect personal information from anyone below that age.

Hybrid is operated from the United States and uses service providers that may process data in the United States and other countries. Where required, we use appropriate safeguards for international transfers.

Changes And Contact

We may update this policy as Hybrid, applicable law, providers, or product controls change.

If changes are material, we will provide notice through the product, by email, or by another reasonable method. The updated policy will show a new effective date.

For privacy questions, data requests, or security concerns, contact support@hybrid.app. Legal notices may also be sent to Xenium, LLC, 3343 Peachtree Rd NE Ste 145-2038, Atlanta, GA 30326.