Privacy Policy

Last updated: November 7, 2026

This Privacy Policy explains what personal data FlowChord collects, why, who receives it, how long it is kept and what choices you have. It applies to the FlowChord website (flowchord.studio), the FlowChord app (app.flowchord.studio), the creators’ sites FlowChord serves at their own addresses (such as yourname.flowchord.studio) and the emails we send (together, the “Service”).

FlowChord is operated by Bahia Ventures USA LLC, a Delaware limited liability company (“FlowChord”, “we”, “us”), which decides how your personal data is used (the “controller”). You can reach us about anything in this policy at [email protected].

1. In short

• We collect what we need to run your account and your projects: your email, your profile, the files you upload and what you create with them.
• Your browser makes large files smaller before they are uploaded; a file that is already small enough, or that the browser cannot convert, is uploaded as it is. Much of the work — preparing files, lining recordings up, rendering the exported video — also happens on your device.
• To detect chords and lyrics, the audio of your recording is sent to AI service providers (Music.AI, and OpenAI or Groq); photos and scans of chord sheets, and pictures of guitar tabs, are sent to Anthropic, which also searches the web for a line of the lyrics heard when the song is not recognized otherwise. For Creator plan subscribers, Anthropic also plans Smart Edits from a few still frames of the video and the words heard in it, spoken or sung. They receive the content, not your name or email.
• Payments are processed by Stripe, and your card details go only to Stripe. We keep a record of your wallet — top-ups, bonuses, gifts and what each video cost — as accounting and tax law requires.
• We use error monitoring (Sentry) and, only if you accept it, analytics (PostHog). Whatever you choose, PostHog also tells us which features still being tried out your account may use (section 8). When you sign in to the app, sessions there are recorded too, unless you declined analytics; you can turn recordings off in Preferences. You can change both at any time (section 8). Anthropic’s Claude helps us look into error reports.
• We do not sell your personal data and we do not use it for targeted advertising. We use the audio of your recordings and the chords and guitar tabs you correct and export to train FlowChord’s own music-analysis models, so that chord and tab detection gets better for everyone; you can turn this off in Preferences (section 8). Your content never trains anyone else’s models.
• Your brand — logo, name, channels and business contact — is yours to fill in or leave empty. We use it for sponsorship opportunities only if you tick a separate box that allows it, and you can take that back at any time (section 5).
• You can access, correct, download and delete your data. Download it and delete your account from the account menu in the app, or write to [email protected].

2. Data we collect

2.1 Account and profile

• Email address, used to sign in with a one-time code.
• Name and profile photo, if you add them or if you sign in with Google, Apple or Facebook. With those providers we receive your name, email address and profile photo, as allowed by your settings there. We do not receive your password.
• Preferences: theme, language and chord notation.
• Acceptance of our terms: the version of the Terms of Service and this Privacy Policy you agreed to, with your confirmation that you are at least 18, how you agreed (when signing in, or later in the app) and when.

2.2 Your projects

• Files you upload: video and audio recordings, the song used in Play Along, chord or lyrics sheets (PDF, text or images), tab files and pictures of tabs, cover, background and other pictures. Before upload, your browser re-encodes large video and audio files (video up to 1440p) and shrinks pictures, and we store that prepared copy; a file that is already small enough, or that cannot be converted in your browser, is uploaded unchanged.
• File information: original file name, size, type, duration and a fingerprint (hash) of the file, used to recognize a file you upload again. For a video or audio recording, also what the file says of itself, read in your browser: its format, resolution, frame rate and codecs, the make and model of the camera or phone and the app that made it, the date it was recorded, and its own title, artist, album and genre tags — never its location.
• What you create: project names, song title and artist you enter, the music styles of the song, chords, lyrics, text and images on the video, styles, timing, edit history and settings.
• Your exports: for each video you export, its shape, size and length, the part of the song it plays, the layers and chords it shows, and the song’s details and music styles as they were then. The video file itself is not stored.
• Play Along performances: the performance you upload when you choose Finish, and timing measurements of the recording (delays in milliseconds and the type of device used, such as “Bluetooth” or “built-in” — not device names or identifiers).
• Fingerings: chord shapes you keep or draw, and any name you give them.
• Results of automated analysis: detected chords, beats, tempo and key; the lyrics transcript with word timings and detected language; what was read from a chord sheet; the guitar notes our own transcription service hears in a recording (the tablature) and a tab file you bring to a project; and, for chords and tabs, the provider’s or the service’s original output.

2.3 Camera and microphone

Only Play Along uses your camera and microphone, and only after you allow it in your browser. While you record, your takes are stored in your browser on your device. Nothing recorded is uploaded until you choose Finish; then the finished performance is uploaded to your project and the takes are deleted from your device. To keep recordings in time, the browser on your device remembers a timing correction for each pair of audio devices, identified by the identifiers your browser assigns to those devices; this stays on your device and is not sent to us.

2.4 Waitlist

If you join the waitlist, we keep your email address, the language of the page, which form you used, the date and, if you unsubscribe, the date you did.

2.5 Use of the Service and your device

• Product analytics (only if you accept analytics): actions in the app (for example, “project created” or “video exported”) with technical details such as counts, durations and settings — not the text of your lyrics, project names or searches; the pages you visit (without the parts of the address that could identify a project); browser, operating system, device type, screen size, and approximate location derived from your IP address by our analytics provider.
• Session recordings (app only, while you are signed in): by signing in you agree to this policy, and with it to PostHog recording how the app’s interface responds to your clicks, scrolls and typing, so we can find problems. This does not happen if you declined analytics, if your browser sends Global Privacy Control, or after you turn off “Record my sessions” in the app’s Preferences. Text fields and the areas that show the text you write (lyrics, names, email, the text you put on the video) are hidden in these recordings, and your videos and pictures are never recorded. The rest of the screen is recorded as it appears, including chord names and the address of each page. Session recordings are not used on the website.
• Error reports: when something fails in the app, Sentry receives technical details of the error, the browser and the page, linked to your user ID (not your email). An AI assistant, Anthropic’s Claude, reads new error reports to help us find their cause.
• Network data: your IP address and request details are processed by our hosting provider and by the security check that protects sign-in, the waitlist and the contact page, and appear in server logs.

2.6 Payments and your wallet

• Your wallet’s record: every top-up (its amount, its bonus and launch bonus, the amount and currency Stripe charged, the discount and the promotion code used), every charge for a video (the project and the length of song charged), every refund, and your balance after each, with the currency your wallet is in. The country that currency is set from (Terms of Service, section 3.3) is read from your connection’s IP address when you first sign in — the country only, never your address — or chosen by you in the app, and we keep when and how it was set.
• Your monthly plan: which plan you are on, each cycle and the minutes of song used from it, the changes and cancellations you schedule, and renewals that could not be charged (Terms of Service, section 3.8).
• Stripe references: the identifiers of the checkout, the payment and the price, so that a payment can be matched with Stripe’s record of it.
• Acceptance of the Terms: whether, and when, you accepted the Terms of Service at checkout.
• Balance we give you (Terms of Service, section 3.7): for a gift of balance, its amount, its date, its end date, how much of it is left, the member of our team who gave it and a short internal note on why. You see the gift and its end date in your History. The note is for our team and is not shown in the app, but you can ask us for it like any of your data (section 8).

2.7 Referrals and creators

• Referral link: when you arrive through a creator’s link, a first-party cookie (flowchord_ref) stores that creator’s code for 60 days (section 9). If you create an account in that time, we record which creator referred you. We also count that a creator’s link was opened: the creator’s code and the day. So that one person counts once, a second cookie (flowchord_ref_seen) remembers which codes your browser already counted, and we keep a one-way fingerprint of your connection’s IP address for that creator, made with a secret key — never the address itself — and delete it after 60 days. It cannot be turned back into your address and says nothing else about you.
• Creators: if you join the creator program, we keep your name, your email address, your referral code, your commission plan and the commissions and payments made to you. We pay you through Wise: the account you are paid into (for example a Pix key or a bank account) is kept by Wise, and we keep only Wise’s reference to it and a label with its last characters. We never store bank or card numbers.
• Your creator agreement: when you accept the Creator Program Agreement in the app, we keep a record of it — the full name you typed as your signature, your email address, your country, your referral code, the deal it states, its version and language, and when you accepted it — and file a signed copy (a PDF) in FlowChord’s Google Drive. To set up how you are paid, we give Wise your name and email address; Wise then asks you directly for the account you want to be paid into.
• Your Wise email: if you ask to be paid at another email address than your account’s, we email a six-digit code to that address and keep it only once you type the code back — with when you last changed it and how many times. Until then we keep the address you asked for and a one-way fingerprint of the code, never the code itself; the code stops working after 15 minutes or five wrong tries. We then give Wise that address instead of your account’s, email your account’s address that it changed, and hold your payments for a few days after the change.
• Joining and reminders: when you publish your site for the first time, we record that you accepted the creator program’s terms, which version and when, with that publication. When you become a creator, FlowChord’s operators get an email with your name, email address and referral code, and a message with your name and referral code in their team chat (Slack). While your agreement is unsigned or your Wise account is not set up, we email you a reminder at most once a week, six times at most, and keep how many we sent and when.
• Creators see how many people opened their link, signed up and paid through it, and how much they earned, with each customer shown only as a code — never who those people are. For the Practice Fund, they see each month the minutes practiced on their videos and how many students practiced them, never who.

2.8 Your messages

If you write to us — by email or from the Help Center’s contact page — we keep the message and our reply. From the contact page we receive what you write, the page you came from, its language, and your browser and the country of your connection; if you are signed in, your account’s email and user ID; if not, the name and email address you give us, which we use only to answer you.

2.9 Your brand

• Brand profile, if you fill it in on the Your brand page: your logo, brand name, description, category, country and city, the language of your content and your website. It is your public identity, not your legal details.
• Business contact: a contact name, a business email and a phone, with its country code. They are never shown on your videos.
• Channels: the Instagram, YouTube and TikTok profiles you add — you give only their address or handle; their name, picture and audience count are what Instagram’s and YouTube’s official APIs answer for them, with the date we read it. We never take a count you type: where a platform answers nothing (TikTok always), there is no count.
• Sponsor authorization: each time you grant or take back the authorization in section 5 — which purpose, which version of its text, which contact details it covers, and when.

We do not collect your card or other payment details (they go only to Stripe), your precise location or your contacts.

2.10 Your site

• Your site, if your plan includes one and you set it up on the Site page: its address (yourname.flowchord.studio), the words you add, its language and whether it is published. It shows your brand’s public identity (section 2.9) — never your business contact.
• What you publish on it: a copy of each video you choose to publish, with a picture of its opening and a copy of the same cut without FlowChord’s chords, lyrics and tab (the practice player plays it), and a copy of each chord sheet (the song’s facts, chords and lyrics). They are copies: your project stays private. We record each publication and withdrawal — what, from where, under which text, and when.
• Students who record along with it: a student whose plan includes recording along (section 2.12) can copy a video you published, with its chords, lyrics and tab, into a project of their own, and keep it and the videos they make with it. That copy is theirs: it is not removed when you take the video off your site, when your plan ends, or when you delete your account.
• Your banner and your courses: the banner picture you upload, and for each course you add, its address, name and description, and a copy of the picture its page shows. To read a course’s page, our server visits the address you give, as a browser would; it sends that page nothing about you.
• Your site in other languages: your site’s words (headline, intro, your brand’s About text, the descriptions and course names) are sent to OpenAI to be translated into English, Portuguese and Spanish when you change them, and the translations are kept with your site. Song titles and chord sheets are not sent.
• Captions of the videos you publish: the sound of each video you publish on your site is sent to OpenAI, which transcribes what is said in it; what you say (never the song) is translated into English, Portuguese and Spanish and kept with the video as its captions.
• FlowChord’s showcase, only if you turn on “Appear in the showcase” on the Site page (it is off until you do): we keep the instruments, styles, lesson languages and short bio you add there, and show your card — your brand name and logo, those details, and how many followers and videos you have — to everyone who uses Discover in the app, and on FlowChord’s public creators page on our website, which search engines can index. Which creators are featured each day is drawn from how recently they published videos, never from data about you. Each video’s level and the moment its preview starts are what you set. While Discover has too few videos practiced to rank them, it shows every signed-in user every video published on a site that is up — yours too, whether or not this is on — newest first, with your brand name, logo, styles, how many videos you have and your latest posters, and finds them in its search; these are the videos anyone can already see on your site. Turning it off takes your card, details and featured place out of Discover at once and you out of the public page at its next update. The students’ song requests you see there are counts, never who asked.
• Visits to your site, measured as section 2.11 describes, with no tracker and no cookie: you see them only as totals — pages seen, visitors, visits, the views of each video, how far they were watched and which parts of it were played, countries, where visits came from (by platform, such as Instagram or YouTube), devices, how many viewers were signed in to FlowChord and on which plan, and the accounts made after a visit, by video and by country — each count shown as its number, however small. You never see who visited, watched or signed up. Each video’s number of views is also shown on your site, to everyone who visits it.

2.11 Visiting a creator’s site

When you visit a creator’s site (name.flowchord.studio), FlowChord measures the visit so that the creator — and FlowChord — can see the site’s audience as totals. No cookie is set and nothing is stored in your browser for it:

• What is recorded: the pages you see, when you start a video, whether you watched at least 3 seconds of it, how far through it you got and for how long, which twentieths of it (each 5 % of its length) you played, a video that fails to play, a chord sheet read, a press on the sign-up button, and a search (as how many results it found — never what you typed).
• With it: your approximate country (read by Cloudflare from your connection; your IP address itself is never kept or sent), the site you came from (its address only, never the page, named by its platform when it is Instagram, YouTube, Facebook, WhatsApp or TikTok), the campaign tags a link may carry, and your device type, browser and operating system as families (for example “mobile”, “Safari”, “iOS”).
• A code instead of you: to count a visitor once a month, our server makes a one-way code from your connection, your browser and the site, with a random key that changes every calendar month and is deleted when the month ends; after that, nobody — not even us — can link the code back to a connection. The code is different on every creator’s site.
• If you are signed in to FlowChord, have accepted analytics (section 8) and your browser does not send Global Privacy Control, our server reads your session to note that the visit came from a signed-in account and which plan it had at that moment (for example Criador, or none). The code is then made from your account instead, with the same monthly key. For the visit itself, your account ID, name and email are not sent, and the creator sees only totals; what you do in the practice player is the exception section 2.12 describes.
• These records are sent to PostHog (section 5) with no name, email, account or address. Crawlers are not counted.
• On the site itself, each video shows how many times it was watched: one total of everyone’s views, never who watched.
• If you then create an account, the flowchord_site cookie (section 9) tells us which creator’s site you came from, the video you last watched there and whether you pressed its sign-up button, and we keep with it the country of your connection at that moment (two letters, read by Cloudflare). The creator sees this only as counts, and a video or a country only once ten accounts or more came from it.

2.12 Practicing on a creator’s site

When you practice with a creator’s video in the practice player:

• Your clips, if you save one: its name, the stretch of the video, the speed and the key, which video and creator’s site it is from, and when you saved it.
• The videos you opened to practice, while your account counts its free ones: which video and when you first opened it.
• Where you are in each video you practice: the point you stopped at, when you first and last opened it, how long you practiced it, and the video’s title and creator’s site as they were then, so your Home can take you back to it.
• Your practice time, for the Practice Fund, if you subscribe to the Student plan: how many seconds you practiced each video each day, filed under the plan payment whose month they fall in, and whether the video’s creator could take part in the fund that day. We use it to share 30% of that payment among the creators whose videos you practiced (Terms of Service, section 19). Creators see only totals — the minutes practiced on their videos and how many students practiced them — never who.
• Recording along, if your plan includes it: the project it makes is yours like any other (section 2.2). The creator’s video is copied into it as its song, with the creator’s chords, lyrics and tab; your take is stored as any upload. Nothing of it is sent for analysis.
• Your voice, if you turn it on: it is recognised by your browser on your device, and offered only where the browser does so. Neither the sound nor the words leave your device; we receive only which command it was, as analytics (section 2.5).
• How you practice, measured on the creator’s site as section 2.11 describes: which actions you took (a repeat, a speed or key change, a voice command’s name), how long the video played, never what you said or typed.
• Signed in, with analytics accepted (section 8): what you do in the practice player is recorded with your account’s user ID, as the app’s analytics are (section 2.5), not with the anonymous code of section 2.11. If a creator’s site brought you to create your account, the visits your connection and browser made to that site that month, before you signed up, are linked to your new account too.

FlowChord’s exercises (in Play): once you have played an exercise, the tempo you last played it at and the fastest, for a scale the key and the place on the neck you left it in, how long you practiced it, and when you first and last practiced it, so you can pick it up where you left it. An exercise only opened and never played is not recorded. An exercise’s music is made in your browser. When you play Placar, the microphone is listened to in your browser only — nothing is recorded or sent — and we keep each round’s score: the tempo, the rating, the points, the longest run, how many strokes were on time, late, early, missed or one too many, and one mark per stroke for the round’s grid; the newest 50 rounds of each exercise. When you record yourself over an exercise, the recording becomes one of your projects, kept like any Play Along recording. How you look at the exercises (the guitar’s view and its two switches) stays on your device (section 9).

2.13 Following creators and liking videos

If you follow a creator or like a video on a creator’s site, we keep which site you follow or which video you liked, and when. How many accounts follow a site and how many liked each video are shown on that site to everyone; who they are is shown to no one — not to the creator, not to other visitors. You can stop following or take a like back on the site at any time. When you follow from FlowChord’s Discover, we also keep where you pressed Follow (the feed, search, a creator’s profile), so that the creator can see how many followers FlowChord’s showcase brought them — as a count, never who.

2.14 Discover and song requests

Discover shows you the videos of the creators you follow, the videos most practiced that week on the sites in FlowChord’s showcase (the same list for everyone who reads your language; while there are too few practiced to rank, every video published on creators’ sites instead, newest first, with each creator’s brand), the featured creators and what you search for. It is not personalised: we use nothing you did to choose what you see. Specifically:

• When you last opened your Following feed, so that the videos published since are marked as new.
• What you search for is not kept. We record only whether a search found anything, roughly how much, and which filters were on — never the words.
• Song requests: when you ask for a song that is not there yet, we keep which recording you chose (its title, artist and a link to hear it, from a music catalogue or the streaming link you pasted), the instrument you named, if any, and when. Every creator can see the song, the instruments and how many people asked for it — never who. When a creator links a video to it, the video appears in your Following feed, and we email you once about it unless you turned those emails off. A request no video answered is deleted 90 days after you made it, or as soon as you withdraw it.
• Discover emails: the daily summary of new videos from the creators you follow is sent only if you turn it on in Account › Notices, at most once a day and only when there is something new. Every one of these emails has a link that stops them without signing in.

2.15 Working on a project with other people

The owner of a project on a plan that includes sharing can invite people to work on it by entering their email addresses. To do that, we keep:

• The invite: the address it was sent to, who sent it, which project, its state (waiting, accepted, declined, cancelled or ended) and when. We email the invite to that address once, and again only when the owner sends it again; the link in it ends after 14 days. Nothing changes for the person invited until they accept, signed in with that address.
• Who is in the project: once someone accepts, which project they joined and when. The owner and the people in a project see each other’s name, email address and profile picture, and who is editing it at the moment.
• The owner’s saved people: every address the owner has invited, and the account it belongs to once someone accepts, so that the owner can pick them again. The owner can forget anyone in the Share dialog.

Everything in a shared project — its files, chords, lyrics, tab and settings — stays the owner’s, whoever changes it, and counts against the owner’s storage; anything that costs money in it is charged to the owner. A person who leaves or is removed loses access at once; what they changed stays in the project.

3. Work done on your device

A large part of FlowChord runs in your browser and does not send your content to anyone:

• preparing files before upload when they need it (re-encoding video and audio, resizing pictures);
• extracting the audio that is sent for analysis;
• lining up recordings that were not started together, and finding obvious restarts in a take;
• reading text from PDF and text sheets that contain text;
• choosing where to place chords and lyrics so they do not cover the important parts of the picture — when the browser provides it, this includes detecting where faces are in the frame; faces are not recognized or identified, and only a coarse map of where to avoid placing things is saved with the project;
• guessing the capo position, and Play Along timing;
• in the practice player, slowing a video down, moving its key and recognising the voice commands you say; and
• rendering the exported video, which is saved directly to your device and is not uploaded to us.

4. How we use your data and on what legal basis

Service emails. A welcome email when you create an account, reminders before a free video’s files are deleted, notices before a project’s files are archived and notices of updated terms are part of the Service and are sent through Resend. They are not marketing. For each of them we keep whether it was delivered, delayed or bounced, whether it was marked as spam, and which of its links were clicked (which link, never where you went next), with your account, to know they arrive and help; we never record whether you opened one.

5. Who receives your data

We share personal data only with the service providers that help us run the Service, under their terms, and only as needed for the purposes above:

Stripe processes payments under its own privacy policy, which also covers the payment details you give it.

AI providers receive the content to be analyzed without your name or email address, and process it under their own terms for API customers. They may keep it under their own retention policies; in particular, the audio files we send to Music.AI stay in its storage, because we do not currently delete them after the analysis. Error reports are the exception: Anthropic’s Claude reads them as Sentry keeps them, with your user ID but not your email.

We may also disclose personal data when the law requires it or to answer a valid order from a court or authority; to protect the rights, safety and property of FlowChord, our users or others; in connection with a merger, acquisition or sale of assets, with notice to you; or with your consent.

We do not sell personal data and we do not share it for targeted advertising. We do not give your content to anyone to train their models. We use the audio of your recordings and the chords and guitar tabs you correct and export to train FlowChord’s own music-analysis models — the ones that detect chords, beats, lyrics timing and guitar tabs — unless you turn this off in Preferences (section 8). These models learn what the chords of a song are, not your voice or your face; they never generate music; what they learn cannot be traced back to you or to a recording; and a recording leaves every future training set when you delete its project (what a model already learned is not undone). One exception: the notes of a guitar tab you exported — the notes our service heard in the recording, the tab it wrote and the tab as you exported it, never the recording itself — are kept as a training example even after you delete the project, until you delete your account or turn this off, and for 5 years at most (section 7).

Which song a recording is, as we find it from the lyrics heard in it — its title, artist, album, year and the address of its cover, and the corrections proposed for its lyrics — is also kept apart from your account, identified only by a fingerprint of those lyrics, and used again for another user whose recording sings exactly the same words: never your name, account, files or edits. When the song was found with confidence, we also keep its title and artist with a fingerprint of the short runs of words your recording sang that the song’s published lyrics also contain — scrambled codes, never the words themselves, and nothing only your recording sings — so that another recording of the same song is recognized without asking an AI provider.

Your projects are private: no other user can see them. Three exceptions: fingerings you keep may be counted, without your name or account, in the suggestions other users see for the same chord; the chords, beats, tempo and key our provider detects in a recording, and the guitar notes our own transcription service hears in it (section 1), are also kept apart from your account, identified only by a fingerprint of the audio or file sent for analysis, and given to another user who sends exactly the same audio — never your name, account, files, lyrics or edits, and only to someone who already has that same recording; and your profile photo is stored at a web address that anyone who has the address can open, although we do not publish it anywhere.

Sponsors. Saving your brand is not an authorization. Only if you turn on “Let brands find you” on the Your brand page do we use your brand profile and your channels, with their audience, to evaluate sponsorship opportunities and present your profile to brands and sponsors interested in a partnership with you; and we give an interested sponsor your business email or your phone only if you also allowed each of them. Never your account’s email, your projects or anything else of yours. We record each grant and each withdrawal — which text, which contact details, when — and stop using your profile for this as soon as you take the authorization back. Your brand logo and your channels’ pictures are stored like your profile photo, at a web address that anyone who has it can open.

6. International transfers

FlowChord is operated from the United States. Your account, your projects and their files are stored in the United States, and the providers in section 5 process your data in the countries below. These countries may not offer the same level of protection as yours.

Each provider receives your data only for the purpose given in section 5, for as long as it provides that service to us, and keeps it as section 7 says. The providers that process data on our behalf do so under data processing terms that bind them to use it only on our instructions, to protect it and to tell us of incidents that affect it, and for people in the European Economic Area, the United Kingdom and Switzerland those terms include the European Commission’s standard contractual clauses and their UK and Swiss equivalents. Stripe, Google and Meta, which also decide how they use some of this data, apply the standard contractual clauses approved by Brazil’s National Data Protection Authority (ANPD, Resolution CD/ANPD nº 19/2024) under their own terms, and we are adding those clauses to our contracts with the other providers. Music.AI is the exception: we have no data processing agreement with it, and its terms, which make it our processor, also let it use content to improve its products and include no transfer clauses.

You can ask us, Bahia Ventures USA LLC, at [email protected], for a copy of the clauses that apply to your data, in Portuguese and free of charge; we answer within 15 days. The measures that protect your data are in section 10, and your rights, including the right to petition the ANPD, in section 8.

7. How long we keep data

Deleting your account. When you delete your account in the app, or ask us to, we delete your profile, your projects and all their files, your analysis results and your fingerings; we remove your address from our email provider and from the waitlist; and we delete your analytics profile and its events. Error reports, session recordings and server logs are not deleted one by one: they are removed when their period above ends. Your payment records are kept for the period set out above, and any balance left in your wallet is handled as the Terms of Service say.

We may keep some data longer when the law requires it or to establish, exercise or defend legal claims.

8. Your rights and choices

Depending on where you live, you have the right to:

• confirm whether we process your data and access it;
• correct incomplete, inaccurate or outdated data — you can edit your profile in the app;
• delete your data — you can delete projects and your account in the app, or ask us to delete your account;
• receive your data in a portable format — “Download your data” in the account menu saves a file with your profile, your projects with their chords and lyrics, and links to your files;
• know with whom we share it;
• withdraw consent you gave — the sponsor authorization at any time on the Your brand page — and object to processing based on our legitimate interest;
• ask for anonymization, blocking or deletion of unnecessary or excessive data, and for a review of decisions made only by automated processing that affect your interests; and
• complain to a data protection authority — in Brazil, the National Data Protection Authority (ANPD).

You can download your data and delete your account yourself, from the account menu in the app. To exercise these or any other of these rights by email, write to [email protected] from the email address on your account. We may need to confirm your identity before acting. When you ask us by email to delete your account, we confirm the request by email and then delete it as described in section 7. We will answer within the time limits set by law.

You can unsubscribe from waitlist emails through the link in any of them. You can also block or delete cookies and browser storage in your browser’s settings; if you block those needed for signing in, the app will not work.

Improving FlowChord’s models. In the app’s Preferences you can turn off “Use my corrections to improve FlowChord”. From then on, your recordings and corrections are left out of every training set we build, and the training examples of your guitar tabs (section 7) are deleted. Models trained earlier are not retrained without them.

Analytics and session recordings. Nothing is sent to our analytics provider until you choose: the first time you visit, we ask whether we may measure how the Service is used, and Accept and Decline are offered side by side. If you decline, or until you choose, no analytics runs on the website or in the app. Separately, while you are signed in to the app, our server asks PostHog which features still being tried out your account may use, sending your user ID and email; this happens whatever your choice, and records nothing of what you do. Signing in to the app — where the sign-in form says that continuing agrees to this policy — is a yes to analytics and to session recordings, unless you declined before; you can turn recordings off at any time with “Record my sessions” in the app’s Preferences, and that choice is kept when you sign in again. You can change either choice at any time — in the app’s Preferences, or through “Privacy choices” at the foot of the website — and when you turn analytics off, what our analytics provider kept in your browser is removed. Your choice is kept in a cookie (flowchord_consent, section 9) for six months, after which we ask again. The Service works the same whichever you choose.

If your browser sends a “Global Privacy Control” signal, we treat it as a decline: we do not ask, and no analytics runs unless you turn it on yourself in the app’s Preferences. We do not sell personal data or share it for targeted advertising. We do not respond to “Do Not Track” signals.

9. Cookies and browser storage

A creator’s site sets no analytics cookie and stores nothing in your browser to measure visits (section 2.11).

We also load fonts from Google Fonts, which receives your IP address and browser information when it delivers them.

10. Security

We protect your data with measures that include encrypted connections (HTTPS), private file storage that can only be opened through links that expire within a week, database rules that limit each account to its own data, sign-in without passwords stored by us, and hiding text fields and the text you write in session recordings. No system is completely secure. If an incident affects your personal data, we will notify you and the authorities as required by law.

11. Children

FlowChord is intended only for people who are 18 or older. We do not knowingly collect personal data from anyone under 18. If you believe a minor has given us personal data, write to [email protected] and we will delete it.

12. Changes to this policy

We will update this policy when the Service or the law changes. If a change is material, we will tell you by email or in the app before it takes effect. The date at the top shows the last change.

13. Contact

Bahia Ventures USA LLC — [email protected]. This address is also our channel for requests from data subjects under Brazil’s General Data Protection Law (LGPD).