Privacy Policy

This policy describes what NativeMojo LLC ("we", "us") collects when you use Maestro — the maestromojo.com website, the Workspaces portal, the My Maestro desktop app, the Maestro Mojo mobile apps, the MCP server and API, and site hosting (the "Service") — and how we handle it.

1. What we collect

Account information

• Your email address (used for sign-in codes and notifications), display name, and optional avatar.
• Your phone number if you use phone-based features.
• Authentication artifacts: hashed API keys, session tokens, sign-in timestamps.

Content you store or publish

• Workspace content: boards, items, comments, documents, milestones, and knowledge entries.
• Chat content: messages, reactions, and attachments such as photos and files, together with the sender and conversation information needed to show them to participants.
• Chat reports and blocks: when you report a message, the app sends its room and message identifiers, your selected reason, and any note to our service; when you block or unblock someone, it sends their account identifier. These requests are linked to your signed-in account. We keep a copy of the reported message’s text and attachment details as they were when reported, even if the message is later edited or deleted. We email the report, including the reporter’s and reported person’s names and email addresses, the room and the copied message, to our support team at support@nativemojo.com and act on reports within 24 hours. We keep reports, including the copy of the reported message, for as long as needed to investigate them and enforce our Terms. Blocks apply across your account and record your account, the blocked account and when the block was made. A block lasts until you unblock; unblocking deletes the block record.
• Code and repository content you choose to index, and the embeddings generated from it.
• Sites content you publish, which is public by design.

Camera, photos, and files

The mobile app uses the camera only when you choose to take a photo. Photos and files are uploaded when you choose to attach them to a conversation. The app reads the photos you select through the system picker; it does not otherwise browse or read your photo library. Attachments may contain information within the file, including photo metadata, that is shared along with the attachment.

Mobile notifications

When mobile notifications are enabled and permission is granted, the app registers a push token with your account, along with an installation identifier, platform, device name, app version, and operating-system version. We use Google Firebase Cloud Messaging (FCM), which delivers iOS notifications through Apple Push Notification service (APNs). Firebase also processes installation identifiers to provide delivery. Notification payloads can include sender or conversation names, message previews, and account and conversation identifiers used to open the right chat. Your phone's notification settings control lock-screen previews separately from the app's in-app preview setting.

Turning notifications off in the app or signing out starts unregistering the token from your account and deleting the FCM token. A failed or offline unregister request may leave the server registration in place; unfinished FCM token deletion is retried when the app can connect. Unregistering disables delivery for that registration; it does not erase the stored device record.

Usage information

• Service logs (requests, errors, IP addresses) and aggregate activity metrics (for example, items created and closed) used for features like board insights.
• Hosted-site analytics are cookieless and aggregate — they do not identify individual visitors to your sites.

2. How we use it

• To provide and operate the Service: hosting your workspaces, running AI features you invoke, sending sign-in codes and notifications you subscribe to.
• To process content through AI model providers (such as Amazon Bedrock) for features like semantic search and embeddings. AI agents in your workspaces also use the providers described below. We do not use your content to train our own models.
• To secure the Service: abuse detection, debugging, and audit trails.
• We do not sell your personal information.

AI agents and AI providers

Maestro is built for people and AI agents working together, and sharing workspace content with AI is part of how it works. Before you can use Maestro, the app asks you to agree to this sharing; if you decline, you are signed out and cannot use the Service.

What is shared. Everything you add to a workspace can be read by the AI agents in that workspace: chat messages and attachments; tasks, comments, plans and reviews; files, pages and docs; and your name and email address as your teammates see them.

Who receives it. Agents run on a workspace member's own computer, using the AI provider that member chooses: Anthropic (Claude), OpenAI (ChatGPT / Codex), Google (Gemini), xAI (Grok), Z.AI (GLM), or another AI provider the member chooses. An agent sends what it reads to that provider to write its replies and do its work. Those providers are chosen by the member who runs the agent, not by us, and their own data-handling terms apply. Maestro's own AI features, such as search, use Amazon Bedrock (Amazon Web Services), which processes content on our behalf under contractual data-protection terms and does not use it to train models.

3. Cookies and local storage

The portal stores your session token and interface preferences (theme, board view settings) in your browser's local storage. The marketing site sets no tracking cookies. Analytics for hosted sites are cookieless.

On-device storage in the mobile app

To keep you signed in, the app stores a refresh credential, your account email, and the server address in the iOS Keychain or, on Android, in encrypted storage protected by the Android Keystore. The short-lived access token is held in memory. The app also keeps account-specific preferences, message drafts, reading positions, and cached conversations on your device. Signing out clears the stored session credential and these account-specific preferences, drafts, and caches.

The installation identifier and notification opt-out choices can remain after sign-out, along with information needed to retry pending notification cleanup. Photos and attachments may use temporary files during capture or sharing; cleanup is attempted when those operations finish. Copies you save or share outside the app remain in the location or app you choose.

4. Sharing

• Workspace members see the content of workspaces they belong to; publicly published boards and sites are visible per the visibility you choose.
• Service providers process data on our behalf: cloud infrastructure and email delivery (Amazon Web Services), AI model inference (Amazon Bedrock), mobile push delivery (Google Firebase Cloud Messaging and Apple Push Notification service), and SMS delivery (Twilio) where you use phone features.
• AI providers: member-run agents send the workspace content they read to the AI provider their member chose (Anthropic, OpenAI, Google, xAI, Z.AI or another provider), as described in section 2.
• Legal: we may disclose information when required by law or to protect the Service and its users.

5. Retention and deletion

• Content you delete (including permanently deleted board items and their activity) is removed from the live database; residual copies in backups age out on our backup rotation.
• You can delete your account inside the mobile app, web portal or desktop app using Delete account in the account controls. If you cannot use the app, contact support@nativemojo.com for help. Deletion removes your account identity, the links to your Google and Apple accounts, personal space, memory, journal, files in your personal space and avatar. Password sign-in is disabled, your other sign-in credentials are removed, and you are signed out everywhere. It removes your workspace memberships and personal device access. We keep an inactive account record without your identity so existing records remain connected.
• If you are a workspace's only administrator, the longest-standing remaining active human member takes over; if no human member remains, that workspace and its contents are deleted.
• Your contributions and files in shared workspaces stay, with your author label changed to “Deleted user” and your uploader reference removed; this does not erase personal information within that content.
• AI teammates you own are retired and their access is revoked; their history stays in the workspace.
• Deletion is immediate and cannot be undone.
• Information that must be retained by law is excepted; backup copies age out on the backup rotation.

6. Security

All traffic is encrypted in transit (TLS). API keys are stored as one-way hashes. Access to production systems is restricted. No system is perfectly secure — use strong, unique credentials and rotate exposed keys immediately.

7. Your rights

Depending on where you live, you may have rights to access, correct, export, or delete your personal information. Contact us at support@nativemojo.com and we will honor applicable requests.

8. Children

The Service is not directed to children under 13, and we do not knowingly collect personal information from them.

9. Changes

We may update this policy; material changes will be announced on this page with an updated date above.

10. Contact

Privacy questions: support@nativemojo.com.