Privacy Policy

This Privacy Policy explains how Podorax collects, uses, stores, shares, and protects information when people use our public website, main app, creator profiles, guest requests, responses, invitations, messaging, scheduling, reviews, notifications, saved items, availability settings, and published episode workflows.

Podorax is built to help podcast hosts and creators discover each other and coordinate collaborations. That means some information is intentionally public or visible to other users, while other information, such as private messages, account details, and internal moderation data, is handled with more limited access. We do not claim compliance certifications that we have not obtained.

We collect information you provide directly, information generated through your use of Podorax, information needed to operate accounts and collaboration workflows, and limited technical information from devices, browsers, and service providers. The specific information depends on which features you use.

Examples include your name, email, login method, profile photo, display name, country, topics, languages, biography, social links, availability information, guest requests, responses, invitations, messages, attachments, reviews, ratings, notification preferences, saved items, scheduling information, published episode links, and support or legal inquiries.

We may also collect operational records such as timestamps, read states, status changes, moderation actions, report history, email delivery state, and system-generated messages. These records help us preserve collaboration context, diagnose product issues, prevent abuse, and explain account or content decisions when support is requested.

When you register or sign in, we process account information such as your email address, authentication identifiers, name or display name, password reset status, and authentication metadata. Podorax currently uses Supabase for authentication, database services, and storage, so account authentication data may be processed through Supabase infrastructure.

We use account information to create and secure your account, verify sessions, route you through onboarding, prevent unauthorized access, support password resets, enforce role-based access, and connect your account to creator profile, request, response, invitation, messaging, scheduling, review, and notification features.

Creator profiles may include your display name, full name, profile photo, country, timezone, topics, languages, headline, biography, social or presence links, availability settings, profile completion score, reputation summaries, and published episode references. Public profile information may be visible to other authenticated users and may be used in discovery, search, recommendations, rankings, invitations, and request matching.

You control the accuracy of the information you add to your profile. You should not add information that you do not want other users to see if the field is public or discoverable. Podorax may use profile information to help hosts find guests, help creators evaluate opportunities, and improve marketplace quality.

Creator Content includes guest requests, responses, invitations, profile text, episode references, preparation notes, resource links, attachments, reviews, ratings, and other content you submit through product workflows. Some Creator Content is public or visible to other users, while other content is limited to specific conversation participants or account owners.

We process Creator Content to provide the service, display public pages, power discovery, support collaboration workflows, facilitate review and reputation features, investigate reports, enforce policies, and improve product quality. You are responsible for ensuring that content you provide is lawful, accurate, and appropriate for the audience that can view it.

Messages are used for conversations created after a host accepts a guest response. Messages may include text, system events, read receipts, typing indicators, attachments, preparation notes, questions, resources, and checklist items. Messages are intended to be visible only to the conversation participants and to Podorax personnel or systems when needed for support, safety, security, legal compliance, or product operations.

We do not treat messages as public profile content. However, users should avoid sending highly sensitive information through messaging unless necessary for the collaboration. If a conversation is reported or blocked, Podorax may review relevant conversation information to understand and address the issue.

Scheduling data may include availability windows, timezone, preferred recording duration, preferred platforms, proposed recording sessions, accepted or declined times, cancellation status, completion status, meeting platform, meeting link, meeting notes, and related system messages.

We use scheduling data to help participants coordinate recordings, show upcoming sessions, manage meeting details, send notifications, support episode lifecycle workflows, and provide dashboard summaries. Scheduling data may be visible to the participants in the relevant conversation and may be retained as part of collaboration history.

Podorax collects review and reputation data when users review completed collaborations or when marketplace statistics are calculated. This may include ratings, written review text, collaboration completion signals, published episode counts, moderation status, reports, and reputation summaries.

Review and reputation data helps users evaluate collaboration quality, supports marketplace ranking, and helps Podorax detect manipulation or abuse. Public reputation summaries may appear on creator profiles, request cards, dashboards, and discovery surfaces. Moderation data and reports are handled with more limited access.

Podorax creates in-app notifications for platform activity such as invitations, responses, accepted or declined responses, messages, recording proposals, meeting links, published episodes, reviews, and system updates. Notification records may include the recipient, type, title, message, entity reference, action URL, read state, and timestamps.

Notification preferences may indicate which categories of in-app or email notifications you want to receive. We use these preferences to decide whether to create or send certain notifications. Some account, security, or service messages may still be sent where necessary to operate or protect the service.

Podorax may send transactional emails, such as account, invitation, response, message, scheduling, review, or platform update emails. We use Resend for transactional email delivery. Email delivery records may include recipient email, subject, provider, provider message identifier, delivery status, error details, metadata, and timestamps.

You may be able to control some categories of email through notification preferences. We do not use transactional email settings to avoid sending messages that are necessary for account security, legal notices, or essential service operations.

We may collect usage information about how users interact with Podorax, such as pages visited, features used, search and filter activity, saved items, request views, profile discovery activity, notification interactions, message state, response status changes, scheduling actions, and review workflows.

Usage information helps us operate the service, diagnose issues, understand product adoption, improve discovery and recommendations, prevent abuse, prioritize roadmap decisions, and maintain marketplace quality. We may use aggregated or de-identified usage information for analytics, investor review, product planning, and trust review.

We may collect limited device and technical information such as IP address, browser type, device type, operating system, referring pages, timestamps, session information, and approximate country signals from trusted hosting or CDN headers when available.

This information is used for security, fraud prevention, debugging, analytics, localization, rate limiting, and operating the service. We do not request browser geolocation permission for normal account flows unless a feature clearly asks for it.

Podorax may use cookies, local storage, and similar technologies to keep users signed in, remember preferences, support theme selection, protect sessions, understand basic usage, and improve the website and app. Authentication and session cookies may be necessary for the service to function.

Marketing or analytics cookies, if introduced, should be described in the Cookie Policy and controlled through appropriate consent or preference tools where required. Browser settings may allow you to block or delete cookies, but doing so may affect authentication, saved preferences, or app functionality.

We use information to provide, secure, maintain, and improve Podorax. This includes authentication, onboarding, profile creation, discovery, recommendations, rankings, guest requests, responses, invitations, messaging, scheduling, episode preparation, reviews, notifications, saved items, support, moderation, abuse prevention, and product analytics.

We may also use information to personalize discovery, suggest relevant creators or requests, calculate profile completion, show reputation signals, route notifications, enforce policies, investigate reports, respond to legal requests, improve reliability, develop new features, and communicate with users about the service.

For example, topics and languages can help match creators with guest requests; country and timezone can support scheduling and location preferences; review and reputation signals can improve marketplace trust; and saved items can help users return to creators or requests they want to evaluate later.

We share information according to the visibility of the feature. Public creator profile information, public guest requests, published episode references, and public reputation summaries may be visible to other users. Responses are visible to the request owner. Invitations are visible to the sender and invited user. Messages and preparation workspaces are visible to conversation participants.

We may share information with service providers that help us operate Podorax, such as Supabase and Resend. We may also disclose information if required by law, to protect rights and safety, to investigate abuse, to enforce policies, during business transfers, or with your consent.

Podorax currently uses Supabase for authentication, database, realtime, and storage services. This means account data, profile information, app data, uploaded profile images, message attachments, and related records may be processed or stored through Supabase infrastructure.

Podorax uses Resend for transactional email delivery. If you receive an email from Podorax, delivery metadata may be processed by Resend. Podorax may also link to third-party podcast platforms, social platforms, recording tools, calendars, or websites supplied by users. Those third-party services are governed by their own terms and privacy practices.

We choose service providers to help operate specific parts of the platform, but we do not control third-party services that users link to or use outside Podorax. If you click a podcast, social, meeting, payment, calendar, or recording link supplied by another user, your use of that service is between you and that provider.

We retain information for as long as needed to provide Podorax, maintain accounts, support collaborations, comply with legal obligations, resolve disputes, enforce agreements, prevent fraud and abuse, secure the service, and maintain business records. Retention periods may vary by data type and feature.

For example, public profile and request information may remain while your account or content is active; messages may remain as part of conversation history; review and reputation data may remain to preserve marketplace trust; logs and backups may remain for limited operational periods; and email delivery records may remain for troubleshooting and compliance.

Retention decisions may also depend on whether a record is connected to a dispute, report, moderation review, security investigation, or completed collaboration.

You may request deletion of your Podorax account through available product controls or the Contact page. Account deletion may remove or deactivate your profile and limit access to your account data. Some information may be retained when necessary for legal, security, fraud prevention, dispute resolution, backup, audit, or legitimate business purposes.

Certain content may not be deleted immediately if it is part of another user's collaboration history, a completed review, a report investigation, a published public record, or a backup. Where appropriate, we may anonymize, de-identify, or restrict retained information instead of deleting it from all systems immediately.

Before requesting deletion, you should export or save any information you need for your own records, such as guest notes, preparation materials, messages, request details, or episode links. Podorax may not be able to recover account information after deletion or deactivation workflows are completed.

Depending on where you live, you may have rights to access, correct, delete, export, restrict, or object to certain uses of your personal information. You may also have the right to withdraw consent where processing is based on consent. European data protection guidance recognizes rights such as being informed, access, rectification, erasure, portability, restriction, and objection.

To exercise privacy rights, contact Podorax through the Contact page. We may need to verify your identity and may decline or limit a request where permitted by law, such as when retention is needed for security, legal compliance, fraud prevention, dispute resolution, or another user's rights. We will not discriminate against users for exercising applicable privacy rights.

We use administrative, technical, and organizational measures designed to protect information against unauthorized access, loss, misuse, and alteration. These measures may include authentication controls, service role isolation, frontend/backend separation for database writes, access limits, storage policies, logging, and review of security-sensitive workflows.

No online service can guarantee perfect security. You can help protect your account by using a strong password, keeping your email account secure, signing out of shared devices, watching for suspicious links, and contacting us if you believe your account or data has been compromised.

Podorax may be used by people in different countries. Information may be processed in countries other than where you live, depending on our infrastructure, service providers, and operational needs. Those countries may have data protection laws that differ from the laws in your location.

Where required, we will use appropriate safeguards for international transfers. If you access Podorax from outside the United States, you understand that your information may be processed in the United States or other locations where Podorax or its service providers operate.

Podorax is intended for professional podcast collaboration and is not directed to children. We do not knowingly collect personal information from children under the age required by applicable law. If you believe a child has provided personal information to Podorax, please contact us so we can review and take appropriate action.

Users should not create accounts for children, submit children's personal information, or use Podorax to solicit participation from minors without appropriate legal authority, consent, and safety review.

We may update this Privacy Policy as Podorax changes, including when we add features, change service providers, improve privacy controls, update retention practices, or respond to legal requirements. We will update the Last updated date and may provide additional notice for material changes.

Your continued use of Podorax after an updated Privacy Policy becomes effective means you acknowledge the updated practices. If you do not agree with the updated policy, you should stop using Podorax and may request account deletion subject to applicable retention rules.

Questions or requests about this Privacy Policy can be submitted through the Podorax Contact page. Please include enough detail for us to understand the request, identify the relevant account, and route it to the appropriate support, privacy, legal, or trust and safety workflow.

Because Podorax is still developing its public privacy operations, the Contact page is the preferred entry point for privacy requests until dedicated privacy contact channels are published.