Scope
This page describes the public Martius marketing website, Google account sign-in and the local-file boundary of the desktop video workflow. The website publishes product information, studio examples, guides and documentation. It does not provide private project uploads, a waitlist form or a checkout flow.
The desktop application works with selected local materials and editable projects. Account authentication, local source files, model requests and approved destination transfers are different data paths; the sections below explain that distinction. Contact the team with a question about a specific workflow or service.
Google sign-in and your account
Opening the login dialog loads Google Identity Services. Google may receive browser and network information while providing its sign-in experience. If you choose to continue, Google supplies an identity credential to our existing X-Pilot account service at server.x-pilot.ai. That service verifies the credential and returns an account session. Martius uses the same account identity as X-Pilot.
The website requests basic identity information for sign-in, including your account name and email address. It does not request access to your Google Drive files, Gmail or local project materials. Google's handling of its sign-in service is described in the Google Privacy Policy.
A session token and limited account information are stored in this browser's local storage for Martius. The token is sent only to the account service to verify your session and retrieve your profile; it is not placed in page URLs. A valid session can be restored when you return. Signing out clears the website's stored session and account information. It does not sign you out of Google, revoke Google consent or revoke a token already issued by the account service.
Signing in does not upload original documents, source footage or editable projects. If you need help with account information or account deletion, contact support@x-pilot.ai.
Original materials and projects stay local
Original documents, footage and editable projects stay on your device. Finished outputs remain local by default. An explicit publishing approval sends only the selected delivery copies and required metadata to your chosen destination.
Original documents, source footage and editable projects stay on your device. Finished outputs remain local by default. Publishing a selected delivery copy is a separate, user-approved transfer to a named destination; it does not upload the entire source collection or editable project.
Original avatar portraits and source audio are included in this local-file boundary. Using an avatar presenter does not turn your local source library into a public asset. Review presenter permissions and the selected output before delivery. Read the avatar presenter workflow.
Local files and model-service requests
Keeping original files local does not mean every AI operation runs offline. A model-assisted task can involve a network request and service metadata. Review the workflow documentation and the service selected for the task; local storage, model processing and publishing should be considered separately.
Approved publishing transfers
A publishing approval identifies the selected output files, destination account, accompanying metadata, visibility and action. Unrelated original files and editable projects stay outside that transfer. The receiving platform processes the selected delivery copy under its own terms.
Learning records sent to an LRS are separate from the lesson video and its local source material. An xAPI statement, a SCORM package and a cmi5 course launch have different runtime and destination requirements. Read the publishing and learning delivery documentation.
The studio films on this website are public showcase assets. Their delivery to a browser is separate from users’ private desktop projects. Explore local video projects.
Visiting the website
Your browser requests pages and media to display the website. Those requests include ordinary delivery information such as an IP address, requested URL and browser information. The hosting environment may process request logs to deliver and protect the website.
This website does not add a marketing analytics or advertising tracking integration. Studio videos are served as website media rather than through a third-party video player. Contact the team for information about the website’s hosting and service providers.
Contacting support
If you choose an email link, your email application sends a message to the team behind Martius and X-Pilot at support@x-pilot.ai. The team receives the address, message and any material you choose to include and uses them to handle the enquiry.
Contacting support does not upload files from a desktop project automatically. Choose what to share and identify the relevant workflow when asking for help.
Links to other services
An installer, installation guide or destination platform may be provided through an external service. That service has its own information and terms. Review them before sharing data or authorizing a transfer.
Questions and updates
Contact support@x-pilot.ai with a question about website requests, local project handling or information you have sent directly to the team. Explain the relevant interaction so the enquiry can be addressed.
The date above records the current edition. This page is updated when website data collection or the documented workflow boundary changes.