This policy was prepared for AVMDEVS LLC, the company that runs Trendetna, and it describes what the site actually does today; a lawyer should review it before it is relied on.
Who we are
Trendetna is operated by AVMDEVS LLC, in Sherman Oaks, California, United States. We do not publish a street address. Write to hello@trendetna.com and a person will answer.
We are the company you buy through. The experiences themselves are run by independent operators, which is why some of your details are passed to an operator when you book. That is set out below.
What we collect, and why
Your account. Your email address, the name you choose to display, and, if you add them, a phone number and a profile picture. Your password is stored only as a bcrypt hash, so nobody here can read it. If you sign in with Google instead, we receive your Google account id, email address, name and profile picture from Google, and you never set a password with us.
A public handle. We generate one when you sign up, from your display name or the first part of your email address, so other people can mention you in the community feed. It is visible to anyone who can see your posts.
Sign-ins. Each time you sign in we record the session: a hashed token, a shortened description of the browser or device, the IP address it came from, and when it started, was last used and expires. This is what your account page lists under your sign-ins, and what signing out everywhere ends. Nobody but you sees it.
Bookings. What you booked and with which operator, the ticket type, how many people, the start time, the name, email address and phone number given for the booking, any notes you wrote, and the practical answers a product asks for, such as a pickup address, a drop-off point or a flight number. Alongside that we keep the money trail: the amount, the currency, the exchange rate and any fee or discount applied, and the payment reference from Stripe. We never receive or store your card number.
Trips you plan. The destination, dates, party size, pace, interests and notes on any itinerary you save.
Saved experiences. The listings you bookmark.
What you post. Posts, replies, photographs you upload, votes, reports you make about other posts, and who you have blocked.
What you ask Etna. Our assistant stores the question as you typed it and the answer it gave, with the city you were looking at.
AI usage records. One row per call to the assistant, holding your account id or IP address, the model, the number of tokens and the estimated cost. It exists to cap spending and to stop abuse.
Searches, counted but not attributed. We keep a count of how often each search phrase is used across the whole site, with no account id attached and no timestamp finer than an hour. There is no per-person search history on our side; your own recent searches stay in your browser.
What we do not do
There is no advertising on this site and no analytics or tracking scripts. We do not sell personal data and we do not share it with anyone for advertising. We do not ask for your location and nothing here reads it from your device.
Cookies, and what your browser keeps
Trendetna sets no cookies of its own.
Your sign-in is kept in your browser's local storage instead, under a key tied to the account signed in, and signing in as somebody else removes the previous account's keys from that device. Your chosen display currency and your recent searches are kept the same way. The details you fill in on a booking form sit in session storage while you finish checking out and disappear when the tab closes. Clearing your browser's site data removes all of it and signs you out of that browser.
Parts of some pages are loaded from other companies. Those companies see your IP address and may use their own cookies or storage:
- Stripe, on the payment step. Stripe's payment form runs in your browser and sets its own identifiers, largely to detect fraud.
- OpenStreetMap, which serves map tiles, and unpkg.com, which serves the mapping library, on any page showing a map.
Who your information is sent to
We use a small number of services, and each gets only what it needs.
Stripe takes the payment. Your card details go from your browser to Stripe directly and never reach our server. We send Stripe the amount, the currency, a description of the booking, your email address so it can issue its own receipt, and reference numbers for the listing, the reservation and your account. What comes back to us is a payment reference, whether it succeeded, and the brand and last four digits of the card, which appear on your confirmation email.
Bokun is the reservation platform the operators use, and it is how a held place, a confirmation and a cancellation reach them. When you hold a place we send the ticket, the time, the number of guests and the practical notes, such as a pickup address or a flight number, because the operator needs those to arrange the day. Your name, email address and phone number are sent only after your payment has arrived, when the booking is confirmed with the operator.
Brevo sends your booking confirmation. It receives your email address, your name and the contents of that receipt. A blind copy of booking emails goes to our own mailbox, so somebody here can act on a booking without waiting to be told about it.
OpenAI is behind Etna, our assistant, and the trip planner. What is sent is the text you type, capped in length, the city you are looking at, and a shortlist of listings from our own catalogue. Your question is also checked by OpenAI's moderation service before the model sees it. Your name, email address, booking history and payment details are never part of any of that.
Google, only if you choose to sign in with Google. Google tells us your account id, email address, name and profile picture. We send Google nothing else about you.
TripAdvisor ratings appear on some listings. We read those from TripAdvisor; nothing about you is sent to them.
If we are ever legally required to hand something over, or need to in order to deal with fraud or a threat to somebody's safety, we will.
The AI assistant
Etna can only recommend listings that exist in our catalogue: it is given a shortlist of real ones and told to answer from those alone, and it cannot link you off this site. It is still a language model, so it can be wrong or out of date. It is never given your account details, and we do not use anything you say to it to train a model. The question and the answer are stored here, and lose their link to your account if you delete it.
How long we keep things
Sign-in records expire after thirty days and are deleted thirty days after that, which is what lets a token presented too late be recognised as a replay rather than as a stranger.
Booking records are kept indefinitely. They are the record of money taken and of a place reserved with an operator, and both have to stay answerable; nothing deletes them automatically.
Posts stay until you delete them or a moderator removes them. A removed post is off the site, but the row is kept so reports about it can still be resolved.
Everything else lives as long as your account does.
Seeing, correcting and deleting your data
Most of it you can read on the site while you are signed in: your profile, your bookings, your saved experiences, your trips, and your sign-ins, each of which you can end.
To delete your account, open your account page and choose to delete it. You confirm with your password, or, if you have only ever signed in with Google, by typing your email address. Deleting removes the account and, with it, your saved experiences, your posts and replies, your votes, your trips, your blocks, your reports and every sign-in. Two things deliberately survive: booking records, including the name, email address and phone number given for that booking, because they are the record of money that moved and a place reserved with an operator; and anything you wrote to Etna, which stays with the link to your account removed. There is no undo.
For a copy of everything we hold about you, or to correct something you cannot edit yourself, write to hello@trendetna.com.
Keeping it safe
Passwords are hashed with bcrypt. Sign-in tokens are stored only as hashes, and if one is ever presented twice we end that whole session rather than let a copied token keep working. Changing your password signs out every other device. The site is served over HTTPS.
Children
Trendetna is not meant for children and we do not knowingly collect anything about them. If you believe a child has given us their details, write to us and we will remove them.
Changes
When this policy changes, the new version appears here and the date at the top of the page changes with it.
Contact
hello@trendetna.com, or AVMDEVS LLC, Sherman Oaks, California, United States.