Privacy policy

01Two different roles

This policy covers Joldisoft LLC, 1001 S. Main St., Ste 600, Kalispell, MT 59901, United States, and it distinguishes two situations, because our obligations differ between them.

As controller, we handle data about our own prospects, customers and website visitors — the people who fill in a demo form or sign a contract with us. As processor, we host and process rider, driver and trip data on behalf of an Operator running their platform on Omei. In that second case the Operator is the controller and decides what is collected and why; we act on their documented instructions.

If you are a rider or a driver on a platform built with Omei, the policy that governs your data is the Operator's, not this one. Contact them, and they can reach us.

02What we collect as controller

Only what we need to sell, deliver and support the platform. We do not sell personal data, and we do not build advertising profiles.

• Contact data: name, work email, phone number and company, from demo requests and contact forms.
• Enquiry data: the market, fleet size and services you tell us about so we can size a plan.
• Account data: administrator names and emails for your Omei console.
• Billing data: company details and invoice records. Card details are held by our payment processor, not by us.
• Support data: the correspondence and tickets you raise with us.
• Website data: pages viewed, referrer and approximate location derived from IP, in aggregate.

03Why we use it

Each use has a defined basis: performing our contract with you, complying with a legal obligation, or a legitimate interest we have assessed.

• Responding to your enquiry and running demos — pre-contract steps at your request.
• Providing, supporting and maintaining the platform — contract.
• Invoicing, accounting and tax records — legal obligation.
• Securing the service and preventing abuse — legitimate interest.
• Improving the product using aggregated, non-identifying usage data — legitimate interest.
• Sending marketing, only where you have opted in — consent, withdrawable at any time.

04Operator data we process

Platforms built on Omei process rider and driver personal data: names, contact details, location during trips, trip history and payment records. That data belongs to the Operator and is held in a database isolated to their deployment.

We access it only to operate, support and troubleshoot the platform, or where an Operator asks us to. Access is limited to staff who need it, granted by role, and recorded. We do not use one Operator's data to benefit another, and we do not use it to train models.

05Who we share it with

A short list of sub-processors, each engaged under contract and each limited to what its function requires: cloud infrastructure and hosting providers, our payment processor for our own invoicing, transactional email and messaging providers, and support and analytics tooling.

We also disclose data where legally compelled, and we will tell the affected party unless we are prohibited from doing so. We provide a current sub-processor list on request and give notice before adding a new one that processes Operator data.

06International transfers

Joldisoft is based in the United States and our infrastructure providers operate globally. Where personal data moves out of its region of origin, we rely on standard contractual clauses or an equivalent lawful transfer mechanism.

Operators with data-residency requirements can be deployed to dedicated infrastructure in a nominated region on the Scale plan. Raise it during scoping rather than after launch — it is much easier to accommodate before go-live.

07How long we keep it

Enquiry data is kept for two years from the last contact unless you ask us to delete it sooner. Contract, invoice and tax records are kept for seven years as US law requires. Support correspondence is kept for three years.

Operator platform data is retained for the life of the subscription and deleted within ninety days of termination, after we have provided the agreed export — or sooner if the Operator instructs us to.

08Security

TLS on every connection and encryption at rest for stored data. Card details never touch the platform: payments run through tokenised, PCI-compliant gateways held in the Operator's own merchant account.

Internal access is role-based and least-privilege, sensitive actions are logged, backups run daily with point-in-time restore, and our recovery procedure is tested rather than merely documented. If a breach affects your data we will notify you without undue delay and tell you what we know, including what we do not yet know.

09Your rights

Depending on where you live you may have rights to access, correct, delete, port or object to the processing of your personal data, and to withdraw consent to marketing at any time. Write to privacy@omei.app and we will respond within thirty days.

If you are a rider or driver on an Operator's platform, send the request to that Operator — they are the controller. We support them in answering it, and we will not action such a request directly without their instruction.

10Cookies and contact

This website uses only what it needs to function and to understand aggregate traffic. We do not run advertising trackers or sell audience data.

Questions about this policy, or about a data processing agreement, go to privacy@omei.app, or by post to Joldisoft LLC, 1001 S. Main St., Ste 600, Kalispell, MT 59901, United States.