RecordAware Privacy Notice — Current Consumer Beta

Version: 2026-09-27.consumer-beta-v2

Effective: September 27, 2026

1. Scope

This Privacy Notice describes how RecordAware LLC handles information in RecordAware's limited consumer beta, currently available to eligible customers whose home state is Texas, Florida, or California, subject to supported route and destination coverage.

2. Information you provide

Depending on the features you use, RecordAware may process a preferred name, email address, account-security information, trip and itinerary facts, conviction or record-status facts relevant to the requested research, supervision or registration facts, selected transportation, lodging and activity information, and information you submit for support or correction.

3. Data-minimization rule

The standard Trip Check is designed not to require a Social Security number, victim identity, registry identifier, complete criminal case file, police report, passport image, or other identity-heavy material when narrower facts are sufficient. Do not enter unnecessary sensitive identifiers or narrative information into free-text fields.

4. Information generated by the service

RecordAware may generate and process report identifiers, research results, source references and verification dates, action and verification status, account/session activity, security events, order identifiers, payment status, entitlement status, and technical records needed to operate and protect the service.

5. Browser storage

RecordAware uses browser storage to support functions such as saving or restoring trip state, preserving route context, reconciling a pending checkout, and recognizing a paid order. Information stored in your browser may remain there until RecordAware clears it through a product action, you use a Start Fresh/reset function where applicable, or you clear browser data yourself.

6. How we use information

We use information to create and personalize Trip Checks, determine which research layers are relevant, save or resume supported workflows, process and reconcile purchases, provide purchased access, protect accounts and sessions, operate security controls, provide support and corrections, maintain source and acceptance records, troubleshoot the service, and comply with applicable legal and accounting obligations.

7. Payments

Payment-card details are processed by the payment processor. RecordAware stores or receives the order, amount, payment status, processor identifiers, refund status, and related transaction information needed to fulfill and administer the purchase. RecordAware does not need to store your full payment-card number or card security code in its Trip Check database.

8. Service providers

RecordAware uses service providers for functions such as hosting, database and authentication infrastructure, payment processing, security, and other technical operations. Providers receive information only as needed for the service they perform and are subject to their own security and privacy obligations.

9. Generative AI

The current consumer beta does not send customer criminal-history or Trip Check profile information to a generative-AI provider for generation or model training. If RecordAware later introduces a materially different AI data flow, the applicable notice and product controls must be updated before that use.

10. Analytics and logs

RecordAware may use technical logs and limited product-usage information to secure, diagnose, and improve the service. The product is designed to avoid intentionally sending offense/profile free text or unnecessary sensitive trip details into ordinary analytics.

11. Sale and targeted advertising

RecordAware does not sell consumer beta Trip Check profile data or use it for targeted advertising.

12. Retention

RecordAware retains information for as long as reasonably necessary for the purpose for which it is used. Different records may have different lifecycles. Account and security records, transaction/accounting records, legal-acceptance records, fraud or abuse records, and records needed to resolve disputes or comply with law may be retained longer than ordinary trip-working data. Browser-stored information follows the browser-storage behavior described above.

13. Access, correction and deletion requests

You may ask RecordAware to review, correct, or delete information associated with your account or Trip Check through the support or contact method made available in the service. Some information may need to be retained when reasonably necessary for security, transaction records, legal compliance, dispute resolution, or an auditable record of a purchase and policy acceptance.

14. Security

RecordAware uses account authentication, session controls, access restrictions, and other technical and operational safeguards designed to protect information. No online service can guarantee absolute security, so customers should also protect their account credentials and devices.

15. Children

The consumer beta is intended for adult users. RecordAware does not intend to create accounts for children. When a minor-related fact is genuinely relevant to a travel rule, the product is designed to request only the minimum adult-provided age-band or relationship information needed for that analysis.

16. Changes

Material changes to this Notice will receive a new version. Paid checkout may record the version presented and acknowledged by the customer.

17. Contact

Privacy, correction, and deletion requests may be submitted through the support or contact method made available in the RecordAware service.