Terms of Service

Effective date: [EFFECTIVE DATE] · Version 1.0

Written in good faith and kept accurate to how Revere operates. This is not a substitute for independent legal advice, and [COMPANY LEGAL NAME] may update these terms as the service evolves.

1. Acceptance of terms

By accessing or using Revere ("the service") you agree to these terms on behalf of yourself and the organization ("tenant") you represent. If you do not agree, do not use the service.

2. The service

Revere is a multi-tenant web portal operated by [COMPANY LEGAL NAME] that provides organizations with tools to automate their data workflows. Each tenant is enabled for the tools it has arranged for, and the service is provided to that tenant's authorized operators under the tenant's own agreement with [COMPANY LEGAL NAME].

3. Accounts and access

Access is scoped to a tenant. Each operator is responsible for keeping their sign-in credentials and any multi-factor authentication secret confidential, and for all activity under their account. Notify us promptly if you believe an account has been compromised.

4. Acceptable use

You agree not to misuse the service — including attempting to access another tenant's data, probing or interfering with the service's security, uploading unlawful content, or using the service to violate any applicable law or third-party right.

5. Customer data and ownership

The tenant retains ownership of the data it uploads and the outputs the service generates from it. [COMPANY LEGAL NAME] processes that data solely to operate the service and produce the tenant's outputs. Our handling of personal data is described in the Privacy Policy.

6. Subscriptions and billing

Billing is handled off-app under a separate written agreement between the tenant and [COMPANY LEGAL NAME]. No payment is collected through the service itself.

7. Accuracy and disclaimers

The service is provided "as is" and "as available." Revere automates data processing, but the operator reviewing an output remains responsible for verifying its accuracy before relying on or submitting it. To the extent permitted by law, [COMPANY LEGAL NAME] disclaims all warranties not expressly stated here.

8. Limitation of liability

To the maximum extent permitted by applicable law, [COMPANY LEGAL NAME]'s aggregate liability arising out of or relating to the service is limited as set out in the tenant's written agreement, or, absent such a term, to [LIABILITY CAP — to be set with counsel]. Neither party is liable for indirect, incidental, or consequential damages.

9. Termination

Either party may terminate access in accordance with the tenant's written agreement. On termination, your right to use the service ends; data handling after termination follows the Privacy Policy and the tenant agreement.

10. Changes to the service and these terms

We may update the service and these terms as it evolves. Material changes take effect on the stated effective date; continued use after that date constitutes acceptance.

11. Governing law and contact

These terms are governed by the laws of [JURISDICTION / GOVERNING LAW]. Questions about these terms can be sent to [LEGAL CONTACT EMAIL], [COMPANY LEGAL NAME], [MAILING ADDRESS].

Privacy Policy

Effective date: [EFFECTIVE DATE] · Version 1.0

Written in good faith and kept accurate to how Revere operates. This is not a substitute for independent legal advice, and [COMPANY LEGAL NAME] may update this policy as the service evolves.

1. Data we collect

Account identity — the name and email address of each operator, and the authentication material needed to sign in (passwords are stored hashed, never in plain text; multi-factor secrets are stored to verify sign-in).
Tenant settings — the tenant's configured details, including any contact name, phone, and email an operator enters for a tool's use.
Uploaded data — the files and data a tenant uploads to the tools it uses, which, depending on the tool, may include business records such as customer names, addresses, product identifiers, shipment tracking numbers, and transaction amounts.
Generated outputs — the results the tools produce from that data, retained as job artifacts.
Operational logs — audit and review logs recording actions taken in the portal, used for security and troubleshooting.

2. How we use data

We use this data solely to operate the service for the tenant: to authenticate operators, run the tools a tenant uses on the data it provides (which, depending on the tool, may include steps such as resolving shipment dates from tracking numbers), send transactional email (such as invitations and security notices), and secure and troubleshoot the service. We do not sell personal data or use it for advertising.

3. Sub-processors

Revere relies on a small set of third-party services to operate. We share only the data each needs for its function:

Amazon Web Services (AWS) — cloud hosting and storage for the application and its data.
Postmark — delivery of transactional email (invitations, security and account notices).
UPS, FedEx, and R+L Carriers — used by tools that resolve shipment dates; when a record carries a tracking number, we query the matching carrier to resolve its date.
Google Fonts — the portal loads its typefaces from Google's font CDN, so your browser requests those font files from Google (see the Cookie Policy).

4. Cookies

Revere uses only strictly-necessary session cookies and a small set of UI-preference cookies; it sets no third-party tracking cookies. See the Cookie Policy for the full list.

5. Data retention

We retain account and tenant data for as long as the tenant's account is active, and job artifacts (uploads and generated outputs) for the period needed to operate the service and meet the tenant's obligations. Specific retention periods are set out in the tenant agreement [RETENTION PERIOD]. On account closure, data is handled per that agreement.

6. Security

Access is scoped per tenant so one tenant cannot reach another's data. Passwords are stored hashed, multi-factor authentication is supported, and traffic is served over TLS. No system is perfectly secure, but we work to protect data in transit and at rest.

7. Your rights

Depending on your jurisdiction (for example under GDPR or CCPA), you may have the right to access, correct, export, or request deletion of your personal data. To exercise these rights, contact [PRIVACY CONTACT EMAIL]; requests are handled manually today. Because most data in the service belongs to a tenant, we may direct a request to the relevant tenant as the data controller.

8. International transfers

The service is hosted in [HOSTING REGION]; using it may involve transferring data to that region. Where required, transfers are made under appropriate safeguards [TRANSFER MECHANISM].

9. Contact

Questions about this policy can be sent to [PRIVACY CONTACT EMAIL], [COMPANY LEGAL NAME], [MAILING ADDRESS].

Cookie Policy

Effective date: [EFFECTIVE DATE] · Version 1.0

Revere uses a small number of cookies and browser-storage entries to keep you signed in and to remember your interface preferences. It sets no third-party tracking cookies.

Strictly necessary cookies

These keep the portal working and cannot be disabled:

A session cookie that keeps you signed in.
A security cookie that protects form submissions against cross-site request forgery.

Preference cookies and storage

These remember how you like the interface and are not used to track you:

rv_theme — your light / dark theme choice.
Browser localStorage — small UI state such as the rail-pinned state and table column widths. Clearing your browser storage resets these.

No tracking cookies

Revere does not set third-party tracking cookies and does not run web analytics that profile users.

Third-party font requests

The portal loads its typefaces from Google Fonts, so your browser requests those font files from Google's CDN. This does not set a Revere cookie, but the request is handled by Google under its own terms. See the Privacy Policy for the full list of sub-processors.