Privacy Policy

Onomo Inc. (“onomo,” “we,” “us,” or “our”) is committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use the onomo platform located at onomo.io and any associated subdomains, applications, or services (collectively, the “Service”).

By using the Service, you consent to the data practices described in this policy. If you do not agree, please do not use the Service. This policy should be read in conjunction with our Terms of Service, Cookie Policy, Acceptable Use Policy, and Copyright Policy.

2.1 Information You Provide Directly

• Account Information: Email address, username, and password (stored as a cryptographic hash — we never store plaintext passwords) when you create an account.
• Birth Month and Year: Your birth month and year, asked when you sign up (or the first time you use the Service after this question was added). We never ask for the day. See Section 8 for why we ask, who can see it, and how long we keep it.
• Profile Information: Display name, avatar, banner, and any other optional profile details you choose to provide, along with your profile settings, such as whether your profile is private and whether it is marked Explicit.
• Payment Information: When you make a purchase, payment details (credit card number, billing address) are processed directly by our payment processor (Stripe). We do not store your full credit card number on our servers. We retain only a tokenized reference, the last four digits, card type, and billing country for transaction records.
• Support Communications: Any information you provide when contacting us for support, including email content, attachments, and metadata.
• Marketplace Creator Information: If you sell content on the marketplace, we collect additional information required for payment processing and tax reporting (e.g., legal name, tax identification number, payout details).

2.2 Information Generated Through Use

• Project Data: The creative content you produce across the Service's surfaces — including music projects, patterns, presets, synth parameters, audio recordings, mixer settings and automation (Studio); designs, images and layers (Canvas); video timelines and clips (Motion); lyrics, notes, ideas and voice memos (Journal); and related assets. By default this data is stored locally in your browser (IndexedDB / local storage) and is optionally synced to our cloud servers when you enable cloud sync or use features that require it.
• Voice Memos & Transcription: Journal voice memos are recorded and stored locally on your device. Live transcription, where available, is performed by your browser's built-in speech recognition; the audio is not sent to us for transcription. Memo audio is uploaded to our cloud storage only if you save it to the cloud.
• AI Interaction Data: When you use AI features, your prompts and the relevant inputs are transmitted to our AI processing providers to generate output. For the Ono assistant this is structured project context (track names, note data, tempo, key, mixer settings, and similar parameters); for image and video generation this includes your prompt and any image, frame, or media you provide as input. See Section 5 for details.
• Usage Analytics: Aggregated data about feature usage, session duration, page views, and error reports, used solely to operate and improve the Service. Your birth month and year, and whether your account is a teen account, are never sent to our analytics providers.
• Social and Safety Records: Who you follow, follow requests you send or receive, the Explicit labels on your content, reports you file, and the results of automated image screening (Section 5.5).

2.3 Information Collected Automatically

• Device Information: Browser type and version, operating system, screen resolution, and device type.
• Network Information: IP address (anonymized for analytics), referring URL, and general geographic location (country/region level, not precise location).
• Cookies and Local Storage: Essential cookies for authentication, session management, and keeping an age restriction in place on a device, browser local storage for application state, and, only with your consent, an analytics identifier (PostHog) and masked error replays (Sentry). See our Cookie Policy for details.

We use the information we collect for the following purposes:

• Providing the Service: Operating Studio, Canvas, Motion, Journal and the other surfaces; processing audio, images and video; rendering exports; syncing projects across devices; and managing your account.
• AI Processing: Transmitting your prompts and relevant inputs to our AI providers to generate assistant responses and generated images or video, as described in Section 5.
• Payment Processing: Processing subscription payments, marketplace purchases, AI credit top-ups, and marketplace creator payouts.
• Communication: Sending transactional emails (account verification, password resets, payment receipts), service announcements, and security alerts. We will not send marketing emails without your explicit opt-in consent.
• Service Improvement: Analyzing anonymous usage patterns to identify bugs, improve performance, and prioritize feature development.
• Age Eligibility and Teen Protections: Using your birth month and year to confirm you are old enough for an account and to apply the protections for teen accounts described in Section 8.
• Content Safety: Screening images shown to others for nudity and sexual content, applying Explicit labels, and reviewing reports, as described in Section 5.5.
• Security and Fraud Prevention: Detecting and preventing unauthorized access, abuse, fraud, and violations of our Terms of Service.
• Legal Compliance: Complying with applicable laws, regulations, legal processes, or governmental requests.

4.1 Local Storage. By default, your project data is stored locally in your browser using IndexedDB and localStorage. This data resides on your device and is not transmitted to our servers unless you enable cloud sync. Local data is subject to your browser's storage policies and may be lost if you clear browser data.

4.2 Cloud Storage. When cloud sync is enabled, your project data is encrypted in transit using TLS 1.2 or higher and encrypted at rest on our servers. Audio files are stored in secure cloud storage with access controls. Cloud infrastructure is hosted by Vercel and Supabase, both of which maintain SOC 2 compliance.

4.3 Security Measures. We implement commercially reasonable security measures including: encryption in transit and at rest, industry-standard salted password hashing (passwords are never stored in plaintext), rate limiting, input validation, and access controls, together with regular security reviews. However, no method of electronic transmission or storage is 100% secure, and we cannot guarantee absolute security.

4.4 Breach Notification. In the event of a data breach that affects your personal information, we will notify affected users via email and/or in-app notification within seventy-two (72) hours of becoming aware of the breach, as required by applicable law. The notification will include the nature of the breach, the data affected, steps we are taking, and recommended actions for you.

5.1 Text / Assistant (Ono). When you use the Ono assistant, we transmit your text prompt and relevant structured project context — track names and types, note data (pitch, velocity, duration), tempo, key and time signature, mixer settings, automation parameters, and sequencer patterns — to our model provider, which is routed through OpenRouter. We do not send raw audio recordings to the assistant; only structured musical data and text are sent.

5.2 Image & Video Generation. When you use image or video generation (for example, in Canvas or Motion), we transmit your text prompt and any image, frame, or media you provide as an input to our generation provider, fal.ai, which runs third-party generative models to produce the output. This means that, unlike the assistant, media-generation features do involve sending the images or frames you choose to generate from.

5.3 AI Provider Data Handling. Our AI providers process this data under their own privacy policies and data processing terms. We do not use your content to train our own AI models, and we do not authorize our providers to use your content to train their general models for our account. Prompts and outputs may be transiently processed or cached for performance and abuse-prevention, but are not used by us for model training.

5.4 AI Conversation & Output Storage. Your Ono conversation history and generated outputs are stored locally in your browser and, if cloud sync is enabled, on our servers as part of your project data. We do not separately analyze, mine, or sell your AI conversations or outputs, and use them only to provide the Service to you.

5.5 Automated Image Screening. Nudity and sexual content are not allowed on the Service. To enforce this, images that will be shown to other people (avatars, banners, post images, cover art, a still frame from cover videos, and images or video sent in messages) are checked by an automated classifier run by our processor, fal.ai. We send the image (or the captured frame) for this check, and fal.ai returns a score; this processing is covered by the provider terms described in Section 5.3. We keep a screening record with the image's address, the account that uploaded it, where it was used, the result and score, the provider and model, and when it was checked. Images that are flagged cannot be used. Some images are held for review, and flagged or held images may be reviewed by our staff. Until an image has been checked, it may be shown only to adult accounts. If you believe an image was rejected by mistake, contact support@onomo.io.

5.6 AI Safety for Teen Accounts. When a teen account (or an account that has not given a birth date) uses AI features, we add extra safety instructions to text requests and use our providers' strictest available safety settings for image and video generation. Your birth month and year are never sent to AI providers.

We use the following third-party services to operate the Service. Each has its own privacy policy governing their handling of your data:

• Supabase — Authentication, database, and cloud storage infrastructure
• Vercel — Application hosting, deployment, and privacy-friendly usage analytics
• PostHog — Product analytics (page views, feature usage, and approximate location derived from IP; IDs in page addresses are removed before sending)
• Sentry — Error and performance monitoring
• Stripe — Payment processing (PCI DSS Level 1 compliant)
• OpenRouter — Routing for the Ono text/assistant model (see Section 5)
• fal.ai — Image and video generation processing, and automated image safety screening (see Section 5)

We do not sell, rent, or trade your personal information to third parties. We do not share your data with third-party advertisers or data brokers. We only share data with the service providers listed above to the extent necessary to operate the Service.

Active Accounts. We retain your account information and cloud-synced project data for as long as your account is active.

Deleted Accounts. When you delete your account, we will permanently delete your personal information and cloud-stored project data within thirty (30) days. Some information may be retained in encrypted backups for up to ninety (90) days before being permanently purged. Anonymized, aggregated analytics data that cannot be used to identify you may be retained indefinitely.

Birth Month and Year. Kept for as long as your account exists and deleted with it. When you join the waitlist, your birth month and year are checked and then discarded; they are not stored.

Image Screening Records. Screening records (Section 5.5) are kept so an image's result stays attached to it wherever it is used and it is not checked twice. When you delete your account, the link between these records and your account is removed.

Legal Obligations. We may retain certain information as required by applicable law, including transaction records for tax and accounting purposes (typically seven years) and data subject to legal holds or pending disputes.

Marketplace Creator Data. If you sell content on the marketplace, transaction records and tax-related information are retained as required by applicable tax law, even after account deletion.

8.1 Why We Ask Your Birth Month and Year. We ask everyone for their birth month and year (never the day) for two reasons: to confirm you are old enough to have an account, and to apply the protections for teen accounts (ages 13 to 17). Your age is worked out from the month and year each time it is needed, so protections lift automatically in the month you turn 18.

8.2 Who Can See It. Only you and authorized Onomo staff can see your birth month and year. It is never shown on your profile, never shown to other users, and never sent to analytics or AI providers. It is included when you ask us for a copy of your data.

8.3 Changing It. Once set, your birth month and year cannot be changed from your account. If it was entered incorrectly, contact support@onomo.io; staff may correct it after review, and every correction is logged.

8.4 Teen Account Defaults. Teen accounts start with privacy-protective settings: the profile is private, so only approved followers see posts and songs; the account is not listed in search, suggestions, or Explore, and its profile is not indexed by search engines; direct messages and collaboration invites work only with people the teen follows; Explicit content is hidden; new post images and cover art from others are shown only after they pass screening; and AI features use extra safety settings (Section 5.6). A teen can choose to make their profile public, which lets signed-in users see it, but the account still stays out of search and search engines until the teen turns 18. Accounts that have not yet given a birth date get the same content and contact protections until they do.

8.5 Children Under 13. The Service is not intended for children under thirteen (13), and we do not knowingly collect personal information from children under 13, consistent with the Children's Online Privacy Protection Act (“COPPA”). If someone indicates at sign-up that they are under 13, no account is created and their birth month and year are not stored; a cookie and a browser storage entry on that device keep the restriction in place (see our Cookie Policy). If we learn that an existing account belongs to a child under 13, we delete the account and its associated data. We keep only a minimal deletion record, without the email address, username, or display name, and delete it after thirty (30) days.

If you are a parent or guardian and believe your child under 13 has provided personal information to us, please contact us at privacy@onomo.io and we will take immediate action.

8.6 Parents and Guardians of Teens. Users aged 13 to 17 may use the Service with the permission of a parent or legal guardian, as described in our Terms of Service. A parent or guardian may contact privacy@onomo.io with questions about their teen's account or to request its deletion. We do not send teens content digests, and our newsletter is written for all ages and sent only to people who opt in.

Depending on your jurisdiction, you may have the following rights regarding your personal information:

9.1 All Users

• Access: Request a copy of the personal information we hold about you.
• Correction: Request correction of inaccurate or incomplete personal information (for your birth month and year, see Section 8.3).
• Deletion: Request deletion of your account and all associated personal data.
• Export: Export your projects and data from the Service at any time.
• Opt-Out: Opt out of non-essential analytics and marketing communications.

9.2 European Economic Area (EEA) Residents — GDPR

If you are located in the EEA, you have additional rights under the General Data Protection Regulation (GDPR), including the right to: data portability, restriction of processing, objection to processing, and the right to lodge a complaint with your local data protection authority. Our legal basis for processing your data is: (a) performance of a contract (providing the Service), (b) legitimate interests (security, fraud prevention, service improvement, age checks, teen protections, and image safety screening), (c) consent (where applicable, such as marketing communications), and (d) compliance with legal obligations, including those that protect children.

9.3 California Residents — CCPA/CPRA

If you are a California resident, you have rights under the California Consumer Privacy Act (CCPA) and the California Privacy Rights Act (CPRA), including the right to: know what personal information we collect and how it is used, request deletion of your personal information, opt out of the “sale” or “sharing” of your personal information (we do not sell or share your personal information as defined by the CCPA/CPRA), and non-discrimination for exercising your privacy rights.

To exercise any of these rights, contact us at privacy@onomo.io. We will respond to verified requests within thirty (30) days (or as required by applicable law).

onomo is operated from the United States. If you access the Service from outside the United States, your information may be transferred to, stored, and processed in the United States or other countries where our service providers operate. These countries may have data protection laws that differ from those in your jurisdiction.

By using the Service, you consent to the transfer of your information to the United States and other countries as described in this policy. Where required by applicable law (such as the GDPR), we rely on appropriate legal mechanisms for international data transfers, including Standard Contractual Clauses approved by the European Commission.

Some browsers transmit “Do Not Track” (DNT) signals. We do not use advertising cookies or track you across other websites. Analytics cookies are set only with your consent where the law requires it, and anyone can decline them with Cookie Settings in the site footer. We do not track users across third-party websites.

We may update this Privacy Policy from time to time. If we make material changes, we will provide at least thirty (30) days' notice via email or prominent in-app notification before the changes take effect. Non-material changes (such as formatting or clarification) may be made without notice. The “Last Updated” date at the top of this page indicates when the policy was last revised.

Your continued use of the Service after the effective date of any changes constitutes your acceptance of the revised policy.

If you have questions or concerns about this Privacy Policy or our data practices, please contact us:

• Privacy Inquiries: privacy@onomo.io
• Data Deletion Requests: privacy@onomo.io
• Security Concerns: security@onomo.io

Onomo Inc.
Atlanta, Georgia, United States