Lima Privacy Notice
Lima is a software-licence management platform operated by [Borea Labs legal entity name], [registered address] ("Borea", "we"). It explains what personal data Lima handles, why, and what you can do about it, for two groups:
- Part A — vendor staff: people who sign in to the Lima portal for a software vendor.
- Part B — end customers: traders who run a vendor's tool (an expert adviser for MetaTrader 4 or 5) under a licence managed through Lima. You never sign in; the tool talks to Lima's API on your behalf.
Part C applies to everyone. Privacy contact: [privacy@borealabs.com]. [DPO or EU/UK representative, if appointed.]
1. Who is responsible for your data
What this means: Borea, except for the contact details a vendor enters about its customers, where the vendor is responsible and Borea acts for it.
Borea is the controller for vendor staff accounts, licence and audit records, diagnostic reports and account snapshots. [Reviewer: for snapshots and diagnostics used for R&D, confirm independent versus joint controllership with the vendor.] For the name, email and reference a vendor enters when assigning a licence, the vendor is the controller and Borea its processor. Your vendor's own notice covers its use of your data outside Lima.
Part A — Vendor staff
2. What we collect about you
What this means: what you need to sign in, what you do in the portal, and enough to keep the account secure.
- Name, work email and the organisation that invited you.
- Password (held only as a hash by our identity provider, Neon Auth), authenticator-app secret if enabled, and recovery codes (hashed).
- Sign-in and session details: IP address, browser and device type, time, active sessions.
- Your portal actions — issuing, assigning and reassigning seats, downloads, snapshot switches — in an audit ledger with your name and the time.
- Emails we send you (invitations, password resets) and support correspondence.
3. Why we use it and on what basis
What this means: to run your account, keep it secure, and record who did what.
| Purpose | Lawful basis |
|---|---|
| Running your account, invitations, password resets | Contract between Borea and your vendor; legitimate interest in serving your organisation |
| Security: authentication, session review, detecting misuse | Legitimate interest in keeping Lima and vendors' data secure |
| Audit ledger of licence actions and downloads | Legitimate interest in an accountable record; legal obligation where it applies |
| Support | Legitimate interest in answering you |
4. Cookies
What this means: one session cookie; nothing for analytics or advertising.
The portal sets one strictly necessary session cookie, which ends when the session expires or you sign out. No analytics, advertising or third-party cookies.
Part B — End customers
5. How your data reaches us
What this means: from your vendor, and from the tool on your terminal.
We have no account for you and learn who you are only from your vendor. We receive: from your vendor, when it assigns you a licence, a name and optionally an email address and a reference; from the tool, on each licence check (about every 6 hours per running copy) and in diagnostic reports, the data in sections 6 to 8. Nothing comes from anyone else.
6. What the tool sends on each licence check
What this means: enough to confirm the licence and tie it to one trading account; no trading activity.
- The licence credential (a per-installation secret, held by us as a hash).
- The tool's name and version, and the platform (MT4 or MT5).
- The broker server name.
- Your trading account login number, stored as a keyed hash (a "fingerprint") so we recognise the same account next time; the raw number is not kept beyond what binding requires, and your vendor sees only a masked form.
- An installation identifier and timestamps.
Licence checks never contain your trades, positions, orders or broker credentials.
7. Diagnostic error reports
What this means: a bounded technical report when something goes wrong; never trade data, never credentials.
The tool sends the error code, module, counts, MetaTrader terminal build, operating system, HTTP status of failed calls, and timing. Reports are bounded in size and content: no trade data, free text or credentials. Borea operators use them to find and fix faults.
8. Account snapshots
What this means: unless switched off, the tool reports your account's balance, equity and currency once a day for analysis and R&D by your vendor and Borea; switching off stops new readings but does not delete old ones.
8.1 What. The trading account's balance, equity and currency, as reported by the MetaTrader terminal, once per account per day; we neither verify the figures nor convert currencies.
8.2 Purpose. Analysis and research and development by your vendor and by Borea: cohort statistics, trends, product decisions. Never to decide anything about you individually; never for marketing.
8.3 Default and switches. Reporting is on by default. Your vendor can switch it off for all its customers; you can switch it off for your account by setting the InpReportAccountSize input to false in the tool. Either switch stops future readings. Readings already collected are not deleted by the switch; ask for deletion under section 13.
8.4 Who sees readings. Your vendor, for its own customers' accounts; Borea operators, for any vendor's customers, only with a recorded reason and with every access logged; no other vendor.
8.5 Identity. We store readings against the account fingerprint and the licence, not your name; but your vendor can link a reading to your licence and Borea operators can see the contact details your vendor entered, so readings are pseudonymous, not anonymous.
9. Why we use your data and on what basis
What this means: licence checks and diagnostics keep the licence honest and the tool working; snapshots are for analysis, with an opt-out.
| Purpose | Data | Lawful basis |
|---|---|---|
| Confirming the licence, binding it to one account, limiting installations and reassignments | Licence checks (section 6) | Legitimate interests of your vendor (enforcing the licence it sold you) and of Borea (running the platform, preventing misuse) |
| Finding and fixing faults | Diagnostic reports (section 7) | Legitimate interest in keeping the tool and the service working |
| Analysis and R&D | Account snapshots (section 8) | [Legitimate interests of your vendor and of Borea in understanding how tools are used, balanced by the two opt-outs, the daily cadence and the absence of trade data — reviewer: confirm whether consent is required instead; see reviewer notes] |
| Licence administration and support for your vendor | Contact details (section 5) | On your vendor's instructions; your vendor's own lawful basis applies |
| Records, disputes, legal compliance | Licence records, audit ledger | Legitimate interest in accountable records; legal obligation where it applies |
You can object to legitimate-interest processing (section 13). Where the basis is consent, withdraw it at any time in the tool or through your vendor.
Part C — Everyone
10. Who we share data with
What this means: the providers that run Lima, your vendor, and nobody else unless the law requires; no selling, no advertising.
| Provider | Role | Data | Location |
|---|---|---|---|
| Vercel | Application hosting | Everything in transit; request logs | United States |
| Neon | Postgres database | All stored data | United States (AWS us-east-2) |
| Neon Auth | Vendor staff identity; password-reset emails | Staff name, email, password hash, authenticator secret | United States |
| Cloudflare | DNS; R2 object storage for tool files | Tool files; download authorisations | United States (region "enam") |
| Resend | Transactional email | Staff name and email; message content | United States |
| Google Workspace | Borea's own email | Whatever you send us | [United States / EU — confirm data-region setting] |
| [Error-reporting service, e.g. Sentry — not yet in use] | Application errors | Error context, possibly including identifiers | [TBD] |
| [Log and uptime monitoring provider — Better Stack per platform spec; confirm whether live] | Request logs, availability probes | Request metadata, IP addresses | [TBD] |
We also share with your vendor (its own customers' records, contact details, check-in state and snapshot readings), with authorities and professional advisers when the law requires or to defend legal claims, and with a successor to the Lima business, under this notice.
11. International transfers
What this means: Lima runs in the United States; for data protected by EU, UK or similar law we rely on the safeguards below.
Every provider above is in the United States. For data protected by the EU GDPR, UK GDPR or similar laws, transfers rely on [the EU-US Data Privacy Framework and its UK Extension where the provider is certified; otherwise the European Commission's Standard Contractual Clauses with the UK Addendum or IDTA — reviewer to confirm per provider]. Ask [privacy@borealabs.com] for a copy.
12. How long we keep data
What this means: minutes or days for links and keys, 180 days for diagnostics, no automatic deletion yet for snapshots, licence records for the vendor relationship's life.
| Data | Retention |
|---|---|
| Invitation links | 7 days |
| Activation keys | 7 days; a hash stays with the licence record |
| Download links | 5 minutes; the authorisation stays in the audit ledger |
| Diagnostic error reports | 180 days, then deleted |
| Account snapshots | No automatic deletion at present; kept until deleted on request (section 13) or until we set a period. [Reviewer: a stated period or review cycle is needed for storage limitation.] |
| Licence records, activations, audit ledger, activity | Life of the vendor relationship, then as required for records, audit and disputes [state a period, e.g. 6 years] |
| Vendor staff accounts | Until removed or the relationship ends, then [90 days] |
| Sessions | Until signed out or expired |
| Request logs at providers | [Short period — confirm; the platform spec allows up to 30 days] |
| Support email | [period] |
13. Your rights
What this means: access, correction, deletion, objection, complaint to a regulator; end customers start with their vendor.
Depending on where you live, you can ask to access, correct, delete or restrict your data, object to legitimate-interest processing, receive a portable copy of data you provided, and withdraw consent where that is the basis. We may need to verify your identity.
Vendor staff: write to [privacy@borealabs.com].
End customers: Lima has no identity for you, so start with your vendor, which can identify your licence and pass the request to us; for data we process on its behalf we act on its instructions. For account snapshots and diagnostic reports, which we hold in our own right, you can also write to [privacy@borealabs.com] with your vendor's name and licence details.
Deleting account snapshots is currently a manual process. Switching off does not delete readings; on request an operator removes the exact readings for your account, within [30 days]. Daily aggregates that no longer identify an account are not deleted.
We answer within one month (up to three for complex requests) and say why if we refuse. You can complain to your data protection authority: [name — e.g. Garante per la protezione dei dati personali (Italy); Information Commissioner's Office (UK); National Privacy Commission (Philippines)].
14. Security
What this means: hashed credentials, authenticators for operators, short-lived links, logged access to sensitive data.
Passwords and licence credentials are stored as hashes, account login numbers as keyed hashes. Borea operators must use an authenticator app; vendor staff can. Invitation, activation and download links are short-lived. Operator access to snapshot readings needs a recorded reason and is audited. If a breach affects you we notify you and any regulator as the law requires.
15. Automated decisions
What this means: licence checks are allowed or denied automatically by licence rules, not by profiling.
Licence checks are answered automatically from the licence's state (valid, expired, revoked, reassigned, account mismatch, blocked version); no profiling, and snapshots are not used. [Reviewer: confirm this falls outside Article 22 or within the contract exception.]
16. Children
What this means: not for anyone under 18.
Lima and the tools it licenses are for adults. We do not knowingly hold data about anyone under 18 and delete it if we learn we do.
17. Region-specific information
What this means: additions for particular jurisdictions, to be completed by the reviewer.
- United Kingdom: [UK GDPR addendum — UK representative if required; ICO contact.]
- California: [CCPA/CPRA — Borea is likely below the thresholds; confirm. If applicable: categories, no sale or sharing, consumer rights.]
- Philippines: [Data Privacy Act 2012 — confirm lawful-basis wording and NPC requirements.]
- [Other jurisdictions]
18. Changes and contact
What this means: we tell you when this changes in a way that matters.
Material changes are notified to vendor staff by email and to end customers through their vendor; the version and effective date at the top change. Contact: [Borea Labs legal entity name], [registered address]; [privacy@borealabs.com]; [DPO or EU/UK representative, if appointed.]