Privacy Policy

1. Information We Collect

1.1 Information You Provide Directly

• Account information (name, email, username)
• Mobile phone number and SMS opt-in consent (if you text us or provide your number to receive messages)
• Profile details (avatar, preferences, optional information)
• Content and Creations (designs, images, text, materials)
• Communications (support requests, feedback)

1.2 Information Collected Automatically

• Usage data (app interactions, features, screens, session length)
• Device and log data (device type, OS, app version, IP address, identifiers, crash logs)
• Cookies and similar technologies

1.3 Information from Third Parties

• Authentication from Apple/Google
• Payment confirmation from Stripe or app stores
• Analytics data from Firebase

2. How We Use Your Information

• Operate, provide, and maintain the Service
• Enable content creation, customization, remixing, and sharing
• Personalize experience and show relevant features
• Process purchases with third-party partners
• Communicate updates, security alerts, support
• Monitor, maintain, and improve the Service
• Prevent fraud and abuse; protect rights and security
• Comply with legal obligations and enforce Terms of Service

3. Legal Bases for Processing (EEA/UK Users)

• Performance of contract
• Legitimate interests (improving Service, securing systems, preventing abuse)
• Consent (for marketing or optional analytics)
• Legal obligations

4. How We Share Your Information

We do not sell your personal information. We may share in these circumstances:

• Service providers (hosting, analytics, support, email, cloud storage)
• Commerce and fulfillment partners (manufacturing, shipping, payment processing)
• Legal reasons (law requirements, protect rights/safety/property)
• Business transfers (merger, asset sale, acquisition)

We do not sell your personal information, and no mobile information or SMS opt-in consent will be shared with third parties or affiliates for marketing or promotional purposes. Mobile opt-in data and consent are excluded from any sharing described above. We share your phone number only with the messaging service providers (such as our SMS carrier and platform) strictly as needed to deliver the messages you requested.

5. Text Messaging (SMS)

If you text us or provide your mobile number and opt in, we use your number to operate our two-way messaging program — for example, to let you submit photos and receive collections back, send order, shipping, and account updates, respond to your questions, and send occasional promotional messages. Message frequency varies, and message and data rates may apply.

Consent to receive text messages is never a condition of any purchase. You can opt out at any time by replying STOP, or reply HELP for help. See our Opt-In Policy for full details. We retain your number and a record of your consent for as long as you remain opted in and as required to document consent.

6. Third-Party Services We Use

6.1 Firebase (Analytics & App Performance)

Collects: device information, usage data, crash logs, app interaction patterns. Does not receive: personal Creations, messages, payment data. Firebase Privacy & Support

6.2 Stripe (Payments)

Collects: payment method details, transaction information, fraud prevention data, billing information. We do not store full payment card information. Stripe on Privacy

6.3 Amazon Web Services (Hosting)

Hosts the Made In Motion CRM and its databases in the United States. Each customer’s CRM data is stored in its own database. AWS Privacy Notice

7. Google User Data: Gmail Integration

Made In Motion’s CRM lets you connect your own Google account so the CRM can send and receive email on your behalf. This is optional. If you do not connect Google, none of this section applies to you.

7.1 What we request

When you connect, Google asks you to grant the CRM the following permissions: your basic profile information (openid, email) so we can identify which mailbox you connected, and full mailbox access (https://mail.google.com/). Google describes the mailbox permission as “Read, compose, send, and permanently delete all your email from Gmail.” That is the only Google permission that supports the standard IMAP and SMTP mail protocols the CRM uses, and every email client that works with Gmail over those protocols requests it. We use it as described below and no further.

7.2 How we use it

• To receive mail. The CRM reads new messages in your mailbox so that emails exchanged with people already in your CRM (leads, contacts, organizations and deals) appear on those records. Messages from people not in your CRM are held in a review queue that only you can see, where you decide whether to link them to a record, create a record, or ignore the sender. The CRM never creates records from your email on its own.
• To send mail. When you compose an email inside the CRM, it is sent from your Gmail account through Google’s servers so it appears in your Sent folder like any other message.
• To keep the connection working. We store the access and refresh tokens Google issues so you do not have to sign in again for every sync.
• To answer your questions about your own mail. Where your company has turned the feature on, you can ask the MadeInMotion assistant built into the CRM, by typing or by voice, to find or summarize email in your own connected mailbox (for example, “what did Greg say about pricing?”). The assistant reads your synced mail only when you ask it to, only to answer you, and only your own mailbox: it cannot search a teammate’s mail, and a teammate, including an administrator, cannot use it to search yours. It cannot send, delete or change email. The same applies to an AI assistant you connect to the CRM yourself with your own access token.

To answer, the text of the relevant messages is sent to the AI provider that powers the assistant on your company’s CRM: Anthropic for typed conversations, and OpenAI or Google (Gemini) for voice conversations, depending on how your CRM is set up. These providers process the text on our behalf to produce the answer, under terms that do not permit them to use it to train their models.

7.3 What we do not do

• We do not delete email from your mailbox. The permission Google grants includes deletion, but the CRM never issues a delete.
• We do not use your Google user data to serve advertisements.
• We do not sell your Google user data, and we do not transfer it to third parties except as needed to provide or improve the CRM’s user-facing features, to comply with law, or as part of a merger or acquisition with prior notice to you.
• We do not allow humans to read your Google user data, unless you ask us to for support, it is necessary for security purposes (such as investigating abuse), we are required to by law, or the data has been aggregated and anonymized for internal operations.
• We do not use Google user data, including the content of your email, to develop, improve or train generalized or non-personalized artificial intelligence or machine learning models.
• The MadeInMotion assistant does not read your email on its own initiative, in the background, or on anyone else’s request. It reads your synced mail only as described above: when you ask it a question about your own mailbox.

7.4 Limited Use

Made In Motion’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.

7.5 Where it is stored and who can see it

Synced messages are stored in your company’s own CRM database, which is separate from every other customer’s, on servers hosted by Amazon Web Services in the United States. Tokens are stored encrypted. You control whether your teammates can see the content of your synced messages: the default shows them only the subject and participants of messages attached to shared records, and you can choose to share full message content or keep it to yourself.

7.6 Retention and deletion

Synced messages stay in your company’s CRM as part of the record history until your company deletes them or the account is closed. You can disconnect Google at any time from the Integrations page in the CRM. Disconnecting revokes the CRM’s access at Google and deletes the stored tokens immediately. You can also revoke access from your Google Account at myaccount.google.com/permissions. To have previously synced messages removed as well, contact us at support@madeinmotion.ai and we will delete them within 30 days.

8. Google User Data: Google Calendar and Google Meet Integration

Made In Motion’s CRM also lets you connect your own Google Calendar so that your meetings appear on the CRM records of the people you meet with. This is a separate, optional connection with its own Google permission screen. If you do not connect Google Calendar, none of this section applies to you. Section 7 above covers Gmail.

8.1 What we request

When you connect, Google asks you to grant the CRM the following permissions:

• Your basic profile information (openid, email) so we can identify which Google account you connected.
• Access to your calendar events (calendar.events), to read the meetings on your calendar and to add a meeting to it when you schedule one from inside the CRM.
• Read-only access to your Google Meet conference records (meetings.space.readonly), to find the transcript and the “Notes by Gemini” document that Google Meet produced for a meeting on your calendar.
• Read-only access to the files Google Meet created in your Google Drive (drive.meet.readonly), to read the text of that meeting notes document. This permission covers only files created by Google Meet, not anything else in your Drive.

8.2 How we use it

• To show meetings on records. Meetings whose attendees match people already in your CRM (leads, contacts, organizations and deals) appear on those records, and each record shows when you last met and when you next will. Events you marked private in Google Calendar never sync.
• To schedule. When you create a meeting inside the CRM, it is created on your Google Calendar and invitations go out from your account like any other event.
• To keep transcripts and notes with the meeting. If Google Meet transcribed a meeting on your calendar or Gemini took notes for it, the CRM copies the transcript text and the notes document text onto that meeting’s record, so what was said stays with the deal or contact it concerns. The CRM does not record, transcribe or join meetings itself; it copies what Google Meet already produced, at your or your organization’s choice in Google Meet.
• To summarize meetings. Where your company has turned the feature on, the CRM writes a short summary of what was discussed and decided from the transcript or notes, marked as written by the assistant. It never replaces a summary a person wrote.
• To answer your questions about your meetings. You can ask the MadeInMotion assistant built into the CRM, by typing or by voice, about meetings you can see in the CRM (for example, “what did we agree with Greg last week?”). The assistant reads a transcript or notes only when you ask it to, only to answer you, and only for meetings whose details you could open yourself in the CRM (see 8.4). The same applies to an AI assistant you connect to the CRM yourself with your own access token.
• To keep the connection working. We store the access and refresh tokens Google issues so you do not have to sign in again for every sync.

To write a summary or answer a question, the relevant meeting text is sent to the AI provider that powers the assistant on your company’s CRM, the same providers described in section 7.2: Anthropic for typed conversations and summaries, and OpenAI or Google (Gemini) for voice conversations, depending on how your CRM is set up. These providers process the text on our behalf to produce the summary or answer, under terms that do not permit them to use it to train their models.

8.3 What we do not do

• We do not delete or change events on your Google Calendar. The CRM adds events you schedule in it and otherwise only reads.
• We do not read any file in your Google Drive other than the transcripts and notes Google Meet created for meetings on your calendar.
• We do not use your Google user data to serve advertisements.
• We do not sell your Google user data, and we do not transfer it to third parties except as needed to provide or improve the CRM’s user-facing features, to comply with law, or as part of a merger or acquisition with prior notice to you.
• We do not allow humans to read your Google user data, unless you ask us to for support, it is necessary for security purposes (such as investigating abuse), we are required to by law, or the data has been aggregated and anonymized for internal operations.
• We do not use Google user data, including your calendar events and the content of meeting transcripts and notes, to develop, improve or train generalized or non-personalized artificial intelligence or machine learning models.
• Apart from the meeting summary described in section 8.2, the MadeInMotion assistant does not read meeting transcripts or notes on its own initiative, in the background, or on anyone else’s request. It reads them only when you ask it a question about a meeting you can see.

8.4 Where it is stored and who can see it

Synced meetings, transcripts and notes are stored in your company’s own CRM database, which is separate from every other customer’s, on servers hosted by Amazon Web Services in the United States. Tokens are stored encrypted. A meeting that you and a connected teammate are both invited to appears once, shared. You control what your teammates see of the meetings you organize: the default shows them only the title, time and attendees, and you can choose to share full details, which includes the description, transcript, notes and any assistant-written summary. You always see your own meetings in full. The assistant follows the same rule: it will not read to a teammate what that teammate could not open in the CRM.

If your company also connects Microsoft Teams or Zoom, transcripts from those meetings land on the same meeting records and are handled the same way. They are not Google user data.

8.5 Limited Use

Made In Motion’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.

8.6 Retention and deletion

Synced meetings stay in your company’s CRM as part of the record history until your company deletes them or the account is closed. You can disconnect Google Calendar at any time from the Integrations page in the CRM. Disconnecting revokes the CRM’s access at Google, deletes the stored tokens immediately, and removes from the CRM the synced meetings you organize, including their transcripts, notes and summaries. A meeting organized by a teammate that you were invited to stays, as theirs. You can also revoke access from your Google Account at myaccount.google.com/permissions. To have anything else removed, contact us at support@madeinmotion.ai and we will delete it within 30 days.

9. Data Retention

Data is retained only as long as necessary to:

• Provide the Service
• Fulfill legal, accounting, reporting obligations
• Resolve disputes and enforce agreements

Data is deleted or anonymized when no longer needed.

10. Security

We use reasonable technical and organizational measures to protect information, though no system can be guaranteed 100% secure. Users are responsible for keeping their account credentials confidential.

11. International Data Transfers

Made In Motion operates from the United States. Data may be stored or processed in the U.S. or other countries where service providers operate. Safeguards are implemented where legally required.

12. Your Rights and Choices

Depending on your location, you may have rights to:

• Access personal information
• Correction of inaccurate data
• Deletion (subject to obligations)
• Restriction of use
• Objection to processing
• Portability in a structured format
• Withdraw consent

Contact support@madeinmotion.ai. You also have the right to lodge complaints with your local data protection authority.

13. Children’s Privacy

The Service is not directed to children under 13. We do not knowingly collect personal information from children under 13. Parents or guardians should contact support@madeinmotion.ai if concerned.

14. Third-Party Links and Services

This Privacy Policy does not apply to third parties. Users are encouraged to review third-party privacy policies.

15. Changes to This Privacy Policy

Updates may occur with a revised “Last Updated” date. Continued use signifies acceptance of the updated policy.

16. Contacting Us

Email: support@madeinmotion.ai