This policy explains how we process personal data in line with Law no. 195/2024 on the protection of personal data of the Republic of Moldova and, where it applies, the EU General Data Protection Regulation (GDPR).
1. Who we are
INNOSOFT SOLUTIONS SRL provides LoadSense and is the controller of the personal data described here.
| Controller | INNOSOFT SOLUTIONS SRL, IDNO 1025600069838 |
|---|---|
| Privacy contact | hello@getloadsense.com |
LoadSense is built for businesses. Where a dispatch company gives its dispatchers access, the company decides who is invited, and we process their account data to provide the Service to that company.
2. Data we collect
| Category | Examples | Source |
|---|---|---|
| Account data | Name, email, password (stored only as a secure hash), role | You or your account owner |
| Company data | Company name, MC number, phone, plan and seats | You |
| Your content | Email templates and signature, truck profiles and cost settings, load alert rules, internal notes | You |
| Contact history | Which loads your team emailed or called, when and by whom (see section 3) | The extension, when you email or call a broker |
| Extension sign-in | The email and password you type in the extension popup, sent over HTTPS to sign you in (the extension doesn’t keep the password), then a sign-in token kept in your browser | You |
| Load board data | The loads your DAT One page shows: broker name, MC and DOT numbers, phone, email, comments, rate, lane, dates and equipment, and the origin of your search. Handled as described in section 3. | The DAT One pages you open |
| Factoring account data (optional) | Your RTS Pro access token or your FactorView session, your portal address and factoring company’s name, and each broker’s rating, credit, buy limit, open balance, days to pay and no-buy notes. Stays in your browser (see section 3). | RTS Pro or FactorView, when you connect them |
| Email connection (optional) | Your Gmail or Outlook address and an encrypted token that lets LoadSense send email for you (see section 4) | Google or Microsoft, when you connect your mailbox |
| Emails you send through LoadSense | Recipient, subject and body of each message, passed through our servers to Google or Microsoft and not stored (see section 4) | You, through the extension |
| Security and usage data | Sign-in times, device and browser type, IP address in security logs | Automatically |
| Product analytics | Pages you open on this website and in the dashboard, clicks, scrolling and recordings of those visits with everything typed into forms hidden; which LoadSense tools you use in the extension (for example opening the card or the map), never the loads themselves | Automatically, through PostHog |
| Support | Messages you send us | You |
| Payments | Plan, amount, currency, date, payment status and transaction id, subscription status, the payer’s name, email and country, and the card type and last four digits. Card numbers are entered on Paddle’s or Paynet’s page and are never received or stored by us. | You and our reseller Paddle or payment processor Paynet |
3. How the extension handles board data
The LoadSense extension runs on DAT One (one.dat.com) and on the LoadSense dashboard, and works with your RTS Pro or FactorView account if you connect one. This section covers everything it reads, keeps and sends to give you profit, routes, broker credit and email on the board.
What it reads on DAT One
It reads the answers your browser already receives for two things: your load searches and the load details you open. That includes the fields listed in section 2, and phones and emails written in load comments. When you copy an MC or DOT number from DAT’s Company block, it removes the prefix from what you copied. It doesn’t read your DAT password or DAT’s access tokens, and it doesn’t read other sites you visit.
What stays in your browser
Load details are processed in your browser and are not stored on our servers, with the exceptions listed under “What is sent to our servers”. Profit calculations, phones and emails found in comments and broker credit all stay on your computer. The extension keeps these in Chrome’s storage:
- your LoadSense sign-in tokens;
- a copy of your templates, signature, truck profiles and settings, refreshed from your account;
- per-load edits you make on the board (for example a negotiated rate), kept 3 days;
- which factoring account is connected and, in memory only until the browser closes, the RTS Pro token and the credit answers.
What is sent to our servers
- Contact history: when you email or call a broker, we store the load’s posting id and a short fingerprint (broker, lane, pickup date and equipment type), with your user account and the time, so your team can see what was already contacted and spot reposts.
- Contact checks: for each search and load you open, the posting ids and fingerprints of those loads are sent to us to find which ones your team already contacted. We use them to answer and don’t store them.
- Map and route requests: pickup, delivery and truck coordinates (the truck’s position is the origin of your DAT search) go through our servers to our map and routing provider, HERE, to draw the route, tolls and map. HERE doesn’t receive your identity. Routes are saved for up to 30 days, rounded to about 100 meters and without your name or account, so the same lane isn’t requested twice.
- Oversize permit estimates, if your plan includes them: the route and the load’s dimensions, used for the estimate and not stored.
- Emails you send through a connected Gmail or Outlook account (see section 4).
- Usage statistics: when you are signed in, the extension tells us which of its tools you used (for example that you opened the card, the map or the profit breakdown, or ran a search and how many loads it returned), so we can see what helps dispatchers and what doesn’t. These events never include the broker, rate, lane or any other load detail, and the extension does not record your screen.
- Sign-in and settings requests: your sign-in, and regular requests for your account settings, which carry your LoadSense token and the extension version.
Factoring accounts: RTS Pro and FactorView
Connecting a factoring account is optional. It shows broker credit from your own account on the board. Your factoring password, tokens and credit answers are never sent to LoadSense’s servers or to anyone other than your factoring site. We use them only to show you credit on the board.
- RTS Pro: you sign in on RTS Pro’s own site as usual. Using Chrome’s
webRequestpermission, the extension reads the Authorization header of requests to*.rtspro.com, only to pick up the access token RTS Pro’s web app sends. It doesn’t change those requests. It keeps the token in browser memory until the browser closes, and uses it, until it expires, to ask RTS Pro about the MC number of each broker on your board. - FactorView: you enter your portal address and accept Chrome’s prompt for
*.factorview.com, then sign in on the portal as usual. The extension uses the session your browser already has there to search the MC number of each broker on your board and read that debtor’s page. It only reads: it never links a debtor or submits a new one to your factoring company. - Who receives what: RTS Pro or your factoring company’s FactorView portal receives the MC numbers of the brokers on your board, under your own account and their own terms. Credit answers are kept in browser memory and asked again after 6 hours.
- Turning it off: click Disconnect on the dashboard’s Factoring page. Removing the extension also deletes what it keeps in your browser.
What the extension doesn’t do
The extension does not log in to load boards, run load searches or book loads, and it does not act on your behalf except as described here. Emails either open in your own email program or, if you connect Gmail or Outlook, are sent from your mailbox when you click the email button or, on plans with load alerts, when an alert you set up to email automatically finds a matching load (see section 4). We never read your mailbox.
The use of data received through the extension complies with theChrome Web Store User Data Policy, including the Limited Use requirements. We use this data only to provide and improve the features described here. We don’t sell it, use it for advertising or to decide creditworthiness or lending, and people don’t read it except with your permission, for security, or where the law requires it.
4. Gmail and Outlook connection, Google user data
Connecting Gmail is optional. When you click Connect Gmail in the dashboard, Google asks you to allow LoadSense tosend email on your behalf (the gmail.send permission) and to see your email address.
- What we access: your Google account email address, and permission to send messages. We can’t read, search, delete or modify your emails, contacts or other Google data.
- How we use it: only to send the email you ask for: when you click the email button on a load, we send the message you see (from your template, to that load’s broker) from your Gmail address. A copy appears in your Gmail Sent folder. Nothing is sent without your click, or without a load alert you set up yourself to email automatically.
- Storage and protection: we store your Gmail address and Google’s refresh token, encrypted (AES-256), on our servers. We don’t store the emails we send for you: the recipient, subject and body pass through our servers to Google and are not saved.
- Sharing: we don’t share, sell or transfer Google user data to anyone, and we don’t use it for advertising or to train AI models.
- Removal: click Disconnect in the dashboard (Email accounts) to delete the token and revoke our access at Google. You can also remove LoadSense at myaccount.google.com/permissions. Closing your LoadSense account deletes it too.
LoadSense’s use and transfer to any other app of information received from Google APIs will adhere to theGoogle API Services User Data Policy, including the Limited Use requirements.
Outlook / Microsoft 365 works the same way and is also optional. Microsoft asks you to allow LoadSense to send email on your behalf (Mail.Send) and to see your basic profile and email address (User.Read). We use this only to send the emails described above, store your address and Microsoft’s refresh token encrypted (AES-256), don’t store the messages and never read your mailbox. Disconnect it in the dashboard (Email accounts), or remove LoadSense from your Microsoft account’s app permissions.
5. How we use data
| Purpose | Legal basis (Law no. 195/2024; GDPR where it applies) |
|---|---|
| Provide the Service, your account, team features and support | Performance of our contract with you |
| Secure the Service, prevent fraud and license sharing | Legitimate interests |
| Take payments and run subscriptions through Paddle or Paynet, issue invoices and handle refunds | Performance of our contract with you |
| Keep accounting and tax records | Legal obligation |
| Send email from your Gmail or Outlook when you connect it | Your consent, which you can withdraw by disconnecting it |
| Show broker credit from your factoring account when you connect it | Your consent, which you can withdraw by disconnecting it |
| Improve the website, the dashboard and the extension using usage statistics and visit recordings (see section 6) | Legitimate interests |
| Product news and offers (you can opt out any time) | Legitimate interests or consent, as required |
| Measure and improve our own ads on Facebook, Instagram and Google Search (see sections 6 and 7) | Legitimate interests or consent, as required |
We don’t sell personal data. We use it only to measure our own ads, never to show other companies’ ads.
6. Who we share it with
We don’t sell personal data. We share it only with these recipients, and only what each one needs:
- hosting and infrastructure providers that run our servers;
- our email delivery provider, Resend, for emails from LoadSense such as sign-up codes, invitations and billing reminders (your email address and the message);
- Google or Microsoft, only to send the emails you ask for when you connect Gmail or Outlook;
- RTS Pro or your factoring company’s FactorView portal, if you connect them: your browser sends them the MC numbers of the brokers on your board, directly and under your own account. This doesn’t go through us;
- Paddle.com, our online reseller and Merchant of Record for customers outside Moldova: it receives your name, email, country and payment details to sell you the subscription, charge renewals, issue invoices, handle tax and refunds, and processes them as an independent controller under its own privacy notice. Its checkout window loads from Paddle’s servers when you pay;
- Paynet (payment processor in Moldova) and the card networks and banks involved in a payment (Visa, Mastercard), to process payments and refunds;
- HERE, our map and routing provider (coordinates and map areas only, sent from our servers);
- DeBounce, to check at sign-up whether an email domain is a throwaway one (only the domain, never your address);
- Meta (Facebook and Instagram), to measure our own ads: when you visit this website or the sign-up page, sign up, first sign in from the extension or pay, we send Meta an event with your email and account id in hashed (unreadable) form, your IP address, browser details and the Meta cookie ids. We never send the content of your account, your loads or your emails;
- Google Ads, to measure our own search ads: this website and the sign-up page load the Google tag, which tells Google about your visit and, when you sign up, that an account was created after a click on one of our ads. We don’t send Google your email, your account or anything you do in LoadSense;
- PostHog (product analytics, hosted in the European Union), to understand how people use LoadSense: page views, clicks and visit recordings on this website and the dashboard (form fields are hidden), the extension tools you use, and your account id, name, email, company and plan once you sign in. The extension sends no recordings and no load details;
- LoadSense partners: if you sign up through a partner’s link or promo code, that partner sees your company name, your email with most of it hidden (for example
j***@gmail.com), your sign-up date, whether you are on a trial or paying, and the commission they earned. They never see your payment details, your loads or your emails; - Gmail, Outlook or Google Maps, when you click a link in the extension that opens them with a draft email or a route;
- accountants, auditors and legal advisers bound by confidentiality;
- public authorities, courts or law enforcement, only where the law requires it.
Our providers act on our instructions under contracts that require them to protect the data.
If LoadSense is involved in a merger or acquisition, data may transfer to the new owner under this policy.
7. Cookies
The LoadSense dashboard uses one essential cookie to keep you signed in securely. This website and the dashboard’s sign-up page also use the Meta Pixel, which sets Meta cookies (_fbp, and _fbc when you arrive from one of our ads) so we can tell which of our ads led to a sign-up. They also load the Google tag, which sets Google Ads cookies (such as _gcl_aw when you arrive from one of our Google ads) for the same purpose. The rest of the dashboard doesn’t load either of them. This website and the dashboard set a PostHog cookie (ph_…_posthog) with a random visitor id, so we can follow a visit from the website to sign-up and see where people get stuck. A first-party cookie, ls_src, keeps for up to 90 days how you reached us (campaign tags in the link, the first page you opened and the site that sent you), so we can see which campaigns bring customers; it is saved with your account when you sign up. Another first-party cookie, ls_ref, keeps for up to 60 days the code of the partner whose link you opened, so the partner gets credit and you get their discount. You can block these cookies in your browser settings and manage ad preferences in your Facebook, Instagram or Google settings; LoadSense works the same without them.
8. How long we keep data
- Account, company and content data: while your account is active, then deleted or anonymised within 90 days of closure.
- Contact history: up to 12 months.
- Gmail or Outlook connection: until you disconnect it or close your account.
- In the extension: sign-in tokens until you sign out or remove the extension; per-load edits 3 days; the RTS Pro token and credit answers in browser memory until the browser closes. Removing the extension deletes all of it.
- Saved routes (no account attached): up to 30 days.
- Emails we send you, such as billing reminders: while your account is active.
- Usage statistics and ad measurement: as long as they’re useful for those purposes, within the retention settings of PostHog and Meta.
- Security logs: up to 12 months.
- Payment and billing records: as long as accounting and tax laws of the Republic of Moldova require, then deleted.
9. Security
We use encryption in transit (HTTPS), hashed passwords, short-lived sessions, access controls and regular updates. No system is perfectly secure; if a breach affects your data, we will notify you and the authorities as the law requires.
10. International transfers
We operate from the Republic of Moldova. Some providers process data in other countries: our servers and map provider may be in the European Union, and Google (Gmail), Microsoft (Outlook) and your factoring site may process data in the United States. Transfers to the European Union go to countries with an adequate level of protection. For other countries we transfer data only with the safeguards required by Law no. 195/2024, such as standard contractual clauses, or where the transfer is needed to provide the Service you asked for. You can ask us for details of these safeguards.
11. Your rights
Under Law no. 195/2024 (and the GDPR where it applies) you have the right to:
- be informed about how your data is processed (this policy);
- access the personal data we hold about you and get a copy;
- rectify inaccurate or incomplete data;
- erasure of your data (“right to be forgotten”);
- restrict how we use your data;
- data portability: receive your data in a common machine-readable format;
- object to processing based on legitimate interests, including direct marketing;
- not be subject to a decision based solely on automated processing that significantly affects you (we don’t make such decisions);
- withdraw consent at any time, where processing is based on consent, without affecting earlier processing;
- complain to the National Center for Personal Data Protection of the Republic of Moldova (datepersonale.md) or to your local data protection authority, and go to court.
California residents: we don’t sell or share personal information for cross-context behavioral advertising.
12. How to make a request
- Access, correction or deletion: email hello@getloadsense.com from the email address on your account. Say which right you want to use.
- Yourself, in the dashboard: you can view and change your name, company details, templates and truck profiles in Settings, disconnect Gmail, Outlook or a factoring account, and sign out other sessions at any time.
- We may ask you to confirm your identity before acting on a request, so that we don’t disclose data to the wrong person.
- We answer free of charge within 30 days. If a request is complex, we may extend this as the law allows and will tell you why.
- If your account was created by your employer (a company account), we may forward your request to them.
13. Children
The Service is for business use and not directed to children under 16. We don’t knowingly collect their data.
14. Changes
We may update this policy. We will post the new version here and, if changes are significant, tell you by email or in the dashboard.
15. Contact
INNOSOFT SOLUTIONS SRL, IDNO 1025600069838. Privacy requests: hello@getloadsense.com.