AtriaLegal
Last updated: October 4, 2026
Atria is operated by Senso Labs Inc. ("Senso Labs"), which is committed to maintaining robust privacy protections for its users. This Privacy Policy ("Privacy Policy") is designed to help you understand how we collect, use, and safeguard the information you provide to us and to assist you in making informed decisions when using our Service. For the purposes of this Privacy Policy, "Service" refers to askatria.ai and the services Senso Labs offers through it, including Atria Scout, the Atria MCP server and API that connect software agents to Atria, data rooms, owner outreach, and our advisory work. The terms "we," "us," and "our" refer to Senso Labs. "You" refers to you, as a user of our Service. By accessing our Service, you accept our Privacy Policy and Terms of Service and you consent to our collection, storage, use, and disclosure of your Personal Information as described in this Privacy Policy.
We collect "Non-Personal Information" and "Personal Information." Non-Personal Information includes data that cannot be used to personally identify you, such as usage statistics, referring and exit pages, and device-specific data. Personal Information includes data that can identify you personally, such as your name, email address, and the content you submit to the Service.
When you create an account, we collect your name, email address and a password, which we store only in hashed form, and the name of your organization. You may also choose to sign in with a Google account, in which case Google shares your name, email address and profile photo with us. Some features ask for a phone number or an address, which we keep with your account. If you subscribe to a paid plan, our payment processor collects your payment details; we keep only the identifiers it gives us to link your subscription to your organization.
We store what you submit so the Service can work and so your team can return to it: the addresses, coordinates and parcels you search for or screen, the descriptions of the sites you are looking for, your conversations with Atria's chat features, and the projects, data rooms, mail campaigns and notes you create.
You can connect a software agent to Atria through the Atria MCP server. When you connect an agent, your agent's client asks you to sign in to Atria and approve the connection, and it then receives a token that lets it call Atria on your behalf. You can also create API keys for programs that call Atria directly. We store tokens and keys in hashed form, keeping only a short prefix of each in readable form so you can tell them apart, together with their names, scopes, the client they were issued to and when they were last used. You can revoke a connection or an API key at any time from the Agents page in your dashboard.
For each call an agent or program makes, each call you make from the playground in your dashboard, and each crawl Scout charges for, we keep two kinds of record. The billing record holds your organization, the key or connection used, the tool, the credits charged, the outcome, how long the call took and when it was made. The content of the call holds the inputs it sent (such as an address, a coordinate, a parcel number, a county, an owner name, or the first 200 characters of a question), the location the call resolved to, any error, and for a crawl the search it ran. We use these records to bill your organization, to show your team its activity, to protect the Service from abuse, and to find and fix errors in the results we return.
Your organization controls how long call content is kept. By default we delete it 30 days after the call; an owner can shorten that to 7 days, or choose not to store what was asked at all, in which case we keep only the billing record from the next call onward and clear content already stored within a day. When a call asks about a county Atria has not mapped yet, or for zoning rules Atria does not hold yet, we record a request to fetch them, which holds the county or jurisdiction, the zoning district asked about and the key that asked. A request to map a county also holds the location asked about, which we delete one day after the request finishes, or seven days after it was made if it never finishes. To check the accuracy of parcel lookups, we compare a sample of them against a second source; the inputs and results of those comparisons are deleted after 30 days, and we make no new comparisons for organizations that choose not to store what was asked. When an agent asks to start a crawl, we keep the request it made until you approve or decline it.
The Service returns information about land in the United States from public records, such as county parcel and assessor records and federal datasets. These records can include the name and mailing address of a property's owner of record, and where a county publishes them, other details it lists for the owner. We store these records with the searches and results that use them. When you enrich the owners in a campaign and an owner is a company, the Service looks up the people behind it in public business filings and on the public web, and stores their names, their roles and links to the sources it used. It also checks owners' mailing addresses with an address verification provider, which reports whether the address is deliverable or vacant.
For owners who are individuals, and for the people behind company owners, the Service can also look up phone numbers and email addresses through BatchData, a contact-data provider, by sending it the person's name and mailing address. We do this when you enrich the owners in Scout. BatchData tells us whether each phone number is on a do-not-call registry, and we keep that flag with the number so the organization that requested it can honor it. We store these contact details with the results of the organization that requested them.
When you run an owner outreach campaign, we store the owners and addresses it is sent to and any replies those owners send. Each letter can carry a code unique to its recipient; when the owner scans it, we record that it was scanned and when, and the page it opens lets the owner send their name, phone number, email address and a message, which we store with the campaign.
If you are a property owner and have questions about information we hold about you, or want us to delete the phone numbers and email addresses we hold for you, email khalil@askatria.ai.
We use cookies to keep you signed in and to remember your settings, and we collect aggregate usage information about how pages are visited, to see which pages are used and to fix problems with them. When you first visit our website, we also set a cookie of our own, kept for 90 days, that records how you arrived: the site that referred you, any campaign details in the link you followed, the page you landed on, when you arrived and, if you arrived while connecting an agent, which agent client it was. If you then create an account, we save that information with your account, together with your answer if you choose to tell us how you heard about Atria. We use it only to understand where new users come from. Our public website also loads advertising and visitor-identification tags from Google Ads and Leadsy, which set their own cookies and receive information about your visits, such as the pages you view and your IP address, so we can measure our advertising and learn which organizations visit our site. Our sign-up form uses a bot-protection check that inspects your browser and receives your IP address to tell people from automated programs.
Our Service is not directed to individuals under 13. We do not knowingly collect data from children under 13. If you believe that a child under 13 has provided us with Personal Information, please contact us, and we will promptly delete such data.
We use Personal Information primarily to provide and enhance our Service, such as answering your questions, running your searches, billing your organization and providing technical support. We do not sell your Personal Information. We share it with the service providers listed below so they can perform services for Senso Labs, and the advertising and visitor-identification tags described above receive information about visits to our public website.
These providers process information on our behalf to run the Service:
To answer a question about a place, the Service also queries public data sources, such as county and state geographic information systems and federal agencies. Those queries carry the location asked about, not your identity.
We use aggregated Non-Personal Information to analyze usage patterns, improve functionality, and enhance the user experience. If Senso Labs undergoes a business transaction, such as a merger or acquisition, Personal Information may be transferred as part of the assets involved in the transaction.
We keep the billing records of agent, API, playground and Scout crawl calls for 12 months, after which we delete them. Call content is kept for 30 days, or the shorter period your organization chooses, as described above. These periods apply to calls made from October 4, 2026; records of earlier calls follow our previous 12-month retention. They apply only to the records of calls described above, not to the work you keep in the Service. Our hosting providers keep server logs for their own limited periods. We keep your account information, including how you first found us, and the content you create, such as crawl results, data rooms, theses, Scout chats, projects and campaigns, together with the crawl requests your agents make, for as long as your account exists. Owner contact details are kept with the results they belong to on the same basis, unless the owner asks us to delete them. You can ask us to delete your account and its data at any time by contacting us.
We implement industry-standard security measures, such as encryption in transit and access controls, to protect your data. Passwords, API keys and agent connection tokens are stored in hashed form, so we cannot read them back; for keys and tokens we keep only a short prefix in readable form to identify them. However, no security measures are foolproof. By using the Service, you acknowledge and agree to assume the risks associated with transmitting data over the Internet.
You may ask us to stop sending you promotional communications by contacting us. Administrative emails, such as updates to our Privacy Policy, will still be sent. You can revoke agent connections and API keys from your dashboard at any time. You may ask us for a copy of the Personal Information we hold about you, or ask us to correct or delete it, by contacting us.
Our Service may contain links to third-party sites. We are not responsible for their privacy practices. Please review their privacy policies before interacting with those sites.
Senso Labs reserves the right to amend this Privacy Policy at any time. Changes will be communicated via email or prominent notices on our site. Material changes take effect 30 days following such notice.
For questions about this Privacy Policy, please contact us at info@askatria.ai.
Some features send your questions and the data needed to answer them to the language model providers listed above. We send them only what a request needs. Anthropic processes our requests under zero data retention: it does not keep the data we send it and does not use it to train its models. OpenAI and Google process our requests under their terms for API customers. We do not use your questions, your call records or your content to train any model, and we do not give them to anyone else to train models. Through the MCP server and API, the only tool that sends text to a language model provider is the one that answers plain-language questions: it sends the question and the data Atria gathered for it to Anthropic. The other tools query public data sources and a routing service with the location only, not your identity. Conversations with Atria's chat features are stored with your account, as described above, so that you and your team can return to them.