1. Who this policy is for

Two groups interact with the Services, and this policy covers both:

• Storage operators who use AnyBay to run their storefront, move-in, and abandoned-session tools, including the follow-up email sent in their location's name.
• Renters who visit an operator's storefront to view units, get a price, and complete a move-in online.

For renter data processed through a storefront, the storage operator is the business that decides why the data is collected, and AnyBay processes that data on the operator's behalf. If you are a renter with a question about your data, please contact the operator you rented from first. We will support them in responding to your request.

2. Information we collect

Information you provide directly

• Contact and demo requests. When you book a demo or request an integration, we collect your name, email address, company or facility name, and any details you include in the message.
• Inbound lead forms.When a renter fills in a lead form on an operator's published website, we collect the name, email address, phone number if the form asked for one, any message they left, and which page they were on. If the form asked whether they agree to be texted by the operator, we store that answer, the wording it was given against, and the time it was given. Where the operator has turned on lead forwarding, those travel to most destinations they choose, and to a HubSpot form only when the operator has named the field that holds them. See Section 4. Unless the operator has turned it off, we send the renter one email in the location's name saying their message arrived. It carries no offers, and a reply to it goes to the operator.
• Account information. When an operator sets up an account, we collect account and contact details and the settings needed to run the storefront.
• Move-in information. When a renter completes a move-in, we collect the details needed to create the rental, such as name, contact information, the unit selected, and move-in date.

Information collected automatically

• Usage and device data. We collect standard log and device information such as IP address, browser type, pages viewed, referring pages, and timestamps.
• Funnel and analytics data.To identify abandoned move-ins and produce funnel analytics, we record which steps of the move-in a renter reached and where they stopped. Where a renter entered their name, email address, or phone number before stopping, we keep those with the record so the operator can see who stopped and follow up, and the email address is what a follow-up email is sent to. Where the renter gave no name there but the same email address or phone number is on a reservation or an enquiry they made with that operator, we show the name from it beside the record. We never show a name from another operator's records. When a renter arrives from a paid ad, we may also hold the click identifier the ad network placed on the landing URL (such as a Google Ads click id), so a completed move-in can be credited to the click that brought the renter. We keep that identifier for up to 90 days, matching Google's conversion window: the cookie expires after that period, and a daily job removes the stored copy from funnel records while leaving campaign tags in place. See Section 3.
• Cookies and similar technologies. We use cookies and similar technologies to keep the site working, remember choices, and measure performance. See Section 6.

Information from an operator's storage software

With the operator's authorization, AnyBay connects to the storage management software the operator already runs. We read inventory, unit types, and pricing to display availability, and we write completed rentals back to that software. The operator's software remains the system of record for units, renters, and rentals.

The sign-in an operator gives us

To make that connection, an operator creates a user account for AnyBay inside their own storage software and gives us its user name and password. We hold those encrypted and use them to make calls on the operator's behalf.

Card payments work differently, and only on SiteLink. Where a SiteLink location takes card payment online, the request that carries the card also carries that user name and password through Evervault, the company that encrypts card details for us (Section 4). Evervault can read them on the way. The arrangement exists so that card numbers never reach AnyBay servers in readable form. Every other call AnyBay makes to SiteLink goes straight to SiteLink and carries no card details.

That user account belongs to the operator, and it is how they end our access. Disabling the Corporate API User Account created for AnyBay, in SiteLink Corporate Control Center, revokes AnyBay's access to that SiteLink account at once and in full. The operator does not have to ask us to do it.

Information from an operator's Google Ads account

An operator can connect their own Google Ads account from their dashboard. They sign in with Google and approve access themselves. AnyBay never places an operator's Google Ads account under a manager account of our own.

What we read today.When an operator connects, we read the IDs of the Google Ads accounts that sign-in can reach, so the operator can pick the right one. For each of those accounts, and for the accounts directly under any manager account among them, we read the account's name, whether it is a manager account, and whether it is active, so the operator can pick by name. We show those names while the operator picks and do not keep them. For the account they pick, we read its ID, its currency, and whether it is a manager account, to confirm the connection works. We do not change campaigns, budgets, or anything else in the account.

What we read to show ad costs.An operator's dashboard shows the total their Google Ads account spent in a period next to the move-ins that came from their ads. To show it, we read, for the account the operator picked, each campaign's ID and name and, by day, its cost, clicks, impressions, conversions, and conversion value. We read these from Google each time they are shown and do not keep a copy. We do not send anything about renters to Google to do this.

What we read to sort campaigns by location.So an operator can say which of their locations each campaign is for, we read, for the account the operator picked, each campaign's ID, name, and status (for example, active or paused). We read these from Google each time the list is shown.

What we keep.While an account is connected, we keep the access Google gives us, encrypted. We also keep the ID of the account the operator picked, the manager account it is reached through if there is one, the list of account IDs that sign-in can reach, the account's currency, whether the connection is working, and the reason Google gave if it is not. When the operator assigns a campaign to one of their locations, we keep the campaign's ID, its name as it was when they assigned it, the account it belongs to, and the location they chose, until they change it, the location is removed, or they disconnect Google Ads. Only AnyBay's servers can read these.

How we use it.We use this information only to connect the operator's account and show them their own advertising results. We do not use it to advertise, we do not sell it, and we do not share it with anyone else, except as needed to run the Services, for security, or to meet a legal obligation. People at AnyBay do not look at it unless the operator asks for support, it is needed for security, or the law requires it. AnyBay's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Ending access and deletion.An operator can end our access at any time. Choosing Disconnect on the dashboard deletes everything listed above and asks Google to cancel our access. If the operator instead removes AnyBay from their Google account's third-party access page, we can no longer read the account, and the next time the connection is checked, the dashboard shows it as ended. We keep the stored record, which no longer works, until the operator chooses Disconnect or their AnyBay account is deleted, which deletes it too.

Payment information

Payments are handled by a third-party payment processor. Card and bank details are submitted directly to that processor and are not stored on AnyBay servers. We receive limited confirmation details, such as whether a payment succeeded and the amount, so the rental and ledger stay accurate.

3. How we use information

• To provide, operate, and maintain the Services.
• To display real-time unit availability and pricing on a storefront.
• To complete online move-ins and post discounts to the operator's ledger.
• To follow up on abandoned move-ins. We record which funnel steps a renter reached. Where a renter left an email address and then went quiet, we send one follow-up email on the operator's behalf, in the name of the location they were booking with, saying their details are saved and that the location can help them finish. At most one follow-up email per abandoned move-in, ever, counting a message an operator sends by hand, and every one of them carries a one-click unsubscribe. We do not send follow-up by text message. Before any message goes out we ask the operator's storage software whether the renter has already moved in: if they have, or if the software cannot tell us, nothing is sent. An operator can change how long we wait, or switch automatic follow-up off entirely, from their dashboard.
• To produce funnel analytics and reporting for operators.
• To connect an operator's own Google Ads account and show them their advertising results, as described in Section 2.
• To respond to demo, integration, and support requests.
• To secure the Services, prevent fraud and abuse, and debug issues.
• To comply with legal obligations and enforce our agreements.

4. How we share information

We do not sell personal information. We share information only as described here:

• With storage operators. Renter and move-in data collected through a storefront is shared with the operator that runs it.
• With the operator's own advertising account.When a renter arrives from a paid ad and later completes a paid move-in, the operator can download a file of those move-ins from their dashboard and upload it to their own advertising account, such as Google Ads, to credit the click that brought the renter. That file includes the ad click identifier the ad network placed on the landing URL, the time of the move-in, and the amount collected. The advertising account is the operator's own, chosen and controlled by them, and the operator decides whether to send this data to it. We provide the file at the operator's request, and only for move-ins from the last 90 days, matching the retention window in Section 2.
• With a destination the operator chooses for inbound leads. When an operator turns on lead forwarding, we post a renter's lead form submission to a HubSpot form or to a link the operator names (for example a webhook, Salesforce Web-to-Lead, or Zapier). That destination is the operator's own system, not AnyBay's. We send it at the operator's instruction so their follow-up tools can act on the lead. The renter did not choose that processor; the operator did.
• What a forwarded lead contains.The name, email address, phone number if one was given, any message left, the page the form was on, the website it came from, and the time the renter submitted it. Where the destination is a link the operator names, it also carries an identifier for the submission, so that a retry after a failure updates the same record instead of creating a second one. A HubSpot form carries no such identifier, because HubSpot's form endpoint accepts none, and HubSpot matches a repeated submission by email address instead. It does not carry a renter's payment details, move-in history, or anything from the operator's storage software.
• The texting-consent answer travels with the lead.Where a lead form asked whether the renter agrees to be texted by the operator, that answer is sent to the destination together with the wording the renter agreed to and the time they gave it. An answer on its own is not a record anyone can rely on later, so the three travel together or not at all. To a link the operator names, they are always sent, because the operator owns that receiver. To a HubSpot form, they are sent only when the operator has named the HubSpot field that holds the answer: with no field named, no consent claim is sent to HubSpot at all, rather than being left in a note where nothing can act on it. AnyBay does not send text messages, and does not use this answer for any purpose of its own. It is forwarded so that the operator's own messaging tools can honor it.
• With an operator's storage software. We write completed rentals and related details back to the operator's management software. Where the renter signs the operator's lease during checkout, we also send the renter's IP address, browser and device information and, when our hosting provider supplies it, their approximate location (city, region and country), which the lease records as evidence of who signed it.
• With service providers. We use vendors for hosting, payment processing, email and messaging delivery, and analytics. They may access information only to perform work for us and are bound by confidentiality and data-protection obligations.
• For legal reasons. We may disclose information to comply with law, respond to lawful requests, or protect the rights, safety, and property of AnyBay, our users, or the public.
• In a business transfer. If AnyBay is involved in a merger, acquisition, or sale of assets, information may be transferred as part of that transaction, subject to this policy.

Subprocessors

These are the companies that process information on our behalf to run the Services. Where a storage operator is the controller of renter data, they are subprocessors in that operator's chain, and we remain responsible for them. We will update this list when it changes.

• Vercel (United States) hosts the Services and serves every page.
• Supabase (United States) holds the database and the operator sign-in system.
• Resend (United States) delivers email, including the follow-up message described in Section 3, the email telling a renter their lead form arrived, and operator sign-in links.
• Evervault (Ireland and the United States), where a location takes card payment online, encrypts card details in the browser so they reach the payment processor without passing through AnyBay in readable form. On SiteLink, the same request carries the sign-in the operator gave us for their storage software, and Evervault can read it. See Section 2.
• Sentry (United States) receives error reports from every part of the Services, including storefronts and move-in flows.
• Google Maps Platform(United States) draws the maps on an operator's website. A location's page shows its address on a Google map, and on a website that lists several locations, the pages that list them show a Google map with a pin for each one. Those maps load from Google in the renter's browser, so Google receives what any website that loads something from Google sends it: the browser's IP address and type, and the address of the page. We give the map only the locations' names, addresses and where they sit, and nothing about the renter. We also send a location's street address to Google once, when the operator confirms it, to find where to put its pin.
• Microsoft Clarity (United States) receives product analytics from the AnyBay website and the operator dashboard only, and never from a storefront or a move-in flow. Microsoft acts as an independent controller of that data under its own privacy statement; we describe below what we send and the advertising use we switch off.

An operator's storage software and their own analytics and advertising accounts are not in this list. Those are the operator's own services, chosen and controlled by them. We send data to their storage software and analytics accounts at their instruction. From their advertising account we only read, as Section 2 describes, and any upload to it is one the operator makes.

5. Data retention

We keep information for as long as needed to provide the Services, meet the purposes described in this policy, and comply with our legal obligations. Retention periods vary by data type and by the operator's instructions. When information is no longer needed, we delete it or de-identify it.

Maintenance logs.Each location's maintenance log, the record of work done on its units and on the location itself, is kept in AnyBay and not in the operator's storage software. We do not delete it when the operator's account is closed. An entry someone deletes from a log can be restored for 30 days. After that we remove it from AnyBay, with its photos. We keep only a record of the deletion: who deleted it, when, and which unit or location it was about, never what the entry said.

6. Cookies and analytics

We use cookies and similar technologies to run the site, remember preferences, and understand how the Services are used so we can improve them. Most browsers let you refuse or delete cookies. If you disable cookies, some parts of the Services may not work as intended.

When a renter lands from a paid ad, we may store a marketing click identifier in a first-touch cookie for up to 90 days, so a completed move-in can be credited to the click that brought them. The cookie expires after that period, and a daily job removes any stored copy from funnel records while leaving campaign tags in place. That cookie is separate from any tag the operator runs on their own website.

An operator may paste their own measurement identifier and container identifier so page views and referrer on their published pages report into a property they own: an analytics handoff. AnyBay does not hold a copy of what that property collects and does not read it back. Those tags load only on published pages: not on the canvas, not in a preview, not on the operator dashboard, and not on the page where a renter enters card details. A Do Not Track header does not suppress the operator's own tags; it does apply to instrumentation AnyBay controls.

Some operators put a HubSpot form on a page of their website. On a published page that carries one, served on the operator's own domain, HubSpot's own tracking script loads alongside the form and HubSpot sets its own cookie in the browser of everyone who opens that page, whether or not they fill the form in. HubSpot uses it to recognize someone who comes back and to attach the pages they looked at to a form they later submit. The operator may also extend that script to the rest of their website, including pages with no form on them, and some do. Either way it is subject to the same limits as the tags above, and what HubSpot collects through it is held by HubSpot under their privacy policy. AnyBay does not hold a copy and does not read it back.

All of this requires the operator's own domain. A website served on a shared anybaysites.com address loads no analytics tag, no tag container and no HubSpot tracking script, and no move-in stage is reported from our servers, even when the operator has saved their identifiers and even on a page carrying a HubSpot form. Websites on that shared address write cookies into one place, so a tag there could read what a visit to an unrelated operator's website left behind, and a HubSpot cookie there could follow someone from one operator's website to another's. Nothing is handed to Google or to HubSpot from those pages at all.

On AnyBay's own website and in the operator dashboard, we use Microsoft Clarity to understand how the product is used: which pages are visited, which buttons are clicked, and where someone setting up an account gets stuck. Clarity does not run on a storefront or a move-in flow. A renter's browser on an operator's website never loads it, and no renter activity is sent to it from our servers either. Clarity sets its own cookies to do this, and Microsoft is an independent controller of what it collects. We switch off Clarity's advertising storage, so it is not used to build an advertising profile; we keep only the part that measures how our own product is used.

For a signed-in operator, we send Clarity an account identifier, the identifier of the operator account it belongs to, and the domain part of the sign-in email address, which is how we tell our own testing apart from real use. We do not send the email address itself, or a name.

In the operator dashboard we also record the screen during a signed-in session, so we can see what an operator saw when something went wrong. Every form field is masked, so what is typed is never captured. On the Integrations screen, where an operator enters the details that connect their storage software, the fields and their contents are masked as well, so the details typed there are never captured in a recording. Session recording does not run on a storefront, on a move-in flow, or on the AnyBay website.

We use Sentry to collect error reports, and it does run on every part of the Services, including storefronts and move-in flows. An error report tells us what broke and where, so an operator's website keeps working; it is not used to study how renters behave. Sentry is configured not to attach personal details to a report by default.

The Google map on a page that lists several locations loads only when a renter scrolls near it. It is part of the page, not measurement, so a Do Not Track header does not remove it, and every location it shows is also listed in text on the same page.

There is no cookie banner on the Services. We honor a Do Not Track header for the measurement AnyBay itself runs: with it set, Clarity is never loaded and collects nothing. As noted above, it does not suppress an operator's own tags, which are theirs to run, and those tags may set cookies of their own that we neither place nor read.

An operator who also saves a Measurement Protocol API secret has each stage of the move-in reported into that same property from our servers rather than from the renter's browser: which units were viewed, when contact details were given, when payment was started, and whether the move-in completed or was reserved to finish in person. Those reports carry the unit, the amount for a completed move-in, and the identifiers the operator's own tag set in the browser so the stages join the same visit. They carry no name, email address, or phone number. This reporting happens only for published pages on the operator's own domain: nothing is reported from the canvas, from a preview, from the operator dashboard, or from a website on a shared anybaysites.com address.

7. Your privacy choices and rights

Stopping follow-up email. Every follow-up email about an unfinished move-in carries an unsubscribe link, and using it takes one click: no account, no reply, and nothing to fill in. It stops every further follow-up from that operator, the ones they send by hand included. It is scoped to the operator that sent it, which may run more than one location, because that operator is who the message came from; it does not stop mail from an unrelated operator, and it does not delete the unfinished move-in, so the operator can still reach you by phone if you left a number.

Depending on where you live, you may have the right to access, correct, delete, or receive a copy of your personal information, and to opt out of certain uses. Because AnyBay processes renter data on behalf of storage operators, we will route renter requests to the relevant operator and assist them in responding. To make a request or ask a question, contact us using the details in Section 12. We will not discriminate against you for exercising these rights.

8. Security

We use administrative, technical, and physical safeguards designed to protect information, including encryption in transit and access controls. No method of transmission or storage is completely secure, so we cannot guarantee absolute security.

9. Children's privacy

The Services are intended for businesses and adults. They are not directed to children, and we do not knowingly collect personal information from children under 13. If you believe a child has provided us information, please contact us and we will delete it.

10. Third-party links and services

The Services may link to or integrate with third-party websites and tools, including an operator's storage software, our payment processor, the operator's own CRM or webhook endpoint when they have turned on inbound lead forwarding, and, when the operator has configured an analytics handoff, the operator's own Google Analytics and Google Tag Manager accounts, and the operator's own HubSpot account when they have added a HubSpot form to a page or extended HubSpot tracking to their whole website. Their handling of information is governed by their own privacy policies, and we encourage you to review them.

11. Changes to this policy

We may update this Privacy Policy from time to time. When we do, we will revise the “Last updated” date above. If the changes are significant, we will provide a more prominent notice. Your continued use of the Services after an update means you accept the revised policy.

12. Contact us

If you have questions about this policy or your information, contact us at tyrin@anybay.app.

AnyBay, Inc.