This Privacy Policy explains how Blipside, Inc. (Blipside, we, us, or our) collects, uses, discloses, retains, and protects personal information when you use Blipside websites, the Blipside Listener application, Blipside Voices, accounts, live sessions, support and safety features, and other services that link to this Policy (collectively, the Service).
This Policy is a privacy notice. It is not bundled into the checkbox used to accept the Terms of Use or Creator Terms.
1. Scope and controller
Blipside, Inc. is the controller or business responsible for the personal information described in this Policy, except where another company independently determines how it processes information under its own terms.
At launch, Blipside is offered and marketed for use in the United States. The Service and its providers may process information in the United States. If you access the Service from another location, applicable law may give you additional rights.
Listener and Creator identities are separate account roles even when they use the same email address. Some Creator information is intentionally public to Listeners. Listener account information and preferences are generally private unless the Service clearly indicates otherwise.
2. Information we collect
Account and authentication information
We collect information needed to create, verify, authenticate, secure, recover, and administer accounts, including:
- email address and canonicalized email;
- password-derived hash and salt, but not your plain-text password;
- account identifier, role, status, and timestamps;
- verification and recovery challenges and their status;
- authenticated-session, revocation, and expiration information;
- linked identity-provider information if you choose a provider that Blipside has enabled; and
- security and authentication audit information.
Verification and recovery codes ordinarily expire after 15 minutes.
Eligibility and legal records
When the eligibility and policy system is active, we collect the age range or age-class source used to determine account eligibility. We do not collect a full date of birth for ordinary Blipside eligibility.
We also collect records showing which legal document and presentation versions were shown to an account, the account role, the action taken, the time of the action, and cryptographic digests or other evidence needed to preserve the exact version.
Listener profile and preferences
We collect Listener account and preference information such as:
- optional display name;
- languages the Listener wants to hear;
- followed Voices and teams;
- blocked or muted Voices;
- Voice Type, Voice Style, league, team, topic, and discovery preferences where available;
- privacy, interface, and personalization choices; and
- account-backed settings and relationship data.
Some playback, appearance, cache, diagnostic, and device-specific settings remain only on the device.
Creator profile and session information
We collect information Creators provide or generate through Blipside Voices, including:
- public display name, avatar, biography, and public Voice profile;
- Voice Types, Voice Styles, languages, leagues, teams, topics, and coverage interests;
- session titles, descriptions, game or topic context, language, tags, schedule, status, and related metadata;
- drafts, scheduled sessions, live-session state, completed-session history, recaps, and analytics; and
- Creator account-support and enforcement information.
Creator profile and session information may be displayed to Listeners. A language label is a Creator declaration about the main language listeners should expect; Blipside does not verify fluency or translate the session.
When public-profile filtering is active, Blipside processes proposed public display names, biographies, session titles, and normalized avatar images to identify potentially objectionable material before publication. This preventive review is separate from live audio and does not turn Listener report volume into automatic session termination.
Live audio
Blipside processes Creator microphone audio to provide live sessions. The current Service does not offer a feature that intentionally records, archives, replays, downloads, clips, transcribes, translates, dubs, clones, or trains generative-AI models on Creator live audio.
Live audio is nevertheless received, encoded or transcoded, transmitted, and temporarily buffered or cached as technically necessary to deliver the stream. Transient playlist or segment data and Listener device or network buffers may exist for a limited period under ordinary media-system operation. Blipside cannot withdraw audio bytes that have already been delivered to a Listener's device or network buffer.
Current reports and session recaps do not contain a stored audio excerpt or transcript. If Blipside later introduces recording, replay, clipping, transcription, translation, evidence clips, or another new audio use, Blipside will update this Policy and obtain any additional rights or consent required before using the feature.
Activity, device, network, and diagnostic information
We collect or generate information about use and operation of the Service, which may include:
- searches and discovery activity;
- session views, joins, listening activity, following, blocking, reporting, Voice switching, and playback events;
- app, browser, device, and operating-system information;
- IP address and network information processed by infrastructure and security systems;
- error, performance, reliability, and security diagnostics;
- logs, telemetry, release information, and opaque identifiers; and
- product-interaction information used for functionality, analytics, personalization, debugging, and abuse prevention.
Blipside uses redaction and minimization controls where practical, but operational data should not be assumed to be anonymous in every circumstance.
Reports, moderation, support, and legal requests
We collect information submitted or created in connection with:
- reports and report categories;
- Voice, session, account, or content context;
- descriptions and diagnostic attachments;
- review status, operator notes, decisions, and audit history;
- blocking and enforcement actions;
- support, privacy, security, and copyright communications;
- account warnings, restrictions, session intervention, and review requests; and
- legal, law-enforcement, or safety requests.
The identity of a person who reports content is not intended to be public. Blipside may provide an appropriate explanation of an outcome without exposing reporters, confidential evidence, or information that would create additional risk.
Information from third parties
We may receive information from:
- app stores and operating-system providers;
- authentication or identity providers that you choose to use;
- cloud hosting, media, email, content-safety, security, and error-monitoring providers;
- sports-data and event-information providers;
- a person who reports or contacts us about your account or content; and
- services you intentionally connect to Blipside.
The information we receive depends on the service and its settings.
3. How we use information
We use personal information to:
- create, verify, authenticate, recover, and administer accounts;
- determine account eligibility and preserve policy presentation and acceptance evidence;
- provide Creator profiles, live audio, schedules, session context, discovery, playback, language preferences, following, blocking, reporting, recaps, and analytics;
- personalize and filter the Service based on saved preferences;
- communicate verification, recovery, password, account, safety, operational, and legal notices;
- provide support and respond to privacy, security, copyright, and legal requests;
- evaluate proposed public profile text and avatar images when preventive content-safety filtering is active;
- monitor reliability, diagnose errors, secure the Service, prevent fraud and abuse, and enforce agreements;
- investigate reports, protect people, preserve evidence, and respond to legal obligations;
- measure product performance and improve features, without using Creator audio for generative-AI or synthetic-voice training under the standard Creator license;
- establish, exercise, or defend legal claims; and
- complete a merger, financing, reorganization, acquisition, or sale subject to appropriate safeguards.
4. What is public
Creator profile and session information may be public within the Service, including a Creator's display name, avatar, biography, Voice attributes, languages, coverage interests, schedule, session title, context, live status, and other information the Creator chooses or is told will be public.
Listener email, password-derived material, authentication information, private preferences, account status, report identity, and private relationship choices are not intended to be public.
Blocking and preference choices are private controls. Reports, protected notes, security records, and internal moderation information are restricted to authorized use, subject to law and the need to explain or review an action appropriately.
5. How we disclose information
We disclose information in the following circumstances.
Service providers
We use service providers to perform hosting, databases, live-media processing, content delivery, transactional email, support email, error monitoring, logging, security, analytics, and related functions. Based on the current production architecture, these providers include Amazon Web Services and Amazon SES, Sentry for error monitoring, Google Workspace for company communications, and Apple for app distribution and device-platform services where applicable.
When preventive public-profile filtering is activated, Amazon Bedrock Guardrails may process proposed public display names, biographies, and session titles, and Amazon Rekognition may process normalized avatar-image bytes. Those adapters do not receive Creator live audio through this filtering path. Service providers may process information only to perform services for Blipside, subject to applicable contracts and law.
The active provider list may change, and Blipside will keep its disclosures aligned with the production release.
Other users and the public
We disclose public Creator profile and session information to Listeners and other people who can access the relevant Blipside surface. Live audio is transmitted to Listeners who join the session.
At your direction
We disclose information when you direct us to do so, request a feature that requires disclosure, or authorize a connected service.
Legal, safety, and enforcement purposes
We may disclose information when we reasonably believe it is necessary to:
- comply with applicable law, a court order, or valid legal process;
- respond to an emergency or a credible threat of harm;
- investigate child-safety, fraud, abuse, security, or intellectual-property concerns;
- enforce our agreements or protect rights and the Service; or
- establish, exercise, or defend legal claims.
Corporate transactions
We may disclose information in connection with a merger, financing, reorganization, acquisition, bankruptcy, or sale of all or part of Blipside, subject to appropriate confidentiality and data-protection measures.
6. Cookies, browser storage, and device storage
Blipside Voices uses essential cookies and browser storage for authentication, security, account and workflow state, drafts, preferences, microphone selection, and other Creator functions. The normal production Creator session uses a secure HttpOnly cookie. Certain browser workflow values may be stored locally and should be cleared on sign-out or terminal workflow transitions as implemented.
The Listener application uses the iOS Keychain for authentication credentials and uses device storage for account-backed caches, preferences, playback settings, interface state, and operational flags. Some unrelated device settings may remain after account deletion.
Blipside does not currently use advertising cookies or third-party tracking for cross-context behavioral advertising. Server and infrastructure logs may process IP addresses and device or network information even when the application does not set an advertising cookie.
7. Sale, targeted advertising, and tracking
Blipside does not sell personal information. Blipside does not share personal information for cross-context behavioral advertising and does not currently use personal information for targeted advertising.
The current iOS privacy configuration declares tracking as false. Blipside will re-evaluate this statement before introducing advertising, new analytics SDKs, data-broker relationships, or another practice that could change the legal classification of its data use.
8. Retention
We retain information only for as long as reasonably necessary for the purpose for which it was collected, including providing the Service, maintaining security, resolving disputes, enforcing agreements, and meeting legal obligations. Our ordinary v1 posture is:
- Account, profile, preferences, and session data: while the applicable account is active, followed by deletion processing and the limited exceptions below.
- Verification and recovery code: expires after 15 minutes; related security records are minimized under the applicable cleanup process.
- Authenticated session: up to 30 days unless revoked sooner.
- CloudWatch and S3 operational telemetry: 30 days.
- Error and diagnostic records: retained only as long as reasonably needed for reliability, security, and incident response, subject to the configured provider period.
- Database backups: up to 7 days, with deletion-receipt reconciliation when a backup is restored.
- Live audio: no deliberate archive; transient processing, buffering, and caching only as needed for live delivery and ordinary expiry.
- Support correspondence: retained while needed to respond, document the resolution, and address a related dispute, safety issue, or legal obligation.
- Reports and moderation evidence: retained while open and, after resolution, only as reasonably needed for safety, fraud prevention, dispute handling, or legal obligations.
- Policy and acceptance evidence: retained while needed to administer the account, document the agreement, resolve a dispute, or meet a legal obligation, with direct identifiers removed or pseudonymized after deletion where practical.
- Pseudonymous deletion receipt: retained while reasonably needed to prove completion and prevent restoration from backup.
We may retain information longer when a specific legal hold, active claim, child-safety matter, fraud investigation, copyright process, or law-enforcement obligation requires it. When the reason ends, the information will return to the applicable schedule.
Deletion from active systems may not immediately erase information from ordinary backups, network or device caches, or data already received by another person. We use deletion receipts and restoration procedures intended to prevent a deleted account from becoming active again after a backup restore.
We may retain de-identified or aggregate information that cannot reasonably be linked to you.
9. Your choices and privacy rights
You can use available account controls to:
- update Listener languages and other preferences;
- follow or unfollow Voices and teams;
- block or unblock a Voice;
- update Creator profile and session information within the applicable lifecycle;
- recover or secure an account;
- request or download an account copy; and
- initiate or request deletion.
Depending on applicable law, you may have rights to request access, correction, deletion, a portable copy, restriction, objection, or an appeal of a privacy-request decision. You may also have the right to use an authorized agent. Blipside will honor rights required by applicable law after reasonable identity verification.
Submit a privacy request to privacy@blipside.app. Describe the account role and request. We may ask for information reasonably necessary to verify your identity and protect the account. We will respond within the time required by applicable law and explain any material limitation or denial.
Because Blipside does not sell personal information or share it for cross-context behavioral advertising, there is no current sale or targeted-advertising opt-out to exercise. If that changes, Blipside will provide required notice and controls before the practice begins.
10. Account deletion
Listener accounts
Authenticated Listener account deletion is available in the Listener application's account settings. The process requires confirmation and is designed to delete the separate Listener identity and Listener-associated data without deleting an independent same-email Creator identity.
Deletion removes active Listener account and authentication records, profiles, preferences, follows, blocks, authored reports under the ordinary retention rule, and other Listener-associated data. It also clears account-backed local state that the application controls after confirmation. Device settings or prior device or iCloud backups outside Blipside's direct control may retain earlier bytes under the platform's ordinary behavior.
Creator accounts
Authenticated Creator account deletion is available through the Creator account experience. It requires the current password and deliberate confirmation, fails closed while a Creator session is starting or live, and returns a recoverable status if the outcome is uncertain. A pseudonymous deletion receipt prevents routine restoration of the deleted account from backup. You may also submit a verified manual request to privacy@blipside.app.
Creator deletion ordinarily removes or de-identifies the Creator authentication record, public profile, managed avatar, drafts, schedules, sessions, recaps, analytics, and other Creator-linked personal information, subject to the retention schedule and legal exceptions above. Disabling an account or resetting a profile is not a substitute for deletion.
Linked identity providers
If Blipside enables Sign in with Apple or another linked identity provider, Blipside will revoke or remove the relevant account linkage as required before representing the deletion as complete. Sign in with Apple is not enabled in the current production release.
11. Children's and teen privacy
Blipside is a general-audience service and is not directed to children under 13. Listener accounts require an eligible age range indicating at least age 13. Creator accounts and Go Live access require an eligible age range indicating at least age 18.
Blipside does not collect a full date of birth for ordinary eligibility. Age-range information is private and is not displayed on a profile or session.
If we learn that we collected personal information from a child under 13 without legally sufficient authorization, we will take appropriate steps to delete or restrict the information and account. A person who reports a possible underage account should not send unnecessary information about the child through an ordinary channel.
Additional teen-privacy, guardian, age-assurance, or content-access requirements may apply depending on launch territory and platform rules.
12. Security
Blipside uses administrative, technical, and organizational safeguards designed to protect information. Current safeguards include password hashing, authenticated routes, secure session handling, session expiration and revocation, role boundaries, rate limits, redaction, encryption for relevant cloud storage and databases, restricted infrastructure, logging, and audited administrative actions.
No system is perfectly secure. Do not send passwords, verification codes, or other sensitive credentials to Support. Report a suspected vulnerability to security@blipside.app and avoid accessing another person's information or disrupting the Service.
13. International processing
Blipside and its primary infrastructure are based in the United States. Information may be transferred to and processed in the United States, where privacy laws may differ from those in your location. If Blipside intentionally expands into additional jurisdictions, it will implement the required transfer, rights, and local-notice measures before representing that expansion as supported.
14. Changes to this Policy
Blipside may update this Policy. Each version will have a new effective date. We will provide notice appropriate to the nature of the change.
A Privacy Policy update is generally a notice rather than contractual assent. If a change requires affirmative consent under applicable law or materially changes an optional data use, Blipside will request that consent separately. A new Privacy notice does not erase or replace acceptance evidence for the Terms of Use or Creator Terms.
15. Contact
- Privacy questions and requests: privacy@blipside.app
- Product support: support@blipside.app
- Security concerns: security@blipside.app
- Legal notices: support@blipside.app with the subject Legal Notice
Blipside, Inc. 200 Washington Avenue, Floor 5, #82 Towson, MD 21204 United States