Privacy written for the actual product, not a generic template

This policy reflects how Loadvis handles account data, loading plans, calculation tasks, result files, and billing records inside the container loading platform.

Last updated: March 7, 2026

This Privacy Policy explains how Loadvis, an independently maintained product by Tom Mcfly, collects and uses information related to the service.

Loadvis is a loading optimization service independently built and maintained by Tom Mcfly. That means the privacy scope is tied to saved plans, user accounts, calculation history, result delivery, and payment records, not just anonymous page visits.

We keep this page focused on the product that exists today: email and Google sign-in, saved planning data, asynchronous calculation tasks, result outputs, point recharges, and subscription billing.

Privacy at a glance

We collect account and planning data to run the service, not to sell a user profile.
We keep billing and usage records that are needed to process payment, prevent abuse, and support account history.
We may use infrastructure, authentication, storage, and payment providers when they are necessary to operate the platform.
Users can contact us to request access, correction, or deletion of personal data, subject to operational and legal retention needs.

Key Facts

Core data: Account, plan, task, result, billing. The service stores the information needed to create, run, and review loading work.
Authentication: Email login + Google sign-in. Session and identity data are used to keep accounts secure and accessible.
Payments: Stripe checkout and subscription records. Payment processing is delegated to the payment provider rather than handled directly on our servers.
Storage: Application database and file storage. Plan results, generated outputs, and uploaded assets may be stored with infrastructure providers.

What information we collect

The platform needs more than a browser cookie because users create projects, save cargo data, run calculations, and pay for usage.

Account data such as email address, password hash, profile name, avatar, and sign-in session details.
Verification and recovery data such as email codes and password reset records.
Optional third-party login identifiers when a user chooses Google sign-in.
Business data including loading plans, product dimensions, weight settings, container definitions, tray settings, calculation rules, task history, and result records.
Billing data such as point account changes, recharge history, Stripe checkout references, subscription references, and payment status.
Technical and security data such as IP address, browser or device context, server logs, and session information needed to operate and protect the service.

How we use information

Each data category is tied to an operational need inside the product rather than collected for unrelated marketing purposes.

To create accounts, authenticate users, and protect sign-in and password recovery flows.
To save projects, run loading calculations, generate outputs, and let users revisit prior results.
To manage queues, task execution, troubleshooting, and platform reliability.
To process point recharges, subscriptions, invoicing, and anti-fraud checks.
To respond to support issues, account requests, and legitimate legal obligations.

When information may be shared

We do not describe data sharing in abstract terms. Sharing happens only when the service needs another provider to do a specific job.

Authentication providers, such as Google, when the user signs in through that provider.
Payment providers, such as Stripe, to complete checkout, subscriptions, and related billing records.
Hosting, database, queue, or storage providers that help run the application and store generated files or uploaded assets.
Professional advisers, regulators, or law enforcement when disclosure is required by law or reasonably necessary to protect the platform, users, or business operations.

Retention, security, and cross-border processing

Some information must remain available after a session ends because users expect plan history, billing history, and account continuity.

Account, plan, task, result, and billing records may be retained for service continuity, dispute handling, fraud prevention, accounting, and legal compliance.
When data is no longer needed, it may be deleted, minimized, or retained only in the limited form required for compliance or abuse prevention.
We use reasonable technical and organizational safeguards, but no online system can guarantee absolute security.
Depending on hosting, storage, authentication, and payment infrastructure, data may be processed in more than one country or region.

User choices and requests

Privacy rights still need to fit the operational nature of the product, especially where account history or billing records are involved.

Users can update parts of their profile and account settings inside the service.
Users can manage future subscription renewal status when that option is available in account settings.
Users may request access, correction, or deletion of personal data by contacting us.
Browser settings can be used to manage cookies, although required account and session features may stop working if essential cookies are blocked.
The service is intended for practical and professional use rather than children.

Privacy contact

If you have questions about privacy, data handling, or account-related requests, contact the channels below.

Email: [email protected]. Use this for privacy questions, data handling issues, and account-related requests.
Website: loadvis.com. Public product and billing pages are available on the main site.
Applies to: loadvis.com and related product workflows. This policy is written for the public website, account flows, and saved planning features of the service.