Legal
Privacy Policy
Effective October 15, 2026
This Privacy Policy explains how Jamigo, LLC (“Jamigo,” “we,” “us”) collects, uses and shares information when you use Jamigo — our website at jamigo.io and the Jamigo app, including on the web (together, the “Service”). Jamigo is a network for working musicians and the people who hire them: profiles, availability, gigs, bands, messages, set lists and coordination on the day of a gig.
Questions? Email us at support@jamigo.io.
¿Lees en español? Lee esta política en español.
Using JAMIGO from Mexico? Read our Privacy Notice for Mexico too (the Spanish aviso de privacidad governs there).
1. Information we collect
Information you give us
- Account information. The mobile phone number you sign in with, the language you choose, and your email address: new accounts add and confirm one when they sign up, and accounts created earlier may add one. We use your email address for security notifications about your account, account recovery and support, membership emails (the confirmation of the launch offer’s terms when you start a membership under it, and the receipts and other emails Stripe sends for us), notices about changes to our Terms and this policy, and setting up an authenticator app. When you start a membership, Stripe receives your email address, so that those receipts and emails reach you. We don’t sell your email address, and we don’t show it to other members.
- Your agreement to our Terms, and your age. When you create an account, we record that you confirmed you are 16 or older, agreed to our Terms of Service and acknowledged this policy, with the date and time, the language you read it in, and which version of the Terms and of this policy (by effective date) you were shown. Before you first start or change a membership, pay through Jamigo, book a paid lesson, set up JamigoPay, put gear up for sale, offer lessons, publish a paid tutorial or a bundle, put a price on a free tutorial you already published, or apply to the Creator Program, the app asks you once to confirm that you are 18 or older (if you set up JamigoPay before we asked, the JamigoPay screen asks you, because nobody can pay you through Jamigo until you confirm); we record that you did, with the date and time, where you confirmed it (the launch offer’s checkbox or the app’s own confirmation), and the version and language of the words. If we tell you about new Terms in the app or by email, we record when we told you, when you first saw the notice, whether you accepted the new Terms, and the date they apply to your account.
- Profile information. Your name, Jamigo handle, profile photo and cover image, bio, city, instruments, genres, the languages you speak, experience, rates and working terms, how far you travel, the equipment you bring, and the ways you prefer to be paid.
- Payment methods. The ways you accept payment directly, outside Jamigo, if you add them: a Zelle, Venmo, Cash App, PayPal, Apple Cash, Mercado Pago or Wise handle (for example a username, $Cashtag, email address or phone number) or, for another service, what someone needs to pay you there. Payment Methods don’t accept bank account numbers, IBANs, CLABEs or card numbers; to be paid into a bank account through Jamigo, use JamigoPay, where Stripe collects your bank details. We store your payment methods and a log of each time someone opens one in full.
- Availability and work. The days you mark as open, booked or blocked; the gigs, roles and jobs you post or apply for, including audition recordings; offers and bookings, including the pay you agree on; your status on the day of a gig; and the details you add to a gig, such as the venue, times, dress code, meeting point, parking notes, and a client’s name and phone number.
- Bands. Band profiles, members and their roles, rehearsals, songs and repertoire notes, set lists, dress codes, and band photos and videos.
- Messages. What you send in gig, band, group and gear conversations: text, photos, videos, voice notes, audio files, PDFs, replies and reactions.
- Posts and other content. Posts, comments, likes and follows; clips and videos; gear listings; tutorials; reviews and ratings; and vouches.
- Messages to us. If you email us, your email address and what you write.
How you heard about JAMIGO
While you sign up, we ask “How did you hear about JAMIGO?”. You choose one of 11 answers — for example a friend or bandmate, social media, a venue, an event, or the JAMIGO team — and you can add a sentence and a referral code. The question is required at sign-up, unless a creator’s referral code already applies to your account and so answers it. Accounts that finished signing up before the question existed are not asked.
We save your answer once, when you give it, together with: the sentence you added; the referral code that
applies to your account, or one you typed that did not apply; the campaign details of the link that first brought
you to the app (its utm_source, utm_medium, utm_campaign,
utm_term and utm_content, if it had any); and the kind of page you arrived on (for
example “a profile”, never which one). It is not shown to other members, and Jamigo’s staff see it only as counts.
Your answer is used only by Jamigo to understand how people find us; it is never shared with or sold to
advertisers or other third parties. The answer and the referral code are kept until you delete your account; the
sentence, the campaign details and the kind of page are deleted 13 months after you answer. If Jamigo’s support
team corrects the referral code on your account, the code saved with your answer is corrected too. If it removes
a code, the code stays saved with your answer as one that did not apply, and if that code answered the question
for you, your answer becomes “Artist / creator”.
Referral codes and the Creator Program
If a creator’s referral code applies to your account (Terms, section 7), we keep one record of it: the creator, the code, whether it came from a link, was typed or was added by Jamigo, when it applied, and whether and when it qualified for commission. If a code applies while you sign up, the app shows it to you then; at any time, you can ask Jamigo’s support team which code your account uses, and they can correct or remove it if it is wrong. When you pay Jamigo — for a membership, or through Jamigo’s fee on something you buy — we record the revenue that counts toward the creator’s commission and the commission worked out from it.
If you are a creator, we keep your application (including the note you wrote), our decision, your code, and the commission that accrues to you.
Memberships and payments
- Your membership. Your plan (Free, Jamigo Member or Jamigo Band), its billing period, status and dates — for example when a free trial ends, when it renews or when it was cancelled — the payments and invoices Stripe reports for it, and the identifiers Stripe gives your customer record and subscription. If Jamigo gives you a complimentary membership, we record it with the reason.
- Your card. You enter your card on Stripe’s secure page, and Stripe keeps it. Jamigo never receives or stores your full card number or security code. We keep only the card’s brand (for example, Visa), its last four digits and its expiry month and year, so we can show you which card is on file.
- Your agreement to a membership’s charges. When you take the launch offer, the app asks you to confirm that you are 18 or older and to agree to the membership’s charges before you add a card, and we keep a record of that agreement: your account; the date and time; the plan, price and billing period; the date of the first charge; the exact wording you were shown and agreed to, with its version and language; the wording shown on Stripe’s page; the effective dates of the Terms of Service and of this Privacy Policy at that time; the Stripe session; what happened next (for example, that the membership started, or that the offer closed first); and when we emailed you the confirmation. If you switch plan during the offer, a new record supersedes the earlier one; we keep both. The record does not include your IP address, your device or a screenshot. A membership that does not start under the launch offer — the 14-day trial from November 1, 2026, a restarted membership, or one at full price — has no such record; Stripe keeps its own records of its payment page and the charge.
- Purchases and sales. If you buy or sell through Jamigo: the order — what was bought, from whom, the price, Jamigo’s fee, how it was paid, and any refund or dispute. You pay for a purchase on Stripe’s page, or in Stripe’s payment form in the app, by card or another method Stripe offers there, such as a bank debit (ACH); Jamigo does not receive your card or bank account number.
- JamigoPay. If you set up JamigoPay to get paid, Stripe collects your identity, tax and bank details on its own pages; Jamigo does not receive them. Stripe tells us only what we need to run JamigoPay: the identifier of your Stripe account; whether it can receive payments and payouts, its country and currency, and whether Stripe still needs something from you; the last four digits of your bank account; and the payouts and transfers made to you (amounts, dates and status).
Sign-in and authentication
Jamigo signs you in with your phone number instead of a password. When you ask for a code, our text message provider sends a one-time code to your number by text message and checks the code you enter. Our authentication provider keeps a record of sign-in events, such as when a code was requested or used and the IP address the request came from. While you are signed in, a session token is stored on your device — in your browser’s local storage on the web — so that you stay signed in. Signing out removes it from that device.
Information collected automatically
- Devices. An identifier for each app installation or browser you use, its platform (web, iOS or Android) and when it was last used, so that we can manage your signed-in devices and notifications. In our iPhone and Android apps, if you allow notifications, the device’s push notification token.
- What you watch. When you view a post, we record that you viewed it and how long you watched, so that we can count views.
- Product usage. A short list of product events — for example finishing a step of sign-up, choosing a membership, publishing your availability or sending an offer — linked to your account, with the app version and platform. Some are recorded by our servers, such as when a membership starts, with its plan and billing period. These events never include message text, files, location, contact details, or card or bank details; their details are limited to short labels and numbers. Before you sign in, the app holds events only in memory (at most 10, for at most an hour) and sends them once you do. These are our own records: no analytics company receives them.
- Crash and error reports. When Jamigo hits an error or crashes — in a browser or in our iPhone and Android apps — it sends a report to Sentry, our error-monitoring service. A report says what went wrong and where in our code, with the app version, the platform, the type and version of your browser or device and its operating system, your language and time zone, and your Jamigo account’s internal identifier — not your name, phone number or email address. Before a report is sent, we remove page addresses, request headers and cookies, and remove or mask anything that looks like message text, an email address, a phone number, a location, an access token or a similar detail; some crash reports from our iPhone and Android apps are sent without that step. The app also tells Sentry when a session starts and ends, with your account’s identifier and your browser or device type, so that we can see how often it crashes. Like any service your device connects to, Sentry sees your IP address when a report arrives. Sentry is configured not to store IP addresses and not to keep a location worked out from them, so reports are stored without your IP address or location.
- Technical logs. Like most online services, our hosting providers automatically record technical information about each request to the Service: the IP address, browser or device type, the date and time, and the address requested — which can include a referral code or campaign details carried in a link. Our database provider’s logs also record an approximate location worked out from the IP address. Opening one of our account emails loads our logo from jamigo.io, which is recorded the same way.
- Local storage. Your browser or device keeps: the sign-in session described above; your preferences, such as language and theme; while you sign up, a referral code and campaign details from the link that brought you, for up to 7 days (the first link wins), removed once your account has them; and, on jamigo.io, the random visitor identifier described below. We don’t use cookies for advertising or tracking, and we don’t use third-party advertising or analytics tools: our analytics are our own, described in this section, and crash reports go to Sentry.
Visits to jamigo.io
The home pages of our website, jamigo.io and jamigo.io/es, count visits and clicks for us without identifying you.
They send our own server three kinds of events: a page view, a click on a button that opens the Jamigo app, and a
click on “Sign in”. Each event carries a random identifier made in your browser; the page’s language and address;
which button was clicked; whether the link that brought you carried a referral code (yes or no, never the code);
and, with the page view, the link’s campaign details (utm_*). The identifier is kept in your
browser’s local storage, not in a cookie, and is reused for up to 30 days; after that, your next visit gets a new
one. We count one page view per identifier per day.
We don’t store your IP address or device details with these events, and we can’t connect them to a Jamigo account; our hosting providers’ request logs still see your IP address, as they do for any request. If your browser sends Global Privacy Control or Do Not Track, the pages send no events and make no identifier. Either way, a referral code or campaign details in the link you arrived with are passed on to the app when you click through, and kept with your account if you sign up (see “How you heard about JAMIGO”). We delete these events after 13 months.
Location
Jamigo uses your device’s precise location only if you choose to share it with your band for a specific gig. When you do, we keep only your most recent position — never your route — and only the members of that gig’s band can see it. Sharing stops when you turn it off, when you arrive, or when the time you chose runs out (never more than eight hours), and your coordinates are then deleted. Jamigo does not collect location in the background, and on the web, sharing works only while the page is open.
When place search is switched on and you look up your city or ZIP code, or a gig’s venue or address, what you type is sent from our servers to Geoapify, a place-search service, to suggest matching places. Geoapify does not receive your name, your account or your IP address. The place you choose — its name, city, region, postal code, country, time zone, coordinates and Geoapify’s identifier for it — is saved on your profile or on the gig. If place search is off or unavailable, what you type is saved as you typed it.
The city on your profile, which you choose, is used to show approximate distances, for example in the Market. It is not your device’s location.
2. How we use information
- To create and secure your account and sign you in, including sending one-time codes by text message.
- To keep a record of your agreement to our Terms and of your confirmation that you are old enough for the features you use: 16 for Jamigo, and 18 for paid and marketplace features.
- To run the Service: show profiles and availability, and operate gigs, bookings, bands, set lists, Live Mode, messages, the Market, gear listings, lessons and tutorials.
- To run memberships: start free trials and memberships through Stripe, show your plan and the card on file, change or cancel your membership when you ask, and send you the confirmation, receipts and reminders.
- To keep a record of what you agreed to when you started a membership under the launch offer, so that we can answer a question or a dispute about a charge and show that we followed the law.
- To process purchases between members and pay sellers through JamigoPay.
- To run referral codes and the Creator Program: apply a code, work out whether a referral qualifies, work out commission from what Jamigo received, and keep creators’ commission records.
- To learn how people find Jamigo, from answers to “How did you hear about JAMIGO?”, campaign details and the anonymous visit counts on jamigo.io, which our staff see only as counts.
- To help people find each other — for example by instrument, genre, city and availability. Social activity such as follows and likes is never used to rank who gets hired.
- To suggest places when you look one up, and to show approximate distances.
- To show reputation: completed gigs, verification steps and reviews make up the reputation other members see.
- To keep Jamigo safe: prevent fraud and abuse, enforce our Terms of Service, and respond to reports.
- To understand how features are used, through the limited product events described above, and to find and fix problems, through crash and error reports.
- To communicate with you about the Service, including changes to our Terms and this policy, and respond to your requests.
- To comply with the law.
We do not sell your personal information, and we do not use it for advertising.
3. How information is shared
With other people on Jamigo
Jamigo works by sharing some information with other members. What they can see depends on what it is:
- Your profile — your name, handle, photos, instruments, genres, city, rates and terms, bands, posts and reviews — is visible to people signed in to Jamigo. Profile photos and cover images are stored so that anyone with their link can view them.
- Availability. When you mark yourself free, people looking for musicians can see that you are available and message you. Your calendar itself — bookings, rehearsals and blocked days — is not shown to them.
- Messages are visible to the members of that conversation. Band chat, including its photos, voice notes and files, is visible to the band’s current members. Attachments are stored privately and opened through links that expire after a few minutes.
- Your phone number is not shown on your profile. It is shared with the other side of a confirmed booking — the musician, or the person who hired them — while the booking is active and for 48 hours after the gig is completed.
- Your payment methods are shown, shortened, only to people you work with: the other side of a booking while it is booked or under way and for 30 days after the gig is completed; the active members of your active bands; and the other side of an open direct conversation in which you have written (never a gear conversation, and never when either of you has blocked the other). They see the full handle only when they open it, and we log each time they do.
- Reviews become visible once both people have submitted theirs, or after seven days.
- Location you choose to share for a gig is visible only to that gig’s band, as described above.
- Tutorials you publish, and their reviews, can be seen by anyone, including people who do not have an account.
- Your membership — your plan, whether you have one, and your card — is not shown to other members.
- Referral codes. If your account counts for a creator, the creator sees only their own totals — never your name or what you paid. When a creator has very few referrals, a change in those totals could let them work out that someone they invited started paying. A creator’s code is usually made from their handle, and is visible wherever they share their link.
- Verified mark. Our staff can mark a profile as verified after confirming who the person is themselves, for example on a video call. We record that it was done, when and by whom; we don’t keep a copy of any ID document. The mark is removed when you delete your account.
With service providers
We use service providers that process information on our behalf, only to provide the Service. Each receives only what it needs:
- Supabase — our database, sign-in, file storage, real-time messaging and the server functions that run the Service, hosted on Amazon Web Services in the United States. It holds the information described in this policy. Its request logs record the IP address, browser or device type and approximate location of each request.
- Vercel — hosting for our website and web app. Its request logs record the IP address, browser type and the address requested.
- Twilio — sign-in codes by text message (Twilio Verify). Twilio receives your phone number, sends the code and checks the code you enter.
- Stripe — payment processing. For memberships, Stripe receives your card details (entered on Stripe’s page) and the name and billing details you enter there, and from us your name on Jamigo, your confirmed email address, your language, an identifier for your Jamigo account and the plan you chose; it charges your card, sends your receipts, trial reminders and payment emails, runs the billing page the app opens, and helps prevent fraud. For purchases and gig pay, Stripe receives what you enter on Stripe’s page or payment form (card or bank account details, and any email or billing details it asks for), and from us the amount and an identifier for the order or booking; for a purchase, also what is being bought and the seller’s name on Jamigo, and, on the web, an identifier for the buyer’s Jamigo account. For JamigoPay, we give Stripe your email address, your name on Jamigo and an identifier for your Jamigo account to open your account, and Stripe collects your identity, tax and bank details (for example your legal name, date of birth, address, tax identification number and bank account) to verify who you are, meet its legal obligations and pay you. Stripe handles this information under its own Privacy Policy.
- Resend — delivery of our emails, to the email address on your account: account emails from auth@jamigo.io (email confirmation codes and security notices; a notice about a change of email address names both the old and the new address), and emails from notifications@jamigo.io (the confirmation of the launch offer’s terms when you start a membership under it, with the plan, price, dates and how to cancel, and notices about changes to our Terms and this policy). Resend receives your email address and the content of the message, and keeps a log of the messages it sends. We don’t track whether you open our emails or click their links.
- Sentry — error and crash monitoring, in the United States. Sentry receives the crash and error reports and session signals described in section 1. It sees your IP address when they arrive but, as we have set it up, does not store it.
- Geoapify — place search, when enabled. Geoapify is run by Keptago Ltd, of Cyprus, and hosts its service in data centres in the European Union. It receives, from our servers, the text you type when you look up a city, ZIP code, venue or address.
- Expo, Apple and Google — push notifications in our iPhone and Android apps, when enabled and if you allow them. Expo, our app platform, receives your device’s push token and each notification’s title and text, which can name another member, a band, a gig or an amount (never the text of a message), and passes them to Apple Push Notification service or Google’s Firebase Cloud Messaging to deliver. Our apps also check Expo for updates when they open, which shows Expo your IP address and app version.
- Mux — video hosting for performance clips, when enabled. Mux receives the video, and the IP address of whoever uploads or plays it. A clip’s playback link works for anyone who has it, and a clip you remove can still be played from its link until our cleanup deletes it from Mux, within about an hour.
- Microsoft and Proofpoint — our email hosting (Microsoft 365) and email security (Proofpoint). If you email us, they receive your email address and your message.
- Google Fonts — our website at jamigo.io loads its typeface from Google, which receives your IP address when the page loads.
If you choose to open a location or directions from Jamigo, it opens in a maps service such as Google Maps, which handles that information under its own privacy policy.
For legal reasons
We may disclose information if we believe in good faith that the law, a subpoena or other legal process requires it, or that it is necessary to protect the rights, property or safety of Jamigo, our members or others.
If Jamigo changes hands
If Jamigo is involved in a merger, acquisition, financing or sale of assets, information may be transferred as part of that transaction, and it will remain subject to this policy.
4. Text messages (SMS)
We use your mobile number to send you one-time codes by text message when you create an account or sign in, so that we can verify your number. These messages are transactional: Jamigo does not send marketing or promotional text messages. Twilio delivers them for us.
Jamigo does not sell or share SMS opt-in data, consent information, or mobile phone numbers with third parties for marketing or promotional purposes.
Reply STOP to any message to stop receiving text messages, or HELP for help. Because your phone number is how you sign in, opting out may prevent you from signing in. See the text message terms for details.
5. Security
We use safeguards designed to protect your information, including encrypted connections (HTTPS), database access rules that limit each account to the information it is allowed to see, private storage for chat attachments, and one-time sign-in codes instead of passwords. Full card and bank account numbers for payments never reach Jamigo: you enter them on Stripe’s pages. Payment Methods don’t accept bank account or card numbers; the payment methods you add are shown in full only to the people described in section 3, and we log each time one is opened. Crash reports are cleaned before they are sent, as section 1 describes. Photos you add to your profile, posts, gear listings and chats are re-encoded before upload, which removes embedded details such as where a photo was taken; videos and other files may keep information embedded in them. No method of transmitting or storing information is completely secure, and we cannot guarantee absolute security.
6. How long we keep information
We keep your information while your account is active, and for the periods below. The table at the end of this section lists each kind of information and how long we keep it. When a period ends, we delete the information, or remove what identifies you and keep only amounts and dates where the table says so.
When you delete your account
You can delete your account in the app (You → Account and privacy → Delete account), or ask us to delete it by emailing support@jamigo.io; we may ask you to confirm that the request comes from you. When your account is deleted, we:
- first end any membership at Stripe, remove your saved card, and clear your name and email address from your Stripe customer record; then delete the card details we kept (brand, last four digits and expiry);
- remove from your profile your name, handle, profile photo, cover image, bio, city and other place details, coordinates, time zone and country, the services you list and what you joined Jamigo to do, and the verified mark;
- delete your musician details (instruments, genres, rates, experience, how far you travel, the equipment you bring, the ways you prefer to be paid, lesson formats), your availability and lesson hours, your notification settings, your tutorial progress, your reputation, the record of your sign-up steps (except the record of your agreement at sign-up and of your 18+ confirmation, which we keep as described below), and the record of what you watched;
- delete your contact details, social links, repertoire, custom instruments and genres, follows, blocks and mutes, payment methods and the log of who opened them, and your answer to “How did you hear about JAMIGO?”;
- remove your phone number and email address from our sign-in system and from its record of your sign-ins (that record is deleted after 90 days) — our sign-in provider may keep a scrambled value in their place, which we never use — and sign you out everywhere;
- delete your devices and push notification tokens, and every notification addressed to you;
- delete your reactions and likes, and remove your comments, whose text is deleted within 30 days;
- take down your posts, including posts you made for a band, and mark your clips removed;
- withdraw your pending offers, invitations, open roles and job applications; close the job postings you posted yourself (a band’s postings stay with the band); withdraw every gear listing you have for sale, so that it is never offered again, and clear the location and description of all your gear listings (a listing that is part of an order keeps its description, as the order’s record, only while the order holds it, as described below); stop offering your tutorials and bundles; and cancel your lessons that have not been paid for, and free lessons that have not started, and tell the other person (our staff follow up on any lesson that was already paid for or is under way);
- stop any location sharing, remove you from your conversations, and hand your bands to another member or close them;
- if you are a creator, close your creator account: your code stops working and is never given to anyone else, referrals still waiting to qualify no longer count, and commission already recorded stays on record, marked held (Terms, section 7.2);
- if you set up JamigoPay, delete the last four digits of your bank account that we kept; a payment to you that is already under way can still be completed, but nobody can start a new one; your Stripe account itself is not closed (Terms, section 6); and
- delete, within 30 days and usually at once, your profile photo and cover image (earlier ones included) and the files you uploaded to your posts, gear listings, auditions and tutorials. The exceptions: the photos and description of a gear listing that is part of an order are kept while the order holds it — while the order is waiting for payment (until 14 days after its payment window closes), while it is disputed, and for 120 days after it was paid (while a card payment can still be disputed), unless it is refunded in full — and are deleted within 2 days after that; a tutorial someone bought stays available to them, with its files; a band’s profile photo and cover, and photos you added to a gig’s dress code, stay with the band or the gig (the files of posts you made for a band are deleted with your other posts); and chat attachments stay with your messages, as described below.
Some information is kept after you delete your account, because other people depend on it or because we need it for accounting, tax, legal and dispute purposes, each for the period in the table below:
- an internal record of the account, with no name, contact details or profile, while other records still refer to it;
- the record of your agreement to our Terms at sign-up and of your confirmation that you are 18 or older — when and how you gave them, and the version and language of the words, nothing else about you — for 7 years after the deletion, as proof for the orders, lessons and memberships they allowed;
- messages you sent, and their attachments, which stay in the other people’s conversations, shown as from a deleted account, until that conversation is deleted as described in the table;
- bookings, orders, payments, payouts, refunds and reviews that other people depend on, and vouches you gave, all without your name;
- notifications other members already received, which may still show your name for up to 12 months after they were sent;
- your membership history and invoices, records of your agreement to a membership’s charges, a creator’s retired code and status, and commission and payment records, kept as described in the table, and the identifier of a Stripe account you set up for JamigoPay, to reconcile payments. Stripe keeps its own records of your payments under its own policy;
- product events, linked only to the account’s internal identifier; records of actions Jamigo’s staff took; records of notices about our Terms; and a record that the account was deleted, with counts only.
Deleted information can stay in our database backups for up to 30 days, until they roll off.
Records of your agreement to a membership’s charges are kept after your account is deleted. They show what you agreed to, and when. We keep them to answer a question or a dispute about a charge (including a chargeback through your bank), to meet our legal obligations for automatically renewing memberships and for payment records, and to establish or defend legal claims, and we use them for nothing else. We keep each record for 7 years after the membership it covers ends — or, for a record that never led to a membership (for example, because the offer ended first), for 7 years after it was made — and then delete it. Records of payments and payouts are kept for 7 years after the end of the tax year of the last payment, refund or payout they record; after that we remove what identifies you and keep only amounts and dates. Stripe keeps its own records under its own obligations.
How long each kind of information is kept
| Information | How long we keep it |
|---|---|
| Your account, profile, content and settings | While your account is active. When you delete your account, removed as described above, or kept without your name where this table says so. |
| The internal record left by a deleted account, with no name, contact details or profile | While other records in this table still refer to it. |
| Your agreement to our Terms at sign-up; your confirmation that you are 18 or older | While your account exists, and for 7 years after you delete it (when and how you gave them, nothing else about you); then deleted. If you confirmed your age in the launch offer’s checkbox, the words you agreed to are also part of that agreement’s record, kept as described below. |
| Records of notices about our Terms (who was told, when, and who accepted) | 7 years after the notice, then deleted. |
| Files you uploaded, after you delete your account | Deleted within 30 days, usually at once. Photos of a gear listing that is part of an order: as the next row describes. A tutorial someone bought stays available to them, with its files. A band’s profile photo and cover, and a gig’s dress-code photos, stay with them; chat attachments stay with the messages. |
| A gear listing that is part of an order, after you delete your account | No longer offered, and its location cleared, at once. Its description and photos stay, as the order’s record, while the order holds them: while the order is waiting for payment (until 14 days after its payment window closes), while it is disputed, and for 120 days after it was paid, unless it is refunded in full. Then deleted within 2 days. |
| Photos and files you replaced or removed — on your profile, a band, a post, a chat, a gear listing, a gig’s dress code or an audition — and uploads never attached to anything | Deleted within 30 days after nothing on Jamigo uses them. |
| Posts and comments that are deleted, by you or by our moderators | Text and media deleted 30 days later, or 30 days after a report about them is resolved. An empty record (dates and moderation status, no text or media) is kept for 2 years, and after that only while something of another member’s — a repost, a reply, a reaction or a mention — or a featured spot still depends on it. |
| Reactions and likes you gave | Until you remove them or delete your account. |
| Messages and chat attachments | For as long as any person in the conversation still has an account, including after you delete yours. Once none does, deleted 3 years after the last message, but not while the conversation is tied to an open dispute, nor while a report about one of its messages is open or was resolved less than 30 days ago. |
| Vouches you gave | Kept without your name after you delete your account, while the profile they are on exists. |
| Notifications | 12 months, then deleted. Notifications addressed to you are deleted when you delete your account. Counters that limit how many notifications you get a day: 30 days. |
| Product events | 13 months, then deleted. After you delete your account, they are linked only to the account’s internal identifier. |
| What you watch (views of posts) | 13 months; after that, only each post’s total views and watch time are kept, without who watched. Deleted when you delete your account. |
| Anonymous visit events from jamigo.io | 13 months, then deleted (every day, the oldest go). |
| The jamigo.io visitor identifier in your browser | Reused for up to 30 days, then replaced on your next visit. It stays in your browser until you clear its storage. |
| Short-lived counters that limit how often a code can be checked or a place searched | About 2 days. |
| Location shared for a gig | Coordinates deleted when sharing stops or expires (never more than eight hours). The record that sharing happened, without coordinates: 30 days after it ended. |
| Places you choose (your city; a gig’s venue) | Your city: until you change it or delete your account. A gig’s place: as described for work records below. |
| Signed-in devices and push notification tokens | Deleted when you delete your account. A device you sign out of, or that stops accepting notifications, is deleted 90 days later. A device not used for 12 months is signed out of notifications (its push token is deleted) and deleted 90 days after that. |
| Payment methods | Until you remove them or delete your account. |
| The log of who opened a payment method | 12 months, or until either account is deleted if that comes first. |
| The record that we removed a payment method because it held a bank or card number (which account and which kind of method, never the number) | 90 days after the removal, then deleted. |
| Your answer to “How did you hear about JAMIGO?” | The answer and the referral code: until you delete your account. The sentence you added, campaign details and the kind of page you arrived on: 13 months after you answer. |
| A referral code and campaign details held on your device | Up to 7 days, or until your account has them. |
| A referral that never qualified | While it is still waiting to qualify, kept as long as both accounts exist. Once it can no longer qualify — because the code was removed, or either account was deleted — deleted when 2 years have passed since the code applied. |
| Your creator application note, and the reason Jamigo gives for a decision about your application or your creator account | While your application is open or you are a creator, including while your creator account is paused. Once an application is rejected or a creator account is closed: 12 months after that decision. At once if you delete your account. |
| Qualified referrals, commission records, the revenue records commission is worked out from, and a retired creator code | 7 years after the end of the tax year of the last payment, refund or cancellation they record; then we remove what identifies you and keep only amounts and dates. |
| Memberships, invoices and Stripe’s customer identifier; orders, refunds, disputes, transfers and payouts; tutorial sales and paid lessons | 7 years after the end of the tax year of the last payment, refund or payout they record; then we remove what identifies you and keep only amounts and dates. |
| Records of your agreement to the launch offer’s charges | 7 years after the membership they cover ends, or 7 years after they were made if they never led to a membership; then deleted. |
| Card details we keep (brand, last four digits, expiry) | Until you change the card or delete your account. |
| Gigs, offers, bookings, jobs and applications, interviews, and lessons not paid through Jamigo | The records stay, because reviews and reputation rely on them. What people wrote in them (notes, descriptions, terms, an event’s name) and exact places (addresses and coordinates) are cleared 3 years after the gig, or after the job posting, application or lesson closed — for an application that made someone a member of a band, 3 years after they left the band; the city, the dates and the pay stay. A gig paid through Jamigo, with its offers, and a lesson paid through Jamigo follow the payment records above. |
| A band gig’s client name and contact details | Cleared 2 years after the gig. |
| Audition recordings | Deleted 180 days after the audition’s deadline (or after a recording sent late), but not while the job application it belongs to is still open. |
| Gig invitations and how quickly they were answered (used for response time) | 24 months after the gig starts, then deleted. |
| Reports about content or members | While a report is open. Once it is resolved, who made it and what they wrote are cleared 2 years later. |
| Records of actions Jamigo’s staff took | 7 years, then deleted. What staff typed to search for an account is removed after 90 days. |
| The record that an account was deleted (counts only) | 3 years, then deleted. |
| Staff verified mark | Until you delete your account or our staff remove it. |
| Performance clips at Mux, when enabled | Deleted from Mux within about an hour after you remove a clip or delete your account; our record of the clip 30 days after that, or, for a clip someone reported, 2 years after the report is resolved. |
| Messages Stripe sends us about payments | 13 months, then deleted. The payment records above keep what they record. |
| Sign-in records kept by our authentication provider, including IP addresses | 90 days, then deleted. Your phone number and email address are removed from them when you delete your account. |
| Sign-in sessions | Until you sign out or the session expires, and never more than 12 months after the session was last used; deleted at once when you delete your account. |
| Crash and error reports | Up to 90 days, then deleted by Sentry. IP addresses are not stored. |
| Technical logs (Supabase, Vercel) and message delivery logs (Resend, Twilio) | Up to 90 days, then deleted by the provider. |
| Backups of our database | Up to 30 days, then they roll off. |
| Stripe’s own records | Under Stripe’s own policy. When you delete your account, we clear your name and email address from your Stripe customer record. |
7. Your choices
- Edit your profile and manage your content in the app at any time.
- Decide what you share: whether you mark yourself available, what you post, which payment methods you add, and whether you share your location for a gig — which you can stop at any time.
- Cancel a membership at any time in the app, on the membership page (You → Your plan, in Jamigo on the web), or on Stripe’s billing page, which the app opens (“Payment method and invoices”), where you can also change the card on file.
- Manage JamigoPay, including your bank details, from the app, which opens your account at Stripe.
- Turn notifications on or off in your device’s settings.
- On jamigo.io, turn on Global Privacy Control or Do Not Track in your browser to stop the visit counts, or clear your browser’s storage to remove the visitor identifier.
- Ask us to correct a referral code applied to your account, at support@jamigo.io.
- Delete your account in the app under You → Account and privacy, or ask us to delete it at support@jamigo.io.
- Stop text messages by replying STOP, as described above.
- Email support@jamigo.io to ask for a copy of your information, or to correct or delete it. Depending on where you live, you may have additional rights under applicable law, and we will respond to requests as that law requires. We may need to confirm that a request comes from you before we act on it.
8. Children
Jamigo is not directed to children, and you must be at least 16 to use it. We do not knowingly collect personal information from anyone under 16. If you believe someone under 16 has an account or has given us personal information, contact us at support@jamigo.io and we will delete the account and that information. Paid and marketplace features — memberships, buying and selling through Jamigo, JamigoPay and the Creator Program — are only for people 18 or older, as our Terms of Service explain.
9. Where information is stored
Jamigo is operated from the United States, and your information is stored in the United States. If you use Jamigo from outside the United States, your information will be transferred to and processed in the United States. Some providers process information elsewhere: Stripe may process payment information in other countries, as its Privacy Policy describes, and, when place search is switched on, Geoapify processes what you type in a place search in the European Union.
10. Changes to this policy
We may update this Privacy Policy. When we do, we will change the effective date at the top, and if the changes are significant we will tell you in the app and by email, to the email address confirmed on your account if it has one. This version applies to everyone from October 15, 2026; the version it replaces is the Privacy Policy dated September 29, 2026. For changes after this version: we will give at least 30 days’ notice, in the app and by email, before a significant change applies to existing members, unless the law requires a change sooner.
Languages. This policy is published in English and in Spanish. Both versions have the same meaning. If you think they say something different, tell us at support@jamigo.io and we will correct them so they match.
11. Contact us
Jamigo, LLC
support@jamigo.io