Privacy Policy

Version 2.0.5 · Effective October 19, 2026 · Last updated October 5, 2026

This Privacy Policy describes how IGNIFY, Inc. ("IGNIFY", "Ignify", "we", "us", or "our") collects, uses, shares, and protects information about you when you use the IGNIFY and IGNIFY Studio mobile applications (iOS and Android; bundle identifiers us.ignify.app and us.ignify.studio), our public website at ignify.us, and our customer dashboard at app.ignify.us (collectively, the "Platform"). IGNIFY Studio is the app for Studio owners, admins, and teachers. Both apps use the same IGNIFY account.

IGNIFY is a technology platform that connects students and families with independent music studios and teachers ("Studios"). IGNIFY is not a Studio or a teacher, does not deliver lessons itself, and is not a party to the lesson relationship between you and a Studio. This Policy covers IGNIFY's own handling of your information; a Studio's separate handling of information it receives through the Platform is governed by that Studio's own practices.

For questions about this Policy or to exercise your privacy rights, contact us at privacy@ignify.us. For other legal matters, contact legal@ignify.us.

1. Information We Collect

Information you (or a guardian) provide directly.

• Adult account details: your name, email address, and date of birth (the apps ask for it to confirm you are at least 18), your answer to "How did you hear about us?", and, if you add them, your phone number and a profile photo. If you sign in with Google or Apple, we receive your name and email address from that provider (and, for Apple, an Apple user identifier).
• Minor child profiles: when a parent or guardian adds a child to their family account, or a Studio adds a child as its student and the guardian is then invited to confirm the profile, we collect only the child's first name, date of birth, the child's relationship to the guardian (for example, "child" or "ward"), and a bundled stock avatar illustration. We do not collect a child's last name, an uploaded photograph, location, payment information, or any contact information for the child separate from the guardian's account. See Section 6 (Children's Privacy).
• Studio relationships: your enrollments, roles, and memberships across the Studios you use.
• Studio business records (IGNIFY Studio): if you run a Studio, its name, address, phone number, email, website, logo, and cover image; and the records a Studio keeps on the Platform about the people it works with: the names, email addresses, and phone numbers of families and staff, staff job titles and hire dates, and students' names and dates of birth (for children, see the item above). A Studio types these in or imports them (see "Information from connected integrations"). A student a Studio imports from its calendar without telling us their age is stored with the name the Studio imported.
• Payment records a Studio keeps: cash payments a Studio records, invoices and whether they are paid, balances owed, and, if a Studio closes, any refunds, how they were paid, the reason a Studio gives for not refunding, and the contact details it leaves for families. Card and bank details are entered only on Intuit's QuickBooks checkout page and never reach IGNIFY.
• Bookings and lessons: scheduling, attendance, and lesson records.
• Communications: chat messages and the content you exchange with Studios, teachers, and family members through the Platform, community posts and comments, and call history (who called whom, and when). Calls themselves are not recorded (see Section 5).
• Photos, videos, and files you upload: profile photos, Studio logos and cover images, gallery photos and videos, images and PDFs in community posts, documents teachers upload, and files sent in chat.
• Consented lesson audio: audio of a lesson, captured only when a teacher initiates recording and the applicable consent has been given — see Section 5.
• Bug reports and support content: when you file a bug report, the description, optional screenshot, recent diagnostic logs, and limited device and app context you submit. Version 1.7.7 does not offer or send a bug-report voice note. Server-side intake discards any legacy voice-note field without transcription or retention. Historical records are described in Section 8.
• Website forms: if you join the waitlist or send us a message on ignify.us, what you enter: your name and email address and, if you add them, your studio's name, what you teach, and your message. They are emailed to our team.

Information collected automatically.

• Device and technical identifiers: device identifiers, push-notification tokens, app build and OS version, and log data including IP address.
• Website visits (ignify.us): unless you decline in the site's cookie banner, the site tells our server each page you open, with the page that sent you there, any campaign tags in the link, and your browser's user-agent string. Our server uses your IP address once to look up an approximate city, region, and country through the ipwho.is service. It then stores that approximate location and a one-way hashed form of the IP address, which lets us count unique visitors, instead of the address itself. We may send ourselves a text message naming the approximate city, the page, and where the visit came from. These records are kept for up to 90 days (see Section 8). Google Analytics also collects information about your visit (see Section 12). If you decline, the site stops sending both.
• Location (Explore): Explore can show Studios near a place. IGNIFY asks for your location the first time you open Explore and, if you allow it, uses it each time you open Explore; IGNIFY Studio asks only when you tap "Use my current location". The apps request a reduced-accuracy (approximate) position from your device. That position, or the coordinates of a place you type, is sent with your search so we can sort Studios by distance. We do not save it to your account, but it can appear in our server request logs. To turn a place you type into coordinates, or your position into a neighbourhood name, the apps use your phone's built-in geocoding service, which Apple (iOS) or Google (Android) provides. You can always type a place instead of sharing your location.
• Mobile analytics and crash data (apps only): our mobile apps embed Firebase Analytics, Firebase Crashlytics, and Firebase Performance Monitoring. These send to Google a pseudonymous identifier — a pseudonymous account identifier and your role — together with crash and performance diagnostics. They do not transmit your raw email address, phone number, name, or date of birth. Google also infers an approximate location, such as your city or region, from your device's IP address. See Section 12 (Cookies and Tracking).

Information from connected integrations.

• If you connect Google Calendar or QuickBooks Online, we receive the OAuth access tokens and the data the integration you enabled requires: from Google Calendar, read-only access to calendar events (titles, times, descriptions, locations, and attendees); from QuickBooks Online, the Studio's invoices and payments and, when a Studio imports them, its customer and employee lists (names, email addresses, phone numbers and, for employees, hire dates). A Studio uses these to bring its existing families, students, staff, and schedule into IGNIFY. When a Studio imports these records, an AI service provider helps us read and organise them (see Section 4).

2. How We Use Your Information

We use your information to:

• Create and manage your account, your family profiles, and your Studio memberships;
• Process bookings and facilitate invoicing and payment status (IGNIFY does not process payments itself — see Section 3);
• Help Studios set up and run their business on the Platform, including importing the records they choose to bring in and keeping the payment records they enter;
• Show you Studios near a place you choose in Explore;
• Send booking confirmations, reminders, schedule changes, and service communications;
• Generate draft completed-lesson reports from consented lesson audio (see Section 4);
• Enable chat between you, the Studios you use, and your family members;
• Operate, secure, debug, and improve the Platform;
• Detect and prevent fraud, abuse, and security incidents; and
• Comply with legal obligations and respond to lawful requests.

We do not sell your personal information, and we do not share it for cross-context behavioral advertising. We do not use your data to train external foundation models (see Section 4).

3. How We Share Information

We share information only with the categories of recipients listed below, each for the specific purpose stated. Several recipients act as our service providers or sub-processors and process information on our behalf under contract.

We do not share your personal information with advertisers or data brokers, and we use no advertising trackers. Our public website ignify.us uses Google Analytics, which you can decline in its cookie banner; our customer dashboard at app.ignify.us uses no third-party analytics (see Section 12).

Google user data — Limited Use

When you connect Google Calendar, IGNIFY'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. We do not use Google user data for advertising, do not sell it, and do not transfer it except as needed to provide the feature you requested, to comply with applicable law, or in connection with a merger or acquisition.

4. AI and Lesson Reports

A central feature of IGNIFY is AI-assisted draft completed-lesson reports. Here is exactly how that works.

What is recorded. When a teacher starts recording a lesson — and only then, with the consent described in Section 5 — the lesson audio is captured, sent over an encrypted connection, and stored on IGNIFY's infrastructure. Recording is teacher-initiated; it is not always-on.

How audio becomes a transcript. Lesson audio is transcribed by our own self-hosted speech-to-text transcription, running on our cloud infrastructure. The audio is not sent to any third-party transcription service.

What is sent to Anthropic for a lesson report. Only the transcript text — never the raw audio — is sent to Anthropic, PBC through Anthropic's first-party Claude API to draft a report. We do not route this content through any intermediary model-hosting service.

Consent is enforced before AI processing. The Platform checks that the required consent exists before any transcript text is sent to Anthropic. This check is fail-closed: it runs when a report job is submitted, again immediately before the model is called, again if an error occurs, and is re-checked at the time of the call. If valid consent is not present, no transcript is sent.

No model training — a contractual commitment. Anthropic operates the Claude API under its Commercial Terms, which contractually prohibit Anthropic from using API content to train its models. This "no training on your data" protection is a contractual commitment by Anthropic, not a technical control implemented in our code. We rely on Anthropic's contractual terms for it.

Teacher review is required. AI output is a draft. A teacher, Studio owner, or admin must review and finalize each report before it is shared. Reports are not delivered to families automatically.

Other uses of Claude. We send three other kinds of content to Anthropic through the same API and under the same Commercial Terms: (1) the bug reports you file (your description, plus the app logs, screen and network breadcrumbs, and device details attached to them), so Claude can suggest a severity, an owning team, and likely duplicates; (2) when a Studio asks IGNIFY Studio to suggest wording for its own listing, the details it is writing about, such as a lesson or service name and type, its length, an amenity, and the Studio's name and category, so Claude can draft text the Studio reviews before using it; and (3) when a Studio imports its calendar or billing records (from Google Calendar or QuickBooks Online), parts of those records, so Claude can help read and organise them, for example by suggesting which events are lessons and how the people in them match the Studio's students, families, and staff. Those records can include students' names, including children's. Anthropic processes them on our behalf to provide this feature, and its Commercial Terms do not allow it to use them to train its models. The consent check above applies to lesson transcripts; these three uses involve no lesson audio.

Bug-report voice feature retired. Version 1.7.7 does not offer voice capture. Server-side intake does not transcribe or retain any voice-note field sent by an older installed client. Bug reports created while the former feature was available may retain transcript text — and some older legacy records may retain an audio attachment — under the retention rules in Section 8. In particular, legacy rows created before per-record expiry was introduced may not have an automatic expiry timestamp. We do not create new bug-report voice recordings or transcripts.

Speaker labels are heuristic, not biometric. Where a report attributes speech to "the teacher" or "the student," those labels come from talk-time heuristics, not from a biometric voiceprint. We do not create or store biometric identifiers or voiceprints, and this pipeline is not intended to generate "biometric information" under the Illinois Biometric Information Privacy Act (BIPA).

5. Recording and Consent

Recording needs a teacher and consent. No recording occurs unless a teacher initiates it and the applicable consent has been captured. For a child, the parent or guardian chooses whether to allow lesson recording and lesson reports, highlight clips, and observer mode when they create the child's profile or confirm one a Studio created, and can change these choices at any time (see Section 6).

Granular, revocable consent. Consent is granular: it can be given globally and per-Studio, and it can be revoked at any time. The Platform keeps an immutable audit history of consent changes.

Per-session acknowledgment. For a recorded session, the relevant participant or guardian is asked to explicitly accept or decline before recording proceeds.

Calls are not recorded by IGNIFY. Voice and video calls placed through the Platform are not recorded on our servers. Only lesson audio and "lab" uploads are recorded and processed as described in this Policy.

Revoking consent. You may turn recording consent off at any time in the app's consent settings, for one Studio or for all of them. Turning it off for one Studio applies to future recordings. Revoking all recording consent for a person also withdraws every report that includes that person's recorded lessons, including finalized ones, and deletes its audio, transcript, generated draft, published copy, preview, and cover image; a report from a group lesson is withdrawn for everyone in it (see Section 9). A report we already sent by email or chat cannot be recalled, but its link stops working.

6. Children's Privacy (COPPA)

IGNIFY is used by families, and children participate through guardian-managed profiles. We take the following positions, and we describe them honestly rather than overstating.

Children do not create their own accounts. Children participate only through child profiles that a parent or guardian creates and manages, or that a Studio creates for its student and the guardian is then invited to confirm; a child profile is not given its own login. No one under 18 may create or operate an independent account, and we describe below the current limits of our age screening for self-registration.

What we collect for a child profile. As stated in Section 1, only the child's first name, date of birth, relationship to the guardian, and a stock avatar — plus the lesson attendance, finalized reports, and (only with the guardian's consent) lesson audio tied to the child's enrolled classes. We do not collect a child's last name, photo, location, payment, or independent contact information.

Recording choices for a child. When a parent or guardian creates a child's profile, or confirms one a Studio created, they choose whether to allow lesson recording and lesson reports, highlight clips, and observer mode for that child. They can change any of these choices at any time in the app's Permissions settings. Sharing anything publicly is not one of these choices.

When a Studio imports its records. A Studio can bring its existing calendar or billing records into IGNIFY. Those records can include a child's name, and our AI service provider helps us read and organise them (see Section 4).

We do not knowingly permit underage self-registration, and we flag suspected underage accounts for review. Because the pre-signup age gate has been removed, it is possible for a Google or Apple social sign-in to create an account identity before the person's age is known. That identity is not usable as an account until a profile is completed, and completing one requires a date of birth that meets our minimum age. Our servers refuse a date of birth below the minimum age wherever one is recorded, so this does not depend on the app enforcing it. Where an account is identified as belonging to someone under 18 outside the guardian-managed model, the app flags it for review; decommissioning is handled manually and is not yet automated.

Verifiable parental consent. We are working to adopt a verifiable parental consent method consistent with COPPA (16 CFR § 312.5). Until that mechanism is in place, we do not represent that we obtain verifiable parental consent in every case, and we rely on the guardian-managed model and the decommissioning practice described above. We do not claim that we never receive any information relating to a child under 13.

Guardian rights. A guardian may, at any time, from inside the app or by emailing privacy@ignify.us, review what we have collected about their child, correct or delete it, delete the entire child profile, revoke consent for lesson audio, or request an export of the child's data. Deleting a child profile in the app also deletes that child's consent records, studio enrollments, and the finalized lesson reports about only that child. A Studio's own records of lessons it delivered, such as its lesson calendar and reports from group lessons that included other students, stay with the Studio, as Section 9 describes for account deletion. We do not condition a child's participation on collecting more information than is reasonably necessary.

If you believe a child has provided us information outside the guardian-managed model, contact privacy@ignify.us and we will act to remove it.

7. Data Security

We use the following safeguards, and we describe their scope precisely.

• Encryption at rest. Data is encrypted at rest using industry-standard server-side encryption managed by our cloud provider.
• Encryption in transit. Connections to the Platform use TLS 1.2 or higher.
• Chat content. Chat messages are stored in plaintext at the application layer (protected by the at-rest encryption above); they are not end-to-end encrypted.
• Web application firewall. We use a web application firewall and other industry-standard safeguards to help protect the Platform.
• Log hygiene. We apply best-effort masking of personal information before it is written to our system logs. This masking is applied to logs; it is not applied to the transcript text we send to Anthropic for report drafting, or to the description you type in a bug report (see Section 4).
• Access controls. We use least-privilege access controls and require multi-factor authentication for administrative access.

No method of transmission or storage is completely secure. If you suspect a security problem, contact security@ignify.us.

8. Data Retention

We retain personal information for as long as needed to provide the Platform and for the specific periods below. These periods are disclosed in full; do not rely on any shorter summary you may have seen previously.

• Lesson audio (raw and normalized): up to 7 days, then automatically deleted.
• Lab audio uploads: up to 14 days, then automatically deleted.
• Lab transcriptions: up to 30 days, then automatically deleted.
• Report transcripts and intermediate report drafts: up to 14 days, then automatically deleted.
• Community uploads: up to 7 days, then automatically deleted.
• Finalized lesson reports: retained as part of your and the Studio's records, with no fixed end date for adults. A finalized report about a child is kept only while it serves the lessons the guardian enrolled the child in: until the guardian revokes all recording consent for that child, deletes the child's profile, the child's sole guardian deletes their account, or the guardian asks us to delete it (see Sections 6 and 9). We are building an automatic time limit for children's reports. Until it is in place, we do not delete them on a schedule.
• Bug-report records: new records receive a 180-day expiry timestamp; deletion by the database is asynchronous after expiry. Legacy records created before per-record expiry was introduced may lack that timestamp and can remain longer — until account deletion or a separately reviewed deletion or backfill removes them. This legacy set may include transcript text or an audio attachment from the retired bug-report voice feature; the 1.7.7 client and server-side retirement control do not add new voice data.
• Site-visit analytics beacon data: up to 90 days.
• Tax and payment records (including a closing Studio's refund records and statements): retained as required for tax and accounting purposes — typically about 7 years under U.S. law — even after account deletion. We do not yet delete these records automatically when that period ends.
• Chat messages and chat attachments: retained for the life of your account. After you delete your account, messages and files you sent to others may remain in their conversations, as described in Section 9.
• Other account content: retained for the life of your account or until deleted, subject to the deletion scope in Section 9.

9. Account Deletion

You can start deleting your account at any time from inside either app (Account → Security → Delete my account → confirm; in IGNIFY Studio, before you create or join a Studio: Home → Delete account), from the web at https://app.ignify.us/auth/delete-account, or by emailing privacy@ignify.us. If your account owns a Studio, you will first be asked to hand the Studio over to another owner or close it, and if you still hold upcoming lessons booked for other families, to hand those over too. This protects the Studio's teachers' and families' records; your deletion then proceeds normally.

How deletion works. When you delete your account, we place it in a 30-day tombstone state. If you do not cancel within that window by signing back in, we then perform an irreversible hard purge. The purge removes your records across our databases, deletes your stored avatar image, removes your stored push-notification tokens and the corresponding push-provider registration, and removes your identity from our authentication system. Some references to you in other users' data are anonymized, and the deletion is recorded in an audit log.

Content you shared with others. Some content you shared with others, such as chat messages and the files you sent with them, may remain in their conversations after your account is deleted. As our deletion process completes, that content is removed or de-identified; for example, the messages you sent no longer show your name or photo. Messages other people sent to you are their content, not yours, and are not deleted by your request.

Deleting a sole guardian's account removes the family's data. If you are the only guardian on a family account, deleting your account cascade-deletes the family's data, including the child profiles you created and their associated consent records. This is intentional: a child profile exists only under a guardian's account and is not retained once its sole guardian is removed.

Honest scope limits — please read.

• Finalized lesson reports follow Section 8, not your account. Deleting your own account does not delete finalized lesson reports about you. A finalized report is also the Studio's record of a lesson it delivered, so it is retained as described in Section 8: your access is removed with your account, but the record remains with the Studio. If you want a report's content removed rather than just your access to it, revoke recording consent for that subject — that retracts the report and deletes its audio, transcript, generated draft, published copy, preview and cover image, while keeping the consent audit trail.
• A sole guardian's deletion also removes their children's reports. If you are the only guardian on a family account, the cascade described above deletes your child profiles' finalized lesson reports, the stored transcripts and processing artifacts for those lessons, and any report cover image — not only your access to them.
• Reports from group lessons are retained. Where a lesson included students from more than one family, that lesson's report is the other families' and the Studio's record too, so the cascade leaves it in place — including the part naming your child. To have that content removed as well, revoke recording consent for your child, which retracts the whole report for every subject on it.
• Deletion is not automatically propagated to sub-processors. Deleting your IGNIFY account does not automatically delete data already held by our sub-processors — including Anthropic, Firebase/Google, and QuickBooks Online. Those providers retain and delete data under their own policies and contractual terms.
• Legally required records are retained. Tax and payment records are kept as described in Section 8.

If you need data removed from a sub-processor, contact privacy@ignify.us and we will assist where we are able.

10. Your California Privacy Rights (CCPA / CPRA)

If you are a California resident, you have the right to:

• Know the categories and specific pieces of personal information we have collected, the sources, the purposes, and the categories of recipients (see Sections 1 and 3);
• Access the specific pieces of personal information we hold about you;
• Delete your personal information, subject to the legally required retention and the scope limits described in Sections 8 and 9;
• Correct inaccurate personal information;
• Opt out of the "sale" or "sharing" of personal information — we do not sell personal information and do not share it for cross-context behavioral advertising, so there is nothing to opt out of, but the right exists;
• Limit the use of sensitive personal information — we do not use sensitive personal information beyond what is necessary to provide the Platform; and
• Non-discrimination — we will not discriminate against you for exercising these rights.

To exercise these rights, contact privacy@ignify.us or use the account-deletion path in Section 9. We will respond within the time required by law (generally 45 days).

11. Your European Privacy Rights (GDPR / UK GDPR)

If you are located in the European Economic Area, the United Kingdom, or Switzerland, you have the right to access, rectify, erase, restrict, and port your personal data; to object to processing based on our legitimate interests; to withdraw consent where processing is based on consent; and to lodge a complaint with your supervisory authority. Erasure is subject to the legally required retention and scope limits described in Sections 8 and 9.

The legal bases on which we process your data include contractual necessity (delivering the service you signed up for), legitimate interests (operating, securing, and improving the Platform), legal obligation (retention required by law), and consent (recording features and any processing for which consent is required).

Submit requests to privacy@ignify.us. We respond within the time required by applicable law (generally one month).

12. Cookies and Tracking

Our websites. Our public website at ignify.us uses cookies to understand how people use the site. When you visit, Google Analytics sets its own cookies (such as _ga) and collects the pages you visit and what you do on them (such as opening or sending a form), your device and browser details, and an approximate location; Google processes this for us so we can see how the site is used. Our own visit log also runs, and looks up your approximate city (see Section 1). You can decline both in the site's cookie banner, or at any time through "Cookie settings" at the bottom of every page. Declining stops them and deletes Google Analytics' cookies from your browser. We do not use Google Analytics for advertising. The site remembers your choice on your device for 12 months. Cloudflare Turnstile runs on the site's forms for security, whatever you choose. Our customer dashboard at app.ignify.us keeps your sign-in in your browser's storage or, where enabled, in secure sign-in cookies, and sets no analytics or advertising cookies. Apart from Google Analytics and Cloudflare Turnstile, our sites load third-party files only to display their pages: fonts from Google Fonts, and code libraries from public content-delivery networks (jsDelivr, cdnjs, the jQuery CDN, and unpkg). As with any web request, those providers receive your IP address and basic browser details when your browser fetches a file; we do not use them to track you.

Our mobile apps. The Firebase Analytics, Crashlytics, and Performance described in Section 1 are present in the mobile apps only, not on our websites. They use the pseudonymous identifiers described there and do not carry your raw email, phone, name, or date of birth.

No cross-context behavioral advertising. We do not sell or share personal information for cross-context behavioral advertising. Our iOS apps do not access the Apple Identifier for Advertisers (IDFA).

You can control cookies through your browser settings; blocking the sign-in cookies, where the dashboard uses them, may prevent parts of the dashboard from working.

13. International Transfers

Our infrastructure is hosted on AWS in the United States. If you use the Platform from outside the United States, your information will be transferred to, stored, and processed in the United States. Where required for transfers from the EEA, the United Kingdom, or Switzerland, we rely on standard contractual clauses and our providers' data-processing terms.

14. Changes to This Policy

We may update this Policy. We will notify you of material changes by email or in-app notice at least 14 days before they take effect and, where required, will prompt you to re-accept the updated Policy in the app. The "Effective" date at the top of this page shows when this version takes effect, and the "Last updated" date shows when we published it.

15. Contact

IGNIFY, Inc. — Privacy Team

• Privacy and data-rights requests: privacy@ignify.us
• Other legal matters: legal@ignify.us