Privacy policy.
Effective September 20, 2026.
Reclearly is operated by Turbo Link LLC. This policy explains what information Reclearly holds, why, who it is shared with, how long it is kept, and how to have it removed.
Who the people in this policy are
Reclearly is sold to real estate agents, teams and brokerages. Those customers are the account holders. Most of the personal information in the system belongs to other people entirely:
- Sellers and buyers, whose names, contact details, property addresses and transaction dates are entered by their agent
- Buyer's agents, who receive showing feedback requests
- Open house visitors, who enter their own details at a kiosk
- Newsletter subscribers, imported by the agent from their own sphere
- Leads, who submit a home value request on an agent's public market page
For that second group the agent is generally the party who decides what is collected and why, and Reclearly handles it on the agent's instructions. If you are a seller, buyer or visitor and you want your information corrected or removed, the fastest route is your agent. You can also write to us directly at the address at the end of this policy and we will act on it.
What is collected
From account holders. Name, email, phone, brokerage, profile photo and logo, and billing details held by Stripe. Reclearly does not store card numbers.
Entered by an account holder. Name, email, phone, property address, transaction dates and milestones, showing notes and feedback, documents the agent uploads, and any notes the agent writes.
Collected automatically. Portal view events, which record that a portal was opened and when. This is what drives the engagement figures an agent sees. It is first party. There is no third party advertising and no cross site tracking anywhere in the product.
Market data is not personal information. It comes from FRED and the Realtor.com monthly research file, and it describes places, not people.
Client portals
Portals are deliberately unauthenticated. A client opens a long random link rather than creating an account, because making a seller register is exactly the friction the product exists to remove. In practice that means:
- Portal links are long and random, and an agent can revoke one at any time
- Documents are held in a private store and served through short lived signed links
- Portal reads are rate limited
- Sensitive material is kept off portals by design. Full contracts and government identifiers are not portal content
Services you connect yourself
An agent can connect Reclearly to other tools. Nothing is connected by default, and disconnecting is available in Settings at any time.
- Follow Up Boss, and Lofty when that connection is enabled. When connected, Reclearly writes contacts, transaction stages, notes and the client's portal link into that CRM, and reads back contact detail changes made there. What is sent is the deal information already in Reclearly.
- Google Calendar. Covered in its own section below.
- Zapier, API keys and webhooks. An agent can send their own Reclearly data to a system of their choosing. Where that data goes after it leaves Reclearly is governed by whoever operates the receiving system, not by this policy.
Google user data
This section describes Reclearly's use of Google Calendar and applies whenever an account holder connects a Google account.
What Reclearly asks for, and why.
calendar.calendarlist.readonly. To show a list of the calendars you can write to, so you can pick which one Reclearly should use. Reclearly reads the list of calendars only, never their contents.calendar.events. To create, update and delete the events Reclearly puts on the calendar you picked: showings, open houses, closings and deadlines. The same scope is what lets Reclearly notice when you move one of those events in Google so the matching date in Reclearly moves too.
What is stored. Reclearly stores an encrypted Google access and refresh token, the id and display name of the calendar you selected, a Google synchronization token, and a list linking each Reclearly record to the id of the Google event created for it. Nothing else from your Google account is stored.
What is read, and what is discarded. To detect a moved event, Google returns the changes on the calendar you selected, which can include events Reclearly did not create. Reclearly matches each change against the events it created and ignores every other one. The contents of events Reclearly did not create are never stored, never shown to anyone, and never used for any purpose.
What Reclearly never does with Google user data. It is never sold. It is never transferred to anyone except as required to provide the calendar feature you turned on, or where the law requires it. It is never used for advertising. It is never used to train, retrain or improve any generalized artificial intelligence or machine learning model. No person at Reclearly reads it, except with your explicit consent to resolve a support issue you raised, or where the law requires it.
Limited Use. Reclearly's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
How to disconnect and delete it. In Reclearly, open Settings, find Calendar, and choose Disconnect. Reclearly removes the events it created from your calendar, deletes the stored tokens and the calendar links, and asks Google to revoke the token. You can also revoke Reclearly's access at any time from your own Google account at myaccount.google.com/permissions. Revoking there stops all further access immediately; the stored tokens become unusable and are removed the next time Reclearly attempts to use them, or sooner if you disconnect in Settings.
A separate option that uses no Google data at all. If you would rather not connect an account, Reclearly can give you a private subscription link that any calendar app, Google Calendar included, can subscribe to. That option is read only, grants Reclearly no access to your Google account, and is available to everyone.
AI features
Four features send account data to Anthropic: extracting the terms of an uploaded offer, extracting dates from an uploaded purchase agreement, the daily market briefing, and the in-product assistant. Extraction results are always shown to the agent to confirm before a client ever sees them. The briefing is grounded only in figures the system fetched, and it shows its sources.
Assistant conversations are kept. What you ask the in-product assistant, and what it answers, is stored so we can see whether it is answering well and what people need that the product does not yet do. Only Reclearly's operator can read it, never another customer. The information the assistant looks up on your behalf while answering, which is your own listing and client data, is not copied into that record. How long it is kept is set out below.
Sub-processors and where data lives
Supabase (database, authentication, file storage), Vercel (hosting), Stripe (payments), Resend (email), Anthropic (the AI features above). The primary database is in AWS us-east-2, in the United States.
How long information is kept
Transaction and client data: two months after cancellation. Two months after an account is cancelled, that account's data is deleted: listings, buyers, timelines, offers, showings and their feedback, documents, portal view analytics, leads, newsletter subscribers and open house visitor records. Uploaded files are removed from storage in the same job.
Assistant conversations: ninety days. What you ask the in-product assistant, and what it answers, is deleted ninety days after the exchange. That clock runs on the age of the conversation, so it applies whether or not the account is still active. If an account is cancelled, its assistant conversations go with the rest of its data in the job described above, whichever comes first.
Account identity is kept until deletion is requested. The login and the account holder's own profile row are not removed by that job, because ending a subscription and erasing a person's login are two different acts. Write to the address below to have the login and profile deleted.
Residual copies may remain in encrypted database backups for up to seven days after deletion, after which they age out. Point in time recovery is not enabled on the production database, so no continuous copy holds data beyond that window.
Your rights and how to reach us
Write to chris@cjohio.com to ask what is held about you, to have it corrected, or to have it deleted. Tell us enough to find the record, for example the email address or the property address it relates to. We will confirm who you are before acting on a request, and we aim to respond within thirty days.
If your information is in Reclearly because an agent put it there, we will normally pass the request to that agent, who decides what happens to it, and we will tell you that we have done so.
Changes to this policy
If this policy changes materially, the effective date above changes and account holders are notified by email before the change takes effect.
Contact: chris@cjohio.com