Legal

Privacy Policy

Effective November 1, 2026

This Privacy Policy explains how Silk Road Merchants LLC ("we", "us", "our") handles information through the martialcrm.com website (the "Website") and the MartialCRM™ school management service at app.martialcrm.com (the "Service"). MartialCRM™ is a product of Silk Road Merchants LLC.

The short version: we collect only what we need to run the Website and the Service, we never sell personal information, and we never use it for advertising.

1. Our role and the school's role

Martial arts schools ("Schools") use the Service to manage information about their students, prospective students, parents and guardians, and staff ("School Data"). The School decides what School Data to collect and how to use it. We store and process School Data only to provide the Service to that School and as the School instructs. If you are a student or parent and have a question about your information, please contact your School first. We will help the School respond.

A School can also offer an inquiry form, a class schedule and online booking to the public through the Service, either on pages at app.martialcrm.com or placed on the School's own website. When you send an inquiry or book a class this way, you are giving your information to that School, and we process it on the School's behalf. If the form is shown on the School's own website, that website's privacy policy covers the website itself.

For information we collect through the Website, such as contact form messages, we decide how that information is used, as described below.

2. Information we collect

When you visit the Website or contact us

  • Contact form. Your name, email address and message, and any optional details you choose to give: phone number, school name, number of students, topic and plan of interest. The form is sent to us by email. With each message we also receive the country your connection comes from, which Cloudflare works out from your IP address.
  • Technical information. Like any website, our hosting and security provider receives your IP address, browser type and the pages you request. This information is used to deliver the site and protect it from abuse.
  • Spam protection. The contact form uses Cloudflare Turnstile, which checks signals from your browser to tell people from bots.

When you use a School's inquiry form or online booking

  • Inquiry form. Your first and last name, an email address or phone number (at least one), whether you are asking about joining or about a current student, and any message you write. On a form for the whole School, you also choose a location. If you are asking for your children, the first name, last name and age of each child, up to four. You may also give your own age, previous martial arts experience and how you heard about the School. If you write about a current student, you may give that student's name. Your inquiry is added to the School's records, either as a new prospective student or on the record of someone the School already has with the same name and contact details, and the School's staff get a task to follow up. A message about a current student may be added to that student's record. Nothing is sent back to you automatically.
  • Class schedule. The public schedule shows each class's time, name and whether places are left. It never shows who has booked or how many people have.
  • Online booking. Your first and last name, email address and phone number, and the first and last name of each child you book for, up to four. A date of birth is asked only for classes with an age range. We email you a 6-digit code to confirm the booking. The booking is kept with the School's records, and if the School has set its classes up that way, a new person who books also becomes a prospective student on the School's records.
  • Notice. Both forms show a notice naming the School. It says the School uses your details to reply to your inquiry, or to confirm and manage your booking and contact you about it, by email, phone call or text message, and it links the School's own privacy policy when it has one. The forms do not ask you to agree to marketing. The notice you saw, and your confirmation that you are 16 or older, are recorded with your inquiry or booking request. MartialCRM™ itself does not call you or send text messages.
  • Spam and abuse protection. Both forms use Cloudflare Turnstile, and to check the result the Service sends Cloudflare your IP address. To limit repeated use, the Service keeps a keyed one-way hash of your IP address when you view a School's class schedule or send either form, and of your email address when you book, rather than the address itself.

When a School uses the Service

  • Staff accounts. Name, username, email address, role, branch and an optional photo for each staff member, and the text size and light or dark display they choose. Passwords are stored only as one-way hashes.
  • Two-step sign-in. If a staff member sets up two-step sign-in, the Service keeps what it needs to check the second step. For an authenticator app, that is the secret the app shares with the Service, which is encrypted before it is stored. For a passkey or security key, it is the key's public key and identifier, the name the staff member gave it, the type of device it reports, and when it was added and last used. Each staff member also gets 10 single-use recovery codes, stored only as one-way hashes. The fingerprint, face or PIN check that unlocks a passkey happens on the staff member's own device, and the Service never receives it.
  • School Data. Information a School enters about its contacts, which may include names, dates of birth, phone numbers, email and mailing addresses, occupation, guardian and emergency contacts, safety information for emergencies (which can include health information), photos, attached files, notes and call logs, ranks, test results, attendance, and membership agreements with their payment terms and payment method. It also includes prospective students and their inquiries, the tasks and follow-ups staff record, and the School's class schedule and bookings. If a School sends email through the Service, School Data also includes those messages and their recipients. When staff import attendance from a spreadsheet, the file is read in their browser and only the check-ins are sent to the Service. The Service does not process payments and does not store card or bank account numbers.
  • Kiosk check-ins. The phone number or student ID entered at a School's check-in kiosk, and the time and place of the check-in. If a School turns on the kiosk's optional camera motion-wake, the camera image is analyzed only on the tablet itself to wake the screen. No images are sent to us or stored.
  • Security and activity records. Each user's most recent sign-in time, the IP addresses of failed sign-in attempts (used to block repeated attempts), and a record of changes to contact records showing which fields changed and who changed them. When School staff download a file attached to a person's record, print or save that person's full profile as a PDF, or download a backup of records due for deletion, we record who did it and when in the person's activity history, and for a backup we also keep a note of which manager accepted responsibility for it. When our support staff use "View As" to see the Service as a School user, we record when the session starts and ends and the reason they give for it (support, an incident, security or a legal requirement, as our Terms of Service allow), and the School's managers can see each session and its reason. When a staff member accepts or declines our Terms of Service or User Terms in the Service, or confirms they have seen a notice of updated terms, we record which version, when, and the IP address and browser they used. When a staff member sets up, removes or uses two-step sign-in, when our support staff reset it for them, and when a second step is refused, we record what happened, when, and the IP address and browser used.
  • Billing information. The plan, number of user accounts and storage a School uses, so that we can invoice the School.

3. Gmail and Outlook mailbox and calendar connection

A School manager may choose to connect a branch's Gmail or Microsoft Outlook mailbox to the Service. This is optional, and only that manager's branch uses it.

  • What we request. Permission to read email (Google's gmail.readonly scope or Microsoft's Mail.Read permission) and to send email (Google's gmail.send scope or Microsoft's Mail.Send permission) from the connected mailbox, plus the mailbox's email address. If the manager turns on calendar sync for an Outlook or Microsoft 365 mailbox, we also request Microsoft's Calendars.ReadWrite permission. We never request permission to change or delete messages, or to change the mailbox's settings.
  • What we read, and when. Only when a staff member opens a contact's record, the Service looks up the most recent messages (up to ten) to, from or copied to that contact's email addresses. It reads each message's date, subject and a short preview, and shows them to the staff member on that page.
  • What we send, and when. The Service sends email from the connected mailbox only as the School's staff set it up, such as the School's campaigns, which a manager writes and turns on. Campaigns are a newsletter sent once at a date and time the manager picks, and automatic emails to students on set occasions, such as two weeks after joining, after time away from class, or a month before a membership ends. Each campaign email goes to the email addresses the School has for the student, includes the School's name, postal address, a phone number or website, and a link to unsubscribe, and is never sent to an email address that has unsubscribed. Messages go out from the School's own mailbox and appear in its Sent folder. We never use a School's mailbox to send our own messages.
  • Booking emails. If a School offers online booking, the Service sends booking emails from the branch's mailbox to the email address given when booking: the confirmation code, a notice that the booking is confirmed, waiting for approval or on the waitlist, a reminder the day before the class, and notices when the School approves, declines, moves or cancels a booking or cancels a class. Each names the School and branch, gives the branch's postal address and a phone number or website, and says it was delivered using MartialCRM™ on the School's behalf. Where it applies, it also includes a link to manage the booking. Booking emails carry no advertising or offers. They are about a booking you made, so they do not include an unsubscribe link, and unsubscribing from a School's campaign emails does not stop them.
  • Calendar sync. If a manager turns it on, the Service creates a separate calendar in the connected Outlook or Microsoft 365 account, named after the School and branch, and keeps the branch's class schedule in it. Each event shows the class name, activity, time and branch. Events never name or count the people who booked, and a booked private lesson shows only "(booked)". The Service changes and removes only the events it created, and does not read the events in any other calendar. Turning sync off stops the updates. The calendar stays in the account until someone deletes it there.
  • What we store. The connected email address and the access tokens the provider issues, which are encrypted before they are stored. Messages read from the mailbox are not stored: their subjects and previews are fetched for the page and then discarded. For email sent through the Service, including campaign and booking emails, the Service keeps the message, its recipients and the time it was sent as part of the School's records, so staff can see what was sent. For calendar sync, the Service stores the calendar's identifier and the identifiers of the events it created.
  • What we never do. We do not use mailbox or calendar data for advertising, we do not sell it or transfer it to anyone else, and we do not use it to train artificial intelligence or machine learning models. No person at Silk Road Merchants LLC reads it, except with the School's permission for support, for security purposes, or where required by law.
  • Disconnecting. A School manager can disconnect the mailbox at any time from the branch's profile in the Service. Disconnecting deletes the stored tokens, and for Gmail it also asks Google to revoke MartialCRM™'s access. You can also remove MartialCRM™'s access yourself from your Google Account or Microsoft account settings.

Google API Services: MartialCRM™'s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

4. How we use information

  • To provide, maintain and support the Service for each School.
  • To send the email and campaigns that a School's staff send or set up through the Service, and to record when a recipient unsubscribes.
  • To run a School's inquiry form, class schedule and online booking: to record each inquiry or booking for the School, give its staff a task to follow up, and send the booking emails described in section 3.
  • To keep a branch's class schedule in its Outlook calendar, when the School turns on calendar sync.
  • To answer messages you send us and tell you about MartialCRM™ when you ask.
  • To keep the Website and the Service secure, prevent abuse and fix problems, including checking forms for spam and limiting repeated submissions.
  • To bill Schools for their subscriptions.
  • To comply with the law and enforce our Terms of Service.

We do not sell personal information, share it for cross-context behavioral advertising, or use School Data for any purpose other than providing the Service to the School that entered it.

5. How we share information

We share information only with service providers that help us run the Website and the Service, and only as they need it to do that work:

  • Amazon Web Services hosts the Service and its databases in the United States.
  • Cloudflare delivers and protects the Website and the Service, runs the Turnstile spam check on our contact form and on Schools' inquiry and booking forms, and delivers contact form messages to us by email. For the Turnstile check on a School's form, the Service sends Cloudflare your IP address. Cloudflare also stores the Service's nightly backups in the United States. They are encrypted on our server before they are sent, so Cloudflare cannot read them.
  • jsDelivr delivers some open-source software components that the Service loads in your browser, including on Schools' inquiry and booking pages. It receives your IP address and browser information, but not School Data.
  • SheetJS delivers the spreadsheet component that a staff member's browser loads to export a report to Excel or import attendance. It receives the IP address and browser information, but not School Data: spreadsheets are read and written in the browser.
  • YouTube (Google) plays the training videos in the Service's Tutorials window, from its privacy-enhanced youtube-nocookie.com domain, only when a staff member opens that window. It receives the IP address and browser information, but not School Data.
  • Google and Microsoft, only if a School connects a mailbox or turns on calendar sync, as described in section 3. Email the Service sends from a connected mailbox, including booking emails, is delivered by that provider.

Where information is stored. The Service, its databases and its backups are stored in the United States, and we answer contact form messages from the United States. If you are outside the United States, including in Canada, your information is transferred to the United States and handled there, and courts, law enforcement and national security authorities in the United States may be able to obtain it under US law.

We may also disclose information if the law requires it, to protect the rights, safety or property of our users, the public or us, or as part of a merger, acquisition or sale of assets, in which case this policy will continue to apply to the information transferred.

6. Cookies and analytics

The Website does not set its own cookies and does not use advertising or cross-site tracking. We may use Cloudflare Web Analytics, which counts visits without cookies and without building a profile of you. The Service uses a strictly necessary session cookie to keep staff signed in, and the check-in kiosk stores a sign-in token on the kiosk tablet. The inquiry form, class schedule and booking pages that Schools share with the public set no cookies of their own. Cloudflare Turnstile, which runs on those forms, works under Cloudflare's own privacy policy. When a staff member plays a video in the Tutorials window, YouTube may store information in their browser.

7. How we protect information

We use administrative, technical and physical safeguards appropriate to the information we hold. These include encryption of all traffic in transit, a separate database for each School, one-way hashing of passwords, automatic lockout after repeated failed sign-ins, two-step sign-in (required for our support staff), role-based access for School staff, encryption of mailbox tokens and authenticator-app secrets, change logging, and daily backups that are encrypted and kept off-site. Booking codes are stored only in a form that cannot be read back, and links to manage a booking are signed so that they cannot be guessed. No system is perfectly secure. If we learn of a security incident affecting School Data, we will notify the affected Schools without undue delay.

8. How long we keep information

We keep contact form messages, and our replies, for up to seven years after our last exchange with you, and then delete them. We keep School Data while the School's subscription is active, and no longer than it is needed. This includes inquiries, prospective students and bookings, which are part of the School's records. Someone who has had a membership agreement with the School is deleted 7 years after their last attendance or the end of their last agreement, whichever is later. Anyone else, prospective students included, is deleted 3 years after the last activity on their record or the day they were added. The School's managers see each record due for deletion for at least 30 days first, and new activity keeps it. During that time a School manager can download a backup of these records, which never includes safety information. A School that does takes sole responsibility for that copy, which these periods no longer cover. Records of a School's own employees are not deleted this way.

When School staff delete a student or prospective student, a file on their record or an attendance entry, or a record is deleted as due, it goes to the School's Recycle Bin, where a School manager can restore it for 30 days. After 30 days it is deleted permanently, and a manager can delete it permanently sooner, for example to answer a request to erase it. One exception keeps some records longer: for someone who has had a membership agreement and was active in the last 7 years, we keep only what may be needed for tax or a legal claim, which is their agreements, their name, date of birth and mailing address with the guardians named on them, their attendance and the notes on their record, and their signed documents. Everything else about them is deleted, including any safety information. These records are deleted 7 years after their last activity, or later only while a legal hold placed for an ongoing legal matter lasts. No one at the School can open them unless we approve the School's request for a legal claim or dispute, a tax or accounting audit, a court order or other legal process, or the person's own request for a copy of their data, and then only to read them, for 30 days. What is left after a permanent deletion records only what kind of item was deleted, when and by which staff member, and backup copies of it age out within 57 days of its permanent deletion.

When a subscription ends, we delete the School's data within 90 days unless the School asks us to delete it sooner or the law requires us to keep it. Backup copies age out within 57 days after that. We keep the record of each staff member's acceptance or refusal of our terms, and of the notices of updated terms they saw, as evidence of the agreement, including after their account is removed. When a staff account is removed, its authenticator-app secret, passkeys, security keys and recovery codes are deleted, and the record of its two-step sign-in activity is kept with the other security records.

Some information from online booking is kept for less time. A booking code works for 10 minutes. Booking requests, including places held while a code was pending, are deleted after 30 days, and a booking that went ahead stays with the School's records. Records of booking emails are deleted after 180 days. The link to manage a booking works until 30 days after the class. The hashed IP and email addresses used to limit repeated submissions are deleted two days after they were last used.

9. Children's information

Martial arts schools teach many children, so School Data often includes information about minors. The Service is used by School staff, not by children. A School's inquiry form and online booking are meant to be filled in by an adult. Both ask whoever fills them in to confirm that they are 16 or older, and both refuse anyone who gives an age or date of birth under 16 for themselves. When a class is for a child, a parent or guardian gives the child's name, and either the child's age on the inquiry form or the child's date of birth when a class has an age range. Each School is responsible for having the right to collect and use its students' information, including obtaining parental consent where the law requires it. We use children's information only to provide the Service to the School. The Website is not directed to children under 16, and we do not knowingly collect personal information from them through it.

10. Your choices and rights

You can ask us to access, correct or delete personal information you sent us through the Website. Depending on where you live, you may have additional rights under laws such as the California Consumer Privacy Act and Canada's Personal Information Protection and Electronic Documents Act (PIPEDA). We will not discriminate against you for exercising any of these rights. To make a request, use our contact form and choose "Make a privacy request". We may ask you to confirm who you are before we act on it. We reply within 30 days. If we need longer, we will tell you before then why, and when you will have our answer. If your request concerns School Data, we will pass it to the School promptly, since the School controls that information, and help it respond. If you sent an inquiry or booked a class through a School's form, that information is School Data, so please ask the School to correct or delete it. You can cancel a booking, or move it to another time of the same class, with the link in your booking email until the School's cutoff before the class. If you receive campaign email from your school through MartialCRM™ and no longer want it, use the unsubscribe link at the bottom of the email or your email program's unsubscribe button. This puts the email addresses on your student account on your school's unsubscribe list, which stops its campaign emails to those addresses on every student account at the school that uses them, a family member's included. Only new consent you give the school takes an address off the list. You can also contact your school, which decides whom it emails. You may also opt out of any marketing email from us at any time.

11. Changes to this policy

We may update this policy as the Website and the Service change. We will post the new version here with a new effective date, and if the changes are significant we will notify Schools before they take effect.

12. Contact us

Our Privacy Officer is responsible for how we handle personal information and for this policy. To reach the Privacy Officer, use our contact form and choose "Make a privacy request", or write to:

Privacy Officer
Silk Road Merchants LLC
2000 Massachusetts Ave
Cambridge, MA 02140
United States

If you have a concern about how we handle personal information, please tell our Privacy Officer first. We will look into it and reply. If you are in Canada and are not satisfied with our answer, you can complain to the Office of the Privacy Commissioner of Canada. If your concern is about information a School holds about you, please contact the School, which is responsible for it, and we will help it respond.