How Oho handles creator, customer, subscriber, and visitor data.

We collect information you provide when you create an account or use Oho, including your name, email address, username, profile details, photos, background assets, social links, creator page content, package listings, newsletter settings, scheduling settings, and collaboration settings.

We also collect transaction and workflow data created through the platform, including newsletter subscriber records, package purchases, buyer and brand contact details, booking requests, booking custom fields, meeting notes, collaboration briefs, delivery links, paid DM messages, payout requests, dispute records, and related operational metadata.

When you use the service, we collect technical and analytics data such as session identifiers, IP address and user-agent data associated with authentication or audit logs, cookie and local-storage identifiers, page paths, referrers, UTM parameters, browser and device details, and approximate country data inferred from network information.

Oho stores billing and payment workflow records such as checkout intent identifiers, subscription status, pricing, buyer name, buyer email, provider membership IDs, payout details, and refund status so we can operate subscriptions and creator transactions.

Payment card details are not stored directly in the Oho application codebase. Payment providers such as Stripe and Whop collect and process payment method details under their own terms and privacy practices.

We use personal information to operate, secure, and improve the service, to provide creator tools, and to complete the workflows you request.

• Authenticate accounts, maintain sessions, and protect against abuse or unauthorized access.
• Host public creator pages, manage packages, bookings, newsletters, collaborations, content modules, and paid DM inboxes.
• Process subscriptions, purchases, payouts, refunds, disputes, and other financial workflows.
• Send transactional email such as sign-in links, password resets, booking notices, DM updates, collaboration access codes, and newsletters.
• Measure traffic, attribution, engagement, conversion performance, and product usage.
• Support users, investigate issues, enforce platform rules, and comply with legal obligations.

Oho uses cookies and similar client-side storage to keep the service working and to understand how the product is used. This includes authentication cookies, a sidebar preference cookie, local-storage visitor identifiers, and local-storage attribution snapshots used to connect page visits and conversions.

Depending on the features enabled in the environment, Oho also uses analytics and measurement tools such as PostHog and DataFast, and may enrich limited network data with services such as IPinfo. These tools help us understand page views, conversion events, traffic sources, and product usage patterns.

You can control cookies and local storage through your browser or device settings, but disabling them may affect login state, attribution tracking, or parts of the product experience.

If you explicitly connect Google Calendar, Oho stores and refreshes the access credentials needed to read your calendar list, save your selected calendar, and create or cancel booking events on your behalf. We only use that connection to support scheduling features you enable.

If you upload files or media, Oho may use Supabase storage to create signed upload URLs, store assets, and serve public or private files, including digital product delivery assets where applicable.

Oho may also query third-party services to support creator workflows, such as analytics, payment, email delivery, or social follower count syncing.

We share information with service providers and subprocessors that help us run the platform, such as infrastructure and database providers, email delivery providers, payment processors, storage providers, analytics providers, calendar providers, and fraud or enrichment providers.

In practice, the codebase is configured to integrate with providers such as Google, Resend, Stripe, Whop, Supabase, PostHog, DataFast, IPinfo, and Sociavault depending on which features are enabled.

We also share information with other users when that is necessary to deliver the service. For example, creators receive buyer, subscriber, brand, booking, and DM information needed to fulfill an order or respond to an inquiry, and buyers or invitees may receive creator contact or meeting details needed to complete a transaction.

We may disclose information when required by law, to respond to valid legal process, to enforce our agreements, to protect the rights or safety of Oho, our users, or third parties, or in connection with a merger, acquisition, financing, or asset sale.

Creators use Oho to collect and manage audience, customer, subscriber, and brand information. If you are a creator, you are responsible for making any notices, consents, and disclosures required for the way you collect and use that information through your page, newsletter, booking flow, collaboration flow, or paid DM offering.

You must only upload, send, export, or use personal information through Oho in a way that is lawful and consistent with your own published policies and contractual commitments.

We retain information for as long as reasonably necessary to operate the service, maintain records, complete transactions, prevent fraud, resolve disputes, enforce agreements, and satisfy legal or tax obligations. Retention periods may differ depending on the account, transaction, message, audit, or billing record involved.

We use reasonable administrative, technical, and organizational safeguards designed to protect personal information. No method of transmission or storage is completely secure, so we cannot guarantee absolute security.

You can update some account and profile information directly inside the product, disconnect certain integrations, and unsubscribe from creator newsletters using the options provided in those messages where available.

Depending on where you live, you may have rights to request access to, correction of, deletion of, or portability for certain personal information, or to object to or limit certain processing. We will review and respond to verified requests as required by applicable law.

If you have a privacy question or would like to make a verified request, use the support or contact channel made available through Oho or on the Oho website.

Oho is not directed to children under 13, and we do not knowingly collect personal information from children under 13 through the platform. If you believe a child has provided personal information to Oho, contact us so we can investigate and take appropriate action.

We may update this Privacy Policy from time to time to reflect changes to the service, our processing practices, or legal requirements. When material changes are made, we may provide notice through the product, on the website, or by another reasonable method before the updated policy takes effect.