Privacy Policy

This Privacy Policy was last updated on June 5, 2026. It applies to motornauts.com, public website inquiries, pilot tenant onboarding, staff users, customer portal users, support communications, and the Motornauts SaaS product.

Motornauts is an early-stage startup product operated by Isira Adithya from Colombo, Sri Lanka. Formal company registration is planned, and public company details will be updated when that is complete.

Motornauts controls website leads, account and administration records, platform operations, billing and support communications, and product or security analytics.

Service centers primarily control their own customer, vehicle, and service records. Motornauts processes that tenant data to provide the SaaS and may use limited protected operational analytics for service reliability and product improvement.

In limited cases, Motornauts and a service center may jointly decide how operational data is used for service improvement. Motornauts does not use service-center customer data for broad direct marketing unless a separate opt-in flow is added.

When you contact Motornauts, request onboarding, ask for a quotation, use support, or create a pilot account, we may collect contact and account details from you.

• Names, email addresses, phone numbers, job titles, tenant or workshop names.
• Messages, support requests, meeting notes, quotation details, and onboarding context.
• Authentication identifiers, session information, staff role details, and security logs.
• Billing, invoice, payment-request, and manual pilot agreement records where relevant.

Service centers that use Motornauts may enter or generate operational data in the SaaS. That data can include tenant configuration, branches, staff, services, customers, vehicles, appointments, repair orders, technician inspections, findings, estimate and approval records, invoices, feedback, generated PDFs, audit records, and service-history timelines.

Customer portal users may provide or view profile details, vehicles, service requests, appointment information, approvals, feedback, documents, invoices, payment request status, and service history depending on the modules the service center enables.

Motornauts may handle private documents, inspection photos, generated estimate or invoice PDFs, and other service artifacts where a tenant uses those features. These records are intended for operational workshop use and customer service visibility, not public publication.

We use data to respond to inquiries, prepare quotations, onboard pilot tenants, provide the SaaS, authenticate users, keep tenant records separate, support users, maintain audit and billing records, troubleshoot incidents, improve reliability, and meet legal, security, and operational obligations.

Contact-form details are used for direct replies, quotations, onboarding, support, and privacy or legal requests. We do not use inquiry details for broad marketing campaigns unless a separate explicit opt-in flow is introduced later.

Motornauts may use limited protected operational analytics to understand product usage, reliability, errors, security events, performance, feature adoption, and support needs. Analytics should be used to operate and improve the product, not to expose one tenant's customer or service records to another tenant.

Motornauts uses authentication and session technologies to sign users in, keep accounts secure, route users to the right tenant workspace, remember security state, and prevent unauthorized access. Some cookies or similar storage may be essential for login, routing, fraud prevention, and product operation.

The current public policy scope includes Clerk for authentication, PostgreSQL for structured data storage, private storage for documents and PDFs, application infrastructure, and email/contact handling. Providers should only receive the data needed to provide their part of the service, support the platform, or meet security and operational requirements.

Online payments, SMS, custom domains, inspection videos, and some media workflows are optional, tenant-enabled, pilot, or future modules. If a tenant enables one of those modules, additional provider terms, consent notices, readiness checks, or setup steps may apply before the feature is used in production.

Motornauts may share data with the relevant service center, authorized tenant staff, customer portal users tied to their own records, service providers, and advisers or public authorities where required for security, compliance, legal process, or dispute handling.

Motornauts does not sell service-center customer data. We do not publish private workshop records, inspection media, invoices, or generated PDFs as public marketing material.

Some infrastructure, authentication, storage, support, or email providers may process data outside Sri Lanka depending on their hosting locations and service configuration. Where this happens, Motornauts aims to use reputable providers and reasonable safeguards suitable for a pilot-stage SaaS product.

Motornauts is designed around tenant separation, role-based access, private document and media access, audit records, authenticated sessions, and server-side handling of sensitive provider credentials. No internet service can be guaranteed completely secure, but we use practical safeguards to reduce unauthorized access, loss, misuse, and cross-tenant exposure.

Service centers are responsible for telling their own customers and staff how Motornauts is used in their workshop, getting any required customer permissions, keeping staff access current, entering accurate records, and using customer notifications only for lawful and appropriate service-center communications.

We keep records while needed for service delivery, billing, audit, legal, security, support, product operations, incident investigation, and tenant account administration. Retention periods can vary by record type, tenant configuration, pilot agreement, and operational need.

Where allowed and technically practical, we delete, export, return, restrict, or anonymize data after valid tenant or data-subject requests and after required retention periods end. Some records may remain in backups, audit logs, dispute files, or security records for a limited period where needed.

Depending on your relationship with Motornauts and the applicable law, you may ask for access, correction, deletion, restriction, objection, export, or withdrawal of consent for relevant personal data. We may need enough information to verify the request and locate the correct tenant, account, customer, vehicle, or service record.

Send privacy requests through the Privacy Requests form or email [email protected]. Customer operational-data requests may need to be coordinated with the relevant service center because the service center primarily controls those customer, vehicle, and service records.

Motornauts is built for service centers, staff users, and vehicle owners. It is not intended as a product for children. Tenants should avoid entering unnecessary sensitive personal data into workshop records and should keep inspection notes, media, and customer communications relevant to the service work.

Motornauts may update this Privacy Policy as the product, providers, modules, or legal obligations change. The updated date above will be changed when a material update is made, and important pilot-customer changes may also be shared by email or onboarding channels.

For privacy, support, sales, onboarding, or legal requests, contact [email protected].