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

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

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

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.

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

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:

With service providers

We use service providers that process information on our behalf, only to provide the Service. Each receives only what it needs:

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:

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:

Deleted information can stay in our database backups for up to 30 days, until they roll off.

How long each kind of information is kept

InformationHow long we keep it
Your account, profile, content and settingsWhile 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 profileWhile other records in this table still refer to it.
Your agreement to our Terms at sign-up; your confirmation that you are 18 or olderWhile 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 accountDeleted 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 accountNo 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 anythingDeleted within 30 days after nothing on Jamigo uses them.
Posts and comments that are deleted, by you or by our moderatorsText 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 gaveUntil you remove them or delete your account.
Messages and chat attachmentsFor 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 gaveKept without your name after you delete your account, while the profile they are on exists.
Notifications12 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 events13 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.io13 months, then deleted (every day, the oldest go).
The jamigo.io visitor identifier in your browserReused 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 searchedAbout 2 days.
Location shared for a gigCoordinates 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 tokensDeleted 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 methodsUntil you remove them or delete your account.
The log of who opened a payment method12 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 deviceUp to 7 days, or until your account has them.
A referral that never qualifiedWhile 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 accountWhile 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 code7 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 lessons7 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 charges7 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 JamigoThe 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 detailsCleared 2 years after the gig.
Audition recordingsDeleted 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 membersWhile 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 took7 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 markUntil you delete your account or our staff remove it.
Performance clips at Mux, when enabledDeleted 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 payments13 months, then deleted. The payment records above keep what they record.
Sign-in records kept by our authentication provider, including IP addresses90 days, then deleted. Your phone number and email address are removed from them when you delete your account.
Sign-in sessionsUntil 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 reportsUp 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 databaseUp to 30 days, then they roll off.
Stripe’s own recordsUnder Stripe’s own policy. When you delete your account, we clear your name and email address from your Stripe customer record.

7. Your choices

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