Privacy Policy

• Account data. When you create an account we store your email address, display name, and a chosen handle. You may optionally save a reusable signature image to your profile.
• Document content. The information you enter into a transport document — which may include the names, addresses, and contact details of shippers, carriers, and consignees; descriptions of goods; vehicle and registration details; and dates and locations of transport.
• Signature data. When you or an invited party signs a document, we store the drawn signature image, the signatory’s name, and — to preserve the document’s evidentiary integrity — the IP address and timestamp recorded at the moment of signing.
• Payment data. Paid plans are processed by Stripe. We do not receive or store your full card number; we retain only the Stripe customer and subscription identifiers needed to manage your billing.
• Support communications. Messages you send us through in-app chat or email, so we can respond and provide support.
• Usage and advertising data. Which features you use (for example, that a document was created or signed), and — with your agreement — how you found Meight Simple: the ad campaign or click identifier that brought you to the website or the app. See Analytics and advertising.
• Technical data. Standard server logs and device information generated when you use the service, used for security, diagnostics, and reliability.

• To create, share, and sign transport documents, and to make signed documents verifiable.
• To operate your account and let invited parties access the documents shared with them.
• To process payments and manage subscriptions.
• To provide customer support and respond to your requests.
• To understand how the service is used and which of our ads bring people to it (see Analytics and advertising).
• To keep the service secure, prevent abuse, and comply with our legal obligations.

We share document content with the parties you invite to view or sign a document — that is the purpose of the service. Beyond that, we do not sell your personal data. We use a small number of trusted service providers who process data on our behalf under data-processing agreements:

• Supabase — application hosting, authentication, and database storage.
• Stripe — payment and subscription processing.
• Resend — delivery of transactional emails (such as invitations and notifications).
• Datadog (EU) — error and performance diagnostics.
• Mixpanel (EU) — product analytics.
• Google (Firebase Analytics and Google Ads) and Apple (Search Ads) — advertising measurement, as described in Analytics and advertising.

We measure how Meight Simple is used and which of our ads bring people to it, so we can improve the service and spend on the campaigns that work. We never share the content of your documents, your contacts, or your signatures for this purpose.

• Product analytics. Our servers record events such as sign-up, document creation, signing, and subscription changes in Mixpanel (EU data residency), together with your display name and email domain, so we can understand how the service is used.
• Website. If you arrive through one of our ads and accept the cookie notice, we store the campaign parameters and the ad click identifier (such as Google’s gclid) in a first-party cookie for up to 90 days. When you then sign up, create a document, or subscribe, we report that event with the click identifier to Google Ads. Accepting also loads Google Analytics for Firebase, which sets Google’s own cookies (such as _ga) and reports page views and those same events to Google, so Google Ads can attribute them to our campaigns; it is not used for ad personalization or remarketing. If you decline, the cookie is not set, Analytics is not loaded, and nothing is reported. Links on our own pages (such as the sign-up link on a shared document) carry only campaign parameters, no advertising identifier; those are stored in the same cookie without a notice, used only to record in Mixpanel where your sign-up came from, and never sent to Google.
• Mobile apps. The apps use Google Analytics for Firebase to report installs, app opens, sign-ups, document creation, and subscriptions to Google, so Google Ads can attribute them to our campaigns. On Android this may include the device’s advertising ID. On iOS, advertising signals and the advertising identifier (IDFA) are used only if you allow tracking when the app asks (Apple’s App Tracking Transparency prompt); otherwise only analytics without advertising identifiers is sent. At sign-up the apps also send us how the app was installed — the Google Play install referrer on Android, or Apple’s Search Ads attribution token on iOS, which we exchange with Apple for the campaign that led to the install.
• Your choice.In the apps this is controlled by the Privacy Policy checkbox on the sign-in screen, which you can untick at any time under Settings → Legal; unticking stops these reports from that device. On iOS you can also change the tracking permission at any time in Settings → Privacy & Security → Tracking. On the website, it is the cookie notice shown to visitors who arrive from an ad. Withdrawing does not affect processing that took place before.