Platform · Security
Each business's data is kept separate in the database with row-level security. Documents are stored privately, and a download needs a signed-in user.
Aditi
Emergency handoff
Platform
Guest and traveller records should never sit in one open table
Travel and hotel records hold names, phone numbers, bookings and trip documents. A careless query in a shared system could show one business another business's guests.
- 01A query written for one business should never return another business's guests.
- 02Tickets and vouchers should not be open web links anyone can share.
- 03An emergency message should never wait in a queue.
How it works
Separation, private files, sign-in and people for emergencies
- 01
Each business is separate
Row-level security in the database limits every query to the business that signed in.
- 02
Documents stay private
Trip documents and vouchers are stored privately. A download needs a signed-in user.
- 03
Two-step sign-in
Turn on two-step verification with an authenticator app for each account.
- 04
Emergencies reach a person
Medical, accident, police and fire messages are handed to a person at once.
On WhatsApp
A stranger gets public answers, not trip details
A number that is not linked to a trip gets public answers only. Aditi does not share an itinerary with a number that is not on it.
- Trip details go only to numbers linked to the trip.
- Other numbers get public answers, with a daily cap.
- Aditi offers to pass the message to the team.
Aditi
Number not linked to a trip
In the portal
Documents are stored privately and downloaded by signed-in staff
Tickets and vouchers are kept in private storage. Staff open them from the portal after signing in, and they are not public links.
- Documents are kept in private storage.
- A download needs a signed-in user.
- A document can be resent to a traveller on request.
Documents · Goa beach week
Flight tickets, outbound.pdf
4 travellers · added 12 Nov
TicketAditi can sendHotel vouchers, Calangute.pdf
Whole trip · added 12 Nov
VoucherAditi can sendAirport transfer, Dabolim.pdf
4 travellers · added 13 Nov
VoucherAditi can sendSunset cruise confirmation.pdf
Day 3 · added 14 Nov
ConfirmationAditi can send
Files are stored privately. Downloads need a signed-in session.
Why teams use it
Protection built into the data path
Data kept apart per business
Row-level security keeps each business's guests, trips and stays in its own rows.
Private document storage
Tickets and vouchers are not public links. A download needs sign-in.
Two-step sign-in
An authenticator app adds a code as a second step at sign-in.
Sensitive details kept out of logs
Passwords, tokens and payment details are kept out of application logs.
Emergencies first
Emergency messages skip the queue and reach a person, with a fixed reply from Aditi.
Roles limit what each person sees
Each person sees the parts of the portal their role allows.
Use cases
Who relies on the separation
Agency with several trips
Keeps each agency's travellers apart on one platform, so one business never sees another's trips.
Straight answers
What this page does not claim
- This page lists no certifications, audit reports or compliance badges. Ask us for the documents you need for your review.
- Aditi shares trip and stay details only with a linked number. Other numbers get public answers, with a daily cap.
- Aditi cannot stop a person from sharing a document they have already downloaded.
- An emergency handoff means a person is alerted. It does not mean a person is on site.
Questions about security
Can another business see my guests?
No. Row-level security limits every query to the business that signed in.
Where are documents stored?
In private storage. A download needs a signed-in user, so a file has no public link.
What is two-step verification?
A second step at sign-in: a code from an authenticator app, after your password.
Are sensitive details kept in logs?
No. Passwords, tokens and payment details are kept out of application logs.
What happens when a guest sends an emergency message?
Aditi hands the chat to a person straight away and sends a fixed reply. Your team sees it in the inbox.