In plain words
MAYA reads your bookings (nights, room type, nightly rate, when the booking was made), your room types and how many rooms each has, your rate plans, and your property's name, time zone and currency. It writes one nightly price per room type to one rate plan. On ThinkReservations it also gives each other standard rate type you tick, such as a wedding or group rate, the same change on its own rate. On Cloudbeds, MAYA also asks Cloudbeds to let it know if the app is uninstalled. On Mews it does not copy your rate plans or property details, and it writes nothing. It never stores guest names, emails, phone numbers, addresses or card details.
This page is the full list, for anyone who needs to answer "what exactly does MAYA touch?" before connecting, or who wants to check afterwards. Where the three systems differ, the tabs say how. The short version: MAYA reads the shape of your bookings and your rates, and it writes nightly prices. Everything else in your system is yours alone.
What MAYA reads
About every five minutes: bookings made or changed since the last read, with every room in the booking and each room's own nightly rate, and your room types with the number of units in each.
About once an hour: your rate plans, with each room type's own nightly rate for the next 396 nights from its base rate plan.
Once a day: the whole again, and your taxes and fees (Cloudbeds requires the request, but MAYA keeps none of it and uses none of it).
Once, at connect: the property's name and which properties your login covers. The time zone and currency are read at connect and checked again once a day: MAYA follows a new time zone, and a new currency only while you are in simulation.
Arrives but is never used or kept: availability and restrictions (minimum stays, closed to arrival or departure), which come with your room types and nightly rates, and guest names, which come with bookings.
Kept only as a scrambled key: which allotment block (or group profile) a booking belongs to, so the group counts as one booking for . Never the code itself.
Never asked for: the room blocks or allotments themselves, or other guest details. Read the Cloudbeds page.
About every five minutes: bookings made or changed since the last read, with each room and its room charges, your room types by name, and your list of rooms, which MAYA counts room type by room type. A room marked as inactive, as not a room, or as not included in occupancy is left out. With the list of rooms comes each room's Room Group, which MAYA shows your room types under. Read Room groups.
About once an hour: your rate types (name, standard or derived, which room types each covers) and your own nightly rates for the next 396 nights from the rate type MAYA sends to, and from each other standard rate type it moves.
Once a day: the whole again.
Once, at connect: the property's name, time zone and currency, and which hotels your login covers.
Kept only as a scrambled key: which group or group block a booking belongs to, so the group counts as one booking for . Never the id or the group's name.
Never asked for: availability (MAYA asks for the permission but makes no such call), restrictions, or guest details. Guest details still arrive with each booking, and MAYA drops them before anything is stored. Read the ThinkReservations page.
About every five minutes: bookings made or changed since the last read, with their room category, arrival, departure and total price, your room categories by name, and your spaces with the category each is in, to count each category's rooms. Of the spaces, MAYA keeps only those counts.
Once a day: the whole window again.
Once, at connect: your property's details, only to check the keys work. MAYA keeps none of them. We set the property's name, time zone and currency with you.
Never asked for: your rate plans, availability, restrictions or guest details. Guest fields that come with a booking are dropped before anything is stored. Read the Mews page.
What MAYA writes
Once you go live: one nightly price per room type, to that room type's base rate plan, for tonight and the next 395 nights, whenever a price changes. MAYA also keeps one notification subscription with Cloudbeds so Cloudbeds can tell it if the app is uninstalled. That is all.
Once you go live: one nightly price per room type, to the rate type MAYA reads and writes (Best Available, or the one you picked), for tonight and the next 395 nights, whenever a price changes. And to each of your other standard rate types you tick on the PMS tab: the same change on its own rate, whenever that changes. All start ticked when you set up; one first found once you are live waits for your tick. That is all. Read Your other standard rates.
Nothing. MAYA does not send prices to Mews yet, including prices you type.
Until you go live, no price is written. Every property starts in simulation. Read going live.
MAYA never creates, changes or cancels a booking. So when a rule raises or cuts a night's price, guests who have already booked keep the rate they booked at. The new price is for bookings made after it reaches your system. MAYA never changes availability, so it cannot cause an overbooking. It never changes restrictions, minimum stays, close-outs, taxes, room types, rate plans or property settings. It never sends a price of 0. Read how prices reach your property system.
Read-only access
Simulation is the read-only way to use MAYA. Every property starts in it and stays in it until a General Manager or Hotel Admin goes live. In simulation MAYA reads your system and runs your rules. The results show on the calendar and in the change log, and no price is sent. On Cloudbeds, the only thing written is the notification subscription, set up when you connect. Read simulation mode.
MAYA has no read-only connection. When you connect Cloudbeds from inside MAYA, or connect ThinkReservations, the permissions it asks for include changing rates, because it needs that once you are live.
If your system lets MAYA read but not change rates, everything else carries on as normal: reads, rules, the calendar and the change log. Once you are live, each price your system refuses is held, and the change log shows a "Prices not reaching" item such as "Cloudbeds won't let MAYA change Standard rates because MAYA doesn't have permission to update rates". To stop sending, go back to simulation instead. Read pausing, or going back to simulation.
What a stored booking looks like
For each room in a booking, MAYA keeps one line per night: the night, the room type, the date the booking was made and its time to the minute, the days between the date and the night, and that room's nightly rate. When 3 or more bookings for the same room type and dates were made together, their lines also keep a key that says they belong together, worked out from the dates, the room type and the times, and nothing about the guest, and when MAYA put them together. It also keeps a short record of the booking's shape: its reference in your system, its status, its dates, how many adults and children, and the channel it came from. Where your system sends them, the record also holds the room the booking was given and the rate plan it was booked on. On ThinkReservations it also keeps the booking's subtotal, tax and total amounts. No price is worked out from these amounts. Bookings read by the history import keep no record at all beyond the line per night.
What one line stands for depends on your system. In Cloudbeds and ThinkReservations it is one room of a booking. In Mews it is one booking, which is always one room. For occupancy every line counts. For a booking counts once however many rooms it holds. Read booking speed.
Guest data
MAYA never stores guest names, emails, phone numbers, addresses, notes, dietary or special requests, payment details, loyalty numbers or a booking channel's own confirmation number. Where your system lets MAYA choose, it does not ask for them: MAYA never asks Cloudbeds for guest details, and never asks ThinkReservations for customer records. Where they arrive anyway (a guest name on a Cloudbeds booking, a customer block on a ThinkReservations booking, a Mews booking's guest fields), MAYA keeps only the fields on a short list and drops the rest before anything is stored. A new field your system adds is dropped by default.
The same promise is in the Privacy Policy and the Terms. Read privacy, security and your data.
Rate plans and packages
MAYA reads your rate plans for two reasons: to find the one plan per room type it writes its prices to, and to read your own nightly rates from that plan about once an hour. On ThinkReservations, once you are live, it also reads the own rates of each other standard rate type it moves. Your own rate is what a rule starts from on a night MAYA has not sent to yet. Read What a rule starts from.
On Cloudbeds MAYA writes to one plan per room type and never to any other. On ThinkReservations it writes its prices to one rate type per room type, and gives the other standard rate types you tick the same change on their own rate.
- Cloudbeds: the room type's base rate, the plan that does not follow another plan and has no public name. Derived plans (a non-refundable rate at 10% off, say) follow the base by Cloudbeds' own rules, so they move when MAYA moves the base. Packages, promotions and long-stay plans are never written to. Read which rate plan MAYA changes in Cloudbeds.
- ThinkReservations: the rate type you pick on the PMS tab, or, left on Automatic, your Best Available rate type, the active standard rate type with "Best Available" in its name. One named exactly "Best Available" or "Best Available Rate" comes first. If no active rate type has that name, MAYA uses the one active standard rate type that covers the most room types. A rate type marked inactive is never used. Derived rate types reprice themselves from it. Every other active standard rate type with rates of its own, a non-refundable or package one included, gets the same change on its own rate when ticked on the PMS tab: all start ticked when you set up, and one first found once you are live is held out until you tick it. Read which rate type MAYA sends to in ThinkReservations and Your other standard rates.
- Mews: none.
On Cloudbeds there is no setting to choose a different plan, in MAYA or with us. It follows from how your plans are built. MAYA writes to the base rate, so a plan you want to move with MAYA's prices should follow the base rate.
On ThinkReservations, a General Manager or Hotel Admin can pick the rate type from the Rate type list on the PMS tab, and the tab says "MAYA reads and writes:" with the one in use. Left on Automatic, it follows from the name, so you can also choose by giving "Best Available" to the standard rate type you want (and to no other). MAYA reads your rate types about once an hour, so a renamed rate type is picked up within about an hour. Read Seeing and picking the rate type.
MAYA never creates a rate plan or a rate type. Set up any new rate structure in your system first. If a room type has no plan MAYA can write to, MAYA has no rate of yours to start from, so it is not priced or sent. On ThinkReservations the change log says so, in simulation too. Read when your property system does not accept a price.
Example: A price moving through The Harbour Inn's rate plans
The Harbour Inn's Standard room in Cloudbeds has "Standard Rate" (the base), "Non-refundable" (follows Standard Rate at 10% off) and "Bed and Breakfast" (a package). MAYA writes $165 to Standard Rate for Fri, Nov 13 2026. Cloudbeds moves Non-refundable to $148.50 on its own. Bed and Breakfast stays where it was. Your booking engine and channels read Standard Rate as they always have.
Taxes and fees
On Cloudbeds, MAYA asks for your taxes and fees once a day, because Cloudbeds requires it of pricing tools like MAYA. MAYA keeps none of it and uses none of it. No price is worked out from your taxes, and nothing about tax is sent. If your property has not given MAYA permission to read them, Cloudbeds turns the request down and MAYA carries on as normal.
On ThinkReservations and Mews, MAYA does not read your tax settings at all. A ThinkReservations booking does arrive with its own tax amount. MAYA keeps it with the booking and works out no price from it. Read what a stored booking looks like.
With or without tax
MAYA reads and writes the same rate field in your system, so prices come out on whatever basis your base rate is on. If your base rate in Cloudbeds is entered with tax included, MAYA's prices are with tax included. If it is entered without, so are MAYA's. The same holds for ThinkReservations. MAYA does not add or remove tax, and it shows you the number it works with.
When property details are read
MAYA reads your property's name at connect and does not read it again; you can change it yourself in the questions step. The time zone and currency cannot be changed inside MAYA, and how they stay right depends on your system. On Cloudbeds MAYA checks both once a day: it follows a new time zone, and a new currency while you are in simulation. Once you are live it keeps the currency it has, and our team is alerted. On ThinkReservations MAYA reads both once, at connect: if you change either there, email us and we change it in MAYA. On Mews MAYA copies none of the three, and we set them with you when we connect. The time zone matters more than it looks: the calendar, the 396-night window, the and every "past week" count run on it. Read time, weekends, currency and holidays.
How many rooms each room type has
Cloudbeds reports the number of rooms in each room type, and MAYA re-reads it on every cycle, so a wing you open shows up on the next read. On ThinkReservations, MAYA counts the rooms in each room type from your list of rooms on every cycle, and keeps the counts it has if the list cannot be read. On Mews, MAYA counts the rooms in each room category from your spaces on every cycle, leaving out spaces switched off in Mews, and keeps the counts it has if the spaces cannot be read. Only if Mews lists no spaces at all does every Mews room category take one number, which we set with you when we connect (100 until then). The count is what divides by and what your bill is based on. Read room types and rooms out of service and your room count and what you pay.