Access and account
Name, company, position, work email, role, approval and activation state, NDA confirmation metadata, language preference, and sign-in timestamps.
Privacy by design
Privacy Policy
How this restricted business workspace handles account, security, project, and calculation data.
Review-ready draft — not legal certification
Technical behavior and public corporate facts are documented. The operator must still approve legal bases, providers, transfers, retention periods, regional wording, and these translations before production use.
Responsible operator
Who is responsible?
- Proposed operator
- Locus Robotics Corporation
- Business address
- 100 Fordham Road Wilmington, MA 01887 United States
- Privacy contact
- privacy@locusrobotics.com
- Bot Calculator assignment
- Pending confirmation that this entity operates Bot Calculator
- Data-protection officer
- Pending appointment decision and contact, if applicable
Corporate details come from current public corporate materials; their use for this service still requires internal approval.
Information collected
What does Bot Calculator store?
Security data
Salted password hashes, hashed sessions and one-time tokens, expiry and use timestamps, rate-limit records, request-address hashes, and audit events.
Workspace data
Projects, sizing and commercial scenarios, immutable snapshots, installation allocations, ROI assumptions, PDF selections, and site-specific deal registrations.
Requests and messages
Transactional delivery metadata, historical privacy-request evidence, and minimized hashed deletion markers. Plaintext passwords and tokens are not stored.
Do not enter special-category data, customer order data, NDA text, or unnecessary personal information in free-text fields.
Purpose limitation
Why is information used?
Information is used to review access and NDA eligibility, operate reproducible planning projects, authenticate users, enforce owner and administrator boundaries, prevent misuse, send transactional messages, and manage privacy requests.
Legal bases require approval
Applicable legal bases and regional scope depend on the final service arrangement. An NDA does not replace privacy obligations. Purpose-specific legal bases require legal approval.
Access, recipients, and transfers
Who can access the data?
- Ordinary users can access only their authorized projects and records. Authorized administrators can review access and privacy requests and inspect cross-user project records under audited permissions.
- The local deployment uses project-scoped PostgreSQL and Mailpit services. Both are loopback-only.
- No advertising, analytics, profiling, social-media, or embedded-content provider receives application data in the observed build.
Service providers and international transfers
Isolated temporary executive demo on owner-controlled infrastructure.
Cookies and device storage
No advertising or analytics storage
Public pages set no cookies. After a successful sign-in, one first-party session cookie provides the authenticated workspace.
| Name/provider | Purpose | Lifetime and protection | Assessment |
|---|---|---|---|
botcalc_demo_sessionBot Calculator (first party) | Keeps an approved user signed in and binds CSRF protection to the server session. It is created only after successful sign-in. | Expires after at most 8 hours or earlier on sign-out or server invalidation. HttpOnly, SameSite=Lax, Path=/, no Domain, Priority=High, and Secure with HTTPS. | Technically necessary for the requested authenticated workspace; not used for analytics, advertising, profiling, or cross-site tracking. Final legal review remains required. |
No separate CSRF cookie
The CSRF value is derived from the server session.
No application browser databases
LocalStorage, SessionStorage, IndexedDB, Cache Storage, and service workers are unused.
No tracking
No analytics, advertising, profiling, pixels, or external telemetry are loaded.
Retention and deletion
How long is information kept?
- Sessions expire after at most 8 hours and are invalidated on logout, suspension, rejection, or password reset.
- Activation links expire after 24 hours; password-reset links expire after 30 minutes. Both are one-time use.
- Users can permanently delete eligible records directly with one clear confirmation. Account deletion also requires the current password. Only a specific active retention hold blocks the affected deletion.
- A deleted record can remain in the single retained recovery backup until replacement. A minimized reconciliation ledger must be applied after restoration so deleted records are not silently reintroduced.
Synthetic demo workspaces are removed after the configured inactivity window.
Individual rights
Privacy choices and requests
Depending on location and circumstances, people may have rights to access, correct, delete, restrict, object, receive a portable copy, appeal, or complain to a regulator. The application provides a JSON export and direct deletion; other requests can be sent to the privacy contact. privacy@locusrobotics.com.
Regional review
GDPR, UK GDPR, and US state rights depend on region, thresholds, role, and exemptions. The observed build does not sell personal information or use targeted advertising. Applicable procedures require legal review.
Security and deployment
How is information protected?
Controls include salted scrypt password hashing, hashed tokens, HttpOnly and SameSite cookies, exact-origin checks, server-derived CSRF tokens, rate limiting, role and owner authorization, redacted logs, audit trails, restrictive browser headers, and a non-root read-only container.
The current LAN URL uses HTTP and is not encrypted in transit. Global deployment requires HTTPS, exact origins, reviewed proxy settings, Secure cookies, protected SMTP, administrator hardening, and updated provider disclosures.