What we collect, and why
This website collects almost nothing. The product collects a government ID and a selfie, because a stranger is about to walk into an empty unit alone. It also holds the messages and calls of the business that uses it. All of it is set out below.
Last updated · October 22, 2026
- 01
Who we are
MYREMOTELY LLC operates MyRemotely.ai: this website, the leasing service at app.myremotely.ai, and the MyRemotely app for Android (package ai.myremotely.app). Our address is 3205 N Wilke Rd #3205-121, Arlington Heights, IL 60004, USA.
For this website, we decide what is collected. For the product and the app, the property manager who uses them decides: they are the business, and we process the data on their instruction. If you toured a unit and want your data removed, write to us anyway. We will route the request to the right party and tell you where it went.
- 02
This website uses no analytics
We run no analytics, advertising pixel or session recorder on this site. The site code sets no cookies. Cloudflare may set security cookies while it protects the site. The embedded services named below load from other companies and may set their own cookies.
Cloudflare serves every page. It receives your IP address because it cannot deliver a page without one. Any log Cloudflare keeps to serve and protect the site belongs to Cloudflare and follows its terms. We do not use it to build a profile of you and we do not use it for marketing.
The vacancy calculator on the home page runs entirely in your browser. The rent and unit counts you type stay on your device. They are never sent to us.
The product is a separate application with its own, narrow analytics. Section 08 describes it.
- 03
What you send us on purpose
There is no contact form on this site. To reach us you send an email, you call, or you book a slot in the scheduler. Whatever you write in that message is what we hold, and we hold it to answer you.
The scheduler on /meeting is HubSpot's, embedded in the page. Booking a demo sends your name, your email address and the time you picked to HubSpot, which is our CRM. HubSpot may set its own cookies. You can avoid the embed by writing or calling instead.
The mutual NDA on /nda is handled by SignNow, also embedded in the page. SignNow takes the name, email address and signature you enter, and keeps the record of the signing. That embed is a second third party in the page, so treat it the same way you treat the scheduler.
The video on /about uses YouTube's privacy-enhanced player at youtube-nocookie.com. When the player loads, YouTube receives the request. Playing a video can send more viewing data to YouTube. You can use the rest of the site without loading that video.
- 04
The product: a government ID and a selfie
This is the collection that matters, so it gets a plain description. Before the product gives a visitor a door code, it checks who they are. The visitor photographs a government ID and takes a selfie. The product reads the ID, compares the face in the selfie to the face on the ID, and records whether the two matched.
That means we handle:
- an image of a government identity document
- the data printed on it, such as name, date of birth, document number and expiry date
- a selfie image
- the result of the comparison between the two, and the time it was made
The reason is narrow and it is the whole reason. A self-guided tour puts an unaccompanied stranger inside somebody's property, often at night, with nobody there. The owner is entitled to know who that person was. Without the check, the door code goes to a name typed into a form.
Identity checks run through an identity vendor: Persona, Stripe Identity or Didit, depending on the account. The visitor does this step in a web browser. The MyRemotely Android app does not take ID photos or selfies; it shows only the result. We use this data to decide whether to issue a door code and to answer a later question about who was let in. We do not use it for advertising, we do not sell it, and we do not use it to train a model.
- 05
The product: tours, codes and the access log
Around the identity check, the product records the tour itself: the inquiry and the messages in it, the unit, the tour window, the access code issued for that window, which locks accepted it, and when it expired or was removed. Each code is written for one unit and one window, then taken away when the window closes.
That log exists to be handed to an owner, an insurer or a court. It is scoped to the customer's organisation. Other customers cannot see it, and neither can the public.
- 06
The product: accounts, messages and calls
To run the leasing work of a business, the product holds:
- team member accounts: name, sign-in email, role and organisation. A password is stored only as a hash.
- prospect contact details the business receives or enters: name, email address and phone number
- text messages (SMS) between the business and prospects, sent and received through Twilio and Telnyx
- internal notes, and email copies of conversations where the organisation turns that on
- business phone calls made or answered in MyRemotely, including calls that Remo, our AI agent, answers. A call can be recorded. We then store the recording, a written transcript and a short summary. Voicemail is recorded and stored the same way.
- unit photos, files and documents, only when a team member uploads them
Remo reads the messages and call transcripts of a conversation to draft replies and summaries. To do that, the conversation text goes to the AI model provider that runs Remo. This data is used to run the service for the business. We do not use it for advertising and we do not sell it.
- 07
The MyRemotely Android app
The app shows the MyRemotely web application at app.myremotely.ai and adds one native feature: a call to the business phone number rings the phone, also when the app is closed or the screen is locked. Business data stays on our servers, not on the phone.
What the app collects in addition to the product data above:
- a push token from Google Firebase Cloud Messaging. We store it with your user and organisation, the platform, whether you are available for calls, and when the phone was last seen. We use it only to ring your phone for incoming calls and to show a missed call.
- the caller's phone number and name, which an incoming-call notification carries to your phone
- microphone audio, only during a call you answered or started. The audio streams over an encrypted connection to the call; the app does not record on the phone.
The app asks for the microphone and for notifications. It also uses a full-screen incoming-call screen, a foreground service that keeps an active call open, and a wake lock while a call rings. It asks for no location, contacts, camera, storage or Bluetooth access. It shows no ads and contains no advertising SDK.
Uninstalling the app stops calls ringing on that phone. It does not delete your account. To delete your account and data, see /account-deletion.
- 08
Product analytics and error reports
The product, in the browser and in the app, sends one analytics event to PostHog: that a page of a given kind was viewed, such as "Units" or "Calls". The event carries a random id that is not tied to your account. It carries no web address, no record id, no name and no organisation. Location lookup, session recording and person profiles are turned off.
When the product hits an error, it sends an error report to our own error-tracking service, which we run ourselves. A report holds the error message, the code location and the software version. It is set to leave out user details, cookies and request headers. We use the reports only to find and fix faults.
- 09
How we protect it
All traffic between your browser or the app and our servers is encrypted in transit with HTTPS (TLS). That covers the web application, the app, push notifications, call audio and media. Each organisation's data is separated from every other organisation's.
This page does not describe encryption at rest, key management or penetration testing. We will not state a control we cannot show you evidence for. Ask, and we will answer in writing.
- 10
How long we keep it
Account data stays while the account exists. When a team member's account is deleted, their sign-in, their sessions and their phone registrations for calls are removed at once. The deletion steps and what is kept are on /account-deletion.
Messages, call recordings, transcripts, summaries, identity results and access records belong to the property manager's business. Their retention period is not fixed on this page. It is set in the agreement with each property manager, because they own the tenancy record and the obligations that come with it.
This is a real gap and we are not going to paper over it with a number we cannot keep. A face image, an identity document and a call recording deserve a published schedule that says how long each is held and when it is destroyed. Until that schedule is on this page, write to us at the address below and we will tell you the period that applies to your data.
- 11
Who else processes it
The companies that handle data on our behalf today:
- Cloudflare — serves this website at the edge
- HubSpot — our CRM, and the scheduler embedded on /meeting
- SignNow — the NDA signing flow on /nda
- Persona, Stripe Identity and Didit — identity document and selfie verification in the product
- Twilio and Telnyx — the SMS and phone calls the product sends and receives
- Google Firebase Cloud Messaging — delivers incoming-call notifications to the Android app
- PostHog — the page-view count described in section 08
- AI model providers — generate Remo's replies and call summaries from conversation text
Two more groups sit beside that list. Lock vendors, TTLock and Sifely, receive the codes the product writes to their hardware. Property management systems, Rentvine and Showdigs, exchange unit and lead data when a customer connects them. A customer chooses those connections; we do not add them on our own.
- 12
Your rights over your data
You can ask us what we hold about you, ask for a copy, ask us to correct it, and ask us to delete it. You can also ask us to limit how we use sensitive data. An identity document and a face image are the most sensitive things we touch, so that last right reaches the data that matters most. These rights are open to every reader, wherever you live.
We do not sell personal information. We do not share it for cross-context behavioural advertising. There is no advertising technology anywhere on this site, in the product or in the app to do either with.
We will not treat you worse for exercising a right. Send the request to the email address below with "Privacy request" in the subject line, or "Delete my account" to delete a MyRemotely account. We will answer within 45 days, and we will tell you if we need longer. To find your record we may need the email address, the phone number or the unit you toured; we ask only for what identifies you.
- 13
Children
This site, the product and the app are for adults renting and managing homes. We do not knowingly collect information from a child.
- 14
Changes, and how to reach us
When this policy changes, the new version replaces this one here and the date at the top changes with it. A change that alters what we collect or why will be called out, not slipped in.
Ask us anything about this page:
- info@myremotely.ai
- 956-275-7366 (956-ASK-REMO)
- 3205 N Wilke Rd #3205-121, Arlington Heights, IL 60004
This is a plain-language summary of how we work, written to be understood rather than to be impressive. It is not legal advice, and it is pending review by counsel.