BRIJ Digital Inc., a Delaware corporation (“BRIJ”, “we”), operates travel.brij.fi, app.brij.fi and the Buy with BRIJ browser extension, and is the data controller for the personal data described here. Contact: [email protected].
2. What we collect
Passenger details, provided at booking time: given and family name, date of birth, title, gender, email address, and phone number — and, when the airline or booking site requires it, nationality and the travel document's number and expiry date. We ask for identity data only because carriers require it to issue a ticket; travel-document data is stored encrypted.
Purchase details, when you buy a product or a train ticket: the recipient's or traveller's name, the shipping address, phone number and email address, the product link and the options you chose.
Saved travellers, if you choose to save them: the same seven fields above, stored against your wallet address so you do not retype them on every booking. Entries are created only when you explicitly ask us to remember someone — we never populate this list from your past bookings — and you can remove any entry at any time from the Travellers screen. Removing an entry deletes it from your saved list; it does not alter or erase bookings already made, which we must retain (see retention below).
Wallet addresses: the funding and refund wallet addresses attached to a booking intent, and the payer addresses of x402 payments.
Booking records: offers, intents, orders, escrow state, refund requests, and the customer support code.
The Buy with BRIJ browser extension: the extension checks the pages you visit, locally on your device, only to decide whether they are a product page; nothing is sent to us. When you click Buy with BRIJ, we receive the address of that product page, the page's content as your browser displays it (with all scripts removed and any text you typed cleared), the price it displays, and the options you selected or wrote. The extension never reads your browsing history, cookies, passwords or payment details.
Supplier messages: the confirmation emails and verification codes the airline, booking site or store sends about your order, received at an address we assign to that order.
Technical logs: IP addresses, request identifiers, timestamps, and request paths, kept for security and debugging.
3. What we use it for
Fulfilling orders: passenger and purchase details are transmitted to the provider that sells what you bought — our flight infrastructure provider, the airline, the booking site or the store — which is necessary to issue the ticket or ship the product and is the sole reason the data is collected. For some sellers we place the order on their website on your behalf, through an automated browser.
Pricing and buying a product you chose with the browser extension, and building the automation that buys from that store. The page content the extension sends is kept for 7 days.
Transactional email: booking-in-progress, booking-confirmed, and refund-request confirmations sent to the passenger email address.
Support and refunds: verifying refund requests against the support code and passenger name on file.
Wallet sign-in: proving control of your wallet by signing a message (no transaction, no fee) grants access to your own bookings and saved travellers. We issue a session token that expires after 7 days; there are no passwords and no accounts.
Security, fraud prevention, and compliance with legal obligations.
We do not sell personal data, and we do not use it for advertising.
4. Who we share it with
Sellers: our flight infrastructure provider, airlines, booking sites, rail operators and stores receive the passenger or purchase details their order requires.
Service providers that run the order for us: the cloud browser and computing providers on which the automated purchase runs, and the AI model provider that checks the payment page before a purchase is paid. They process the data only to perform the order.
Email delivery provider: passenger email address and booking summary, to send transactional messages.
Encrypted off-site backups: booking records are included in routine database backups stored with a cloud storage provider.
Authorities: where required by applicable law.
5. The blockchain is public
Payments are settled on the Solana network. Wallet addresses, payment amounts, escrow accounts, and transaction history are public and permanent by design, visible to anyone, and cannot be altered or deleted by BRIJ. Do not use a wallet you are not willing to associate publicly with these transactions. No passenger, recipient or address data is written on-chain.
6. Retention
Booking and payment records are retained for as long as needed to service the booking (including refunds and disputes) and to meet legal, tax, and accounting obligations. Technical logs are retained for a shorter operational period. Backups roll over on a fixed retention schedule.
7. Security
Data is encrypted in transit, stored on access-restricted infrastructure, and access to a booking is gated by capability tokens (the intent id and the customer support code) rather than accounts. Keep those tokens secret; anyone holding them can read the booking.
8. Your rights
Depending on where you live, you may have rights to access, correct, delete, or receive a copy of your personal data, and to object to or restrict certain processing. Write to [email protected] and we will respond within a reasonable period. Note that we cannot modify on-chain data (see section 5) and may need to retain booking records where the law requires it.
9. Children
The Service is not directed at children. Passenger records for minors may only be submitted by an adult making a booking on their behalf.
10. Changes
We may update this policy; the current version is always published at this address with its last-updated date.