Energy Asset Data Security Policy & Terms of Service

1. Account and firm isolation

Supabase manages email/password authentication. Session tokens are held in HTTP-only cookies. Voyage, interruption and adjustment records are stored in the configured Supabase database. Tenant membership comes from the database, not editable company text. Row-level security and tenant foreign keys restrict records to the appropriate firm. Database administrators retain privileged access; row-level security is access control, not encryption or an absolute guarantee against disclosure.

Roles are operator, coordinator and director. All three can operate their firm's manual voyage clocks in Phase 1. Role assignment and verified notification destinations are administrator-managed; users cannot assign themselves another firm's membership.

2. Information we use

Registration uses your name, corporate email, company, trading hub and account credentials. Manual voyage registration stores vessel identity, destination and coordinates, target profit, allowed laytime, daily demurrage rate and NOR timestamp. Target profit is commercially sensitive financial information. Interruption reasons, actor identities, timestamps and adjustment snapshots are retained in the ledger.

Physical purchase prices, end-buyer identities and cargo volumes are not required by Manual Sentry. Do not include unnecessary counterparty information or credentials in notes. The application does not provide a cross-firm market-data product.

Demurrage Recap Review analyses pasted, redacted negotiation text in your browser using configured matching rules. Explicitly saving a draft stores its source text, selected line references, operator review notes, house-standard snapshot and revision history in your firm’s private database records. A draft export contains reviewed terms, unresolved points and cited source excerpts; review it before sharing. The tool does not authenticate a transcript, establish counterparty acceptance or send contractual notices.

3. Provider boundaries

When enabled, Cloudflare Turnstile processes browser and network signals on registration, login and email recovery forms to prevent automated abuse. Supabase validates the resulting security token. Deal and voyage records are not sent to Turnstile. See the Cloudflare privacy policy.

Supabase processes authentication and stored ledger data in the configured project, whose supplied region is eu-west-2. Review the Supabase privacy policy. Passwords are managed by Supabase authentication, not stored in voyage tables.

Manual Sentry does not call AIS or weather feeds. Automated enrichment and document extraction are unavailable behind the premium roadmap notice. Existing integration and CSV code is preserved for future work.

When a deployment administrator enables a verified Telegram destination, an adjustment can transmit vessel name, terminal, consumed hours, demurrage, remaining target margin, hourly rate and event time to Telegram and that chat's members. Approve the destination and review chat membership before enabling delivery. Missing configuration is shown explicitly. A timed-out delivery may have reached Telegram; uncertain sends are not automatically repeated. Threshold monitoring runs independently of the browser. Enabled, verified email, Telegram, WhatsApp and SMS destinations can receive financial alarm snapshots through configured providers. Preferences, consent, threshold snapshots and delivery status are retained. Provider acceptance does not prove receipt by a person. External delivery requires an operating worker and provider credentials. Configured morning summaries are scheduled for 06:00 in each destination port’s local time zone and group voyages by destination time zone. They are separate from threshold and daily alarm milestones.

4. Persistence and retention

Reloading or closing the browser does not erase saved voyages, interruptions or event snapshots. Completing a voyage freezes its calculation and retains its ledger; it does not delete or archive it. This phase has no self-service permanent erasure workflow.

Retention periods, backup deletion procedures, operational request contacts and applicable dispute-related retention must be agreed before production use. Copies received by notification providers or exported by users require separate handling.

5. Manual calculation basis

NOR is the starting timestamp under the explicitly confirmed Phase 1 accounting basis. Every logged interruption is deducted, including interruptions after the laytime allowance has expired. The operator must confirm that this treatment matches the agreed contract. Pause, resume and completion use database-recorded timestamps. Contract parameters are locked after registration in this interface.

Displayed demurrage equals excess net hours multiplied by the daily rate divided by 24. Remaining margin equals entered target profit minus calculated demurrage; it excludes other costs. These values are a ledger calculation, not a settled invoice, verified claim, guaranteed return or instruction to trade. No automated contractual interpretation or forecast is provided by Manual Sentry.

Only enter information you are authorized to process. Review calculations and accounting exclusions with the responsible operational and contractual personnel. Final commercial terms, contracting entity, governing law and service commitments remain to be agreed.

6. Contact and launch requirements

The operator's legal name, registered address and verified privacy/security contacts have not yet been supplied. marginsentry.net is the official domain for the hosted MarginSentry website. Operator details and a process for access, correction and deletion requests must be established before commercial onboarding.

The intake acknowledgement confirms the manual accounting basis and that you have read this notice. It is not permission for unrelated marketing. Material changes to data handling should be disclosed before activation.