Privacy Policy

• 1. Who we are
• 2. What we collect from you
• 3. Public-record property and owner data
• Removal requests
• 4. How we use information
• 5. Who we share it with
• 6. Selling and sharing
• 7. Cookies
• 8. How long we keep it
• 9. Security
• 10. Your choices and rights
• 11. Children
• 12. Changes
• 13. Contact

1. Who we are

Locumetric LLC ("Locumetric", "we", "us") runs locumetricdata.com and the Locumetric mobile app (the "Service"). This policy explains how we handle personal information when you use the Service. It works alongside our Terms of Service.

2. What we collect from you

• Account details: your name, email address, password (stored only as a one-way hash, never in readable form), the firm name you optionally give us, when you accepted our Terms, and any team you belong to.
• Billing details: payments are handled by Stripe. We receive your plan, billing interval, subscription status, billing period and a Stripe customer reference. We never see or store your full card number. Stripe also gives us a card fingerprint, a code that identifies a card without revealing its number; we use it only to stop one card from redeeming a one-time offer more than once, and to keep the Charter rate to one per card. During a pilot we also record whether a card is on file, and when one was added, so we know whether your membership continues when the pilot ends.
• Invitations: when a team owner or admin invites a colleague, or we invite a design partner, we store the invitee's email address (and who sent the invitation) so we can send the invitation and recognize it when it's accepted. A team invitation link expires after 14 days.
• What you do in the Service: the addresses and parcel IDs you search, the reports you generate and download, credits used, questions you ask the AI Analyst and its answers, and (in the mobile app) saved searches, watchlists and an activity history. When you use Intelligence we also keep: what your team bought (reports, profiles, lists and briefs) so you can re-open it; a record of searches, previews, unlocks, list rows and downloads (usage events) for fair-use limits and security; the quick looks you run before a report; the share links you create, the contact details you choose to show on them, and the time of each view of each link (logged per link, without the viewer's IP address or browser, and shown to your team); your team's branding (firm name, logo, brand colour and default cover note) if you add it; your team's assignments (the client name your team types, a note, a status, the reports, links and lists linked to it and their activity, shown to your team only); your team's watchlist (the properties and companies you watch, the public records found for them, and each member's read mark and alert e-mail choices, shown to your team only); and, for each file you download, an identifier written into the file that ties it to your account and the time of download.
• Comp notes, comp selections and your own comps: on a report, your team's comp notes (include or exclude, a reason and a note on a comparable sale); your team's comp selection (the sales it leaves out, with the reason for each, and the sales it puts back or adds) and a frozen copy of it for the documents made with it; the alternates your team chose to see; the off-market sales your team enters (price, date, building and land size, property type, address or label, and a note); and a record of each change and of each document made with the selection, with who made it and when. These are your team's own: users outside your team never see them, and we never pool them, add them to our property data, or use them to improve estimates or test our methods. A client sees only what a document you give them shows (with your figure: the sales used, the reasons sales were left out, and the sales you entered, labelled as yours), never your team's comp notes or the notes on the sales you entered. Our staff don't look at a team's selection, notes or own comps, except what you send us yourself (for example with "Is this value right?" or a support request) or when the law requires it.
• Value feedback: your answer to "Is this value right?" on a report: your verdict (looks right, too high or too low), which figure it is about (Locumetric's estimate or your comp selection), and anything you choose to add: a reason, which comparable sale you think is wrong, your own value or a note. It goes to the Locumetric team with the report, its version, the figure shown and your team, and we use it to check our estimates and data.
• Impact questions, feedback and testimonials (optional): after a report, we may ask a few optional questions: roughly how much time the report saved you, whether you used it for a client, a deal or a decision (yes, not yet or no only: we never ask who the client is, so please don't name your client in a comment), and a comment if you want to add one. Feedback you send us as "Something worked well" can also say what it let you do and about how much time it saved. We may also ask you for a testimonial, with a short form we send you a link to: what you choose to say about how you used the Service and, if you give them, your name, firm, role and credentials. We store your answers with your account, the report they're about (if any) and the time (for a testimonial, also when you first opened its link); the Locumetric team can see them, and other members can't. Answering is optional, and skipping the questions changes nothing in your account. We use the answers in aggregate (see section 4). We quote what you wrote only if you give us explicit permission in the form, and we record when you gave it: anonymously, without your name or firm, or with your name (and your firm) only if you choose that. We may use a quote you allow in our marketing and as supporting evidence for Locumetric (for example, in applications and filings that describe its use). To withdraw a permission to quote you, write to support@locumetricdata.com; we then stop any new use of that quote, but we can't recall copies already published.
• Page-use counts: to learn which parts of our reports are useful, we count, per day, how often each report section is shown on screen, a "?" definition is opened, a section is included in a share link, and a PDF or spreadsheet is downloaded. We keep only those daily totals. They don't record who you are, which report or property you looked at, or your IP address, and no third party is involved.
• Clients you send a report to: when you e-mail a share link to a client through the Service, we store the client's email address (and the name you give) with that link, so we can send it and your team can see who it went to. We send that client only the email you asked us to send; we don't add them to any list or contact them otherwise.
• Documents you upload: rent rolls, offering memoranda, leases and similar files, and the rent data extracted from them. These can contain information about third parties, such as tenant names; you are responsible for having the right to share them. Our team can see your uploads, and PDF and text files are processed by our AI provider to extract the rent data.
• Messages: what you send us when you contact support or use the feedback form, including any screenshot you attach.
• Technical data: IP address, browser or device type, and timestamps, recorded in server logs and used for security and rate limiting.

3. Public-record property and owner data

The Service is built on public records. We compile public property, business-registry, zoning, lease and loan records. These records can name people in the roles in which they were recorded, together with the addresses filed with them. For example: the owner of record of a property and the owner's mailing address; a company's officers, its registered agent and the agent's address, and its principal office; the beneficial owners a District of Columbia company reports, with their addresses; the applicant or owner in a zoning case; or a landlord, tenant, borrower or lender named in a lease or loan record. Some owners are individuals, and some filed addresses are home addresses.

We show members these names, roles and addresses as the records give them, and members can search by a person's name. Phone numbers and email addresses that appear in public records are shown as filed, with the record they come from, and a removal request covers them like the rest of the record. We also match these records to property owners automatically (for example, to link an owner to the company filings behind it) and group related entities. These matches are automated and can be wrong.

Where it comes from: parcel, assessment, sales and zoning records published by county and city governments; business-entity filings from the Virginia State Corporation Commission, the Maryland State Department of Assessments and Taxation and the District of Columbia government; and public federal records and filings that describe commercial leases and loans, such as HUD records, SEC filings for commercial mortgage-backed securities and GSA lease records. Data from the District of Columbia is licensed under CC BY 4.0.

Asking us to remove information: anyone can ask us to hide information about them through our removal request form. A request made through the form applies right away to the name and address it gives, and our team reviews it within 72 hours. See Removal requests below.

We can't change what a government publishes, but if something we display about you is inaccurate, or you have a question about it, write to support@locumetricdata.com and we will review it.

Removal requests

You can ask us to hide personal information about you, or about someone you are authorized to act for, such as a name or an address that appears in the public records we show. Judges, law-enforcement officers, victims of crimes such as domestic violence or stalking, and their authorized representatives can use the same process.

• How to ask: use our removal request form (https://www.locumetricdata.com/privacy/removal); you don't need an account. You can also email support@locumetricdata.com.
• Applied immediately: as soon as we receive a request through the form, information matching the name and address in it is hidden from our members' searches, reports and exports while we review it. Records listed in a request are reviewed by our team before they are hidden. Files a member already downloaded can't be recalled.
• Reviewed within 72 hours: our team reviews every request within 72 hours. If we approve it, the information stays hidden. If we can't confirm it, we'll tell you, and the information may be shown again.
• What we may ask to verify: that you are the person named, or that you can act for them. For example, we may contact you at the email address or phone number you gave, ask you to write from an official court or agency email address, or ask for a signed authorization from the person named. We ask only for what we need to confirm the request.
• What we keep: we use the information in a request (who it is about, your contact details and what you sent us) only to handle it and to keep the matching information hidden. We keep it for as long as the removal applies and for 3 years after it ends (for example, after a removal is lifted or we decline a request), so we can show how the request was handled. Then we delete the personal information in it; we keep only a record that a request was handled (its dates and outcome).

A removal covers what Locumetric shows. We can't change what a government office publishes.

4. How we use information

• To provide the Service: find comparable sales, estimate values, build and deliver your reports, answer your AI Analyst questions and extract rent data from your documents.
• To run your account and billing, including credit balances and team credits.
• To send service emails, such as your welcome email, password resets, membership confirmations and renewal reminders, team invitations, and important account or policy notices. We don't send marketing email without a way to unsubscribe.
• To keep the Service secure: preventing abuse, enforcing rate limits, fair-use limits and our Terms (including short holds on unusual activity and tracing files redistributed in breach of them), and investigating problems.
• To improve the Service, mostly through aggregated usage and data-quality statistics. Anonymized, aggregated rent figures from uploaded documents (never the documents themselves) may in future help improve estimates for all users; today they don't, because that pooling is switched off. We also count, across all teams, how often each reason is given for leaving a comparable sale out of a comp selection (for example "Not arm's length"), and how often selections are changed, sales are added or entered and alternates are shown; those counts name no team, member, report or property, and a count under 5 isn't shown.
• To measure and describe what the Service does for its users: we combine counts of what accounts do in the Service (for example, how many reports are run and in which jurisdictions, how long they take to deliver, and how often they are shared with a client, downloaded or re-run), including your account's own report and usage counts, with the answers to our optional impact questions, into aggregate statistics that we may publish or share (for example, with investors, partners or our advisers, or in applications and filings that describe the Service's use). Those statistics don't name any member, team or client, or the properties a member looked at. Accounts we run ourselves, including test accounts and accounts used for testing at our request, are labelled as such and counted separately from members' accounts. We quote a comment or testimonial only as described in section 2.
• To meet legal obligations, such as tax and accounting records.

5. Who we share it with

We use a small number of service providers who process data on our behalf, only as needed to provide their service to us:

Pages also load a few public resources directly in your browser: maps and address lookup from OpenStreetMap services, and open-source scripts from public CDNs (unpkg and jsDelivr). Those providers receive your IP address and, for address lookup, the address you searched. The client page of a share link that shows a map loads the map the same way, so those providers receive the viewer's IP address.

We also share information when you ask us to (for example, with your team's owners and administrators, who can see each member's credit usage), when the law requires it, to protect the rights and safety of our users or others, and with a buyer or successor if the business is sold or reorganized, under this policy.

6. Selling and sharing

We don't sell our members' account information (what we collect from you, described in section 2), and we don't share it for targeted or cross-context advertising. Our paid product includes public-record information that can name people, together with the addresses filed with them, as described in section 3; anyone can ask us to hide information about them through our removal request form. There are no advertising or analytics trackers in the Service.

7. Cookies

We only use cookies the Service needs to work:

• a session cookie that keeps you signed in while you use the site;
• a security token cookie that protects forms against cross-site request forgery; and
• a "keep me signed in" cookie, only if you tick that box at sign-in.

We don't use advertising, analytics or cross-site tracking cookies. The mobile app stores its sign-in token on your device instead of cookies.

8. How long we keep it

• Account, reports and usage: while your account is open. After you ask us to close it, we delete or de-identify this information within 90 days, except as below.
• Stored results: what your team bought is kept while the purchasing team's account exists, so it can be re-opened. Removal requests apply to it at every re-open and download.
• Comp notes, comp selections and your own comps: kept with the report, together with the record of changes, while your team's account exists, so each document made from a selection can be explained. A share link keeps the selection it was made with until it expires or is withdrawn. Counts of exclusion reasons identify no one and may be kept.
• Share links: each link and its view count are kept with the report it shares, together with any client email address entered to send it; a link stops working when it expires (30 days) or is withdrawn. The log of each link's view times is deleted after 60 days.
• Download identifiers: kept with the record of the download, so a redistributed file can be traced to the account it was issued to.
• Usage events (searches, previews, unlocks, list rows, downloads), kept for fair use and security: deleted after 90 days. Quick looks: deleted after 30 days.
• Page-use counts: daily totals that identify no one, kept for up to 25 months.
• Impact answers and testimonials: kept while your account is open and handled with it when it closes (see the first point). Aggregate statistics identify no one and may be kept.
• Billing records: kept as long as tax and accounting law requires (often up to seven years).
• Uploaded documents: until you ask us to delete them or close your account. Anonymized, aggregated figures derived from them may be kept.
• Removal requests: for as long as the removal applies and for 3 years after it ends (or after we decline the request), so we can show how it was handled. Then we delete the personal information in them; we keep only a record that a request was handled (its dates and outcome). See Removal requests.
• Password-reset links expire after 60 minutes. Server logs are kept for a short period for security and troubleshooting.
• Backups are overwritten on their normal cycle, so deleted data can stay in them for a limited time.

9. Security

We use HTTPS for the website and API, store passwords only as salted hashes, keep uploaded documents in access-restricted storage, and limit who on our side can reach production systems. No system is perfectly secure; if we learn of a breach affecting your personal information, we will notify you as the law requires.

10. Your choices and rights

You can cancel your subscription at any time in the billing portal. You can also ask us to:

• tell you what personal information we hold about you and give you a copy;
• correct information that is wrong, including your name or email address;
• delete your account, your uploaded documents, or other personal information (subject to the retention exceptions above);
• stop quoting you, by withdrawing a permission you gave with an impact answer or a testimonial.

Email support@locumetricdata.com from the address on your account. We may need to verify your identity, and we aim to respond within 30 days. Depending on where you live (for example, Virginia or another state with a privacy law), you may have additional rights, including the right to appeal a decision about your request by replying to our response. We won't treat you differently for exercising your rights.

11. Children

The Service is for professionals and is not directed to children. We don't knowingly collect personal information from anyone under 18.

12. Changes

We will post any update here with a new "Last updated" date, and tell you by email or in the Service before a material change takes effect.

13. Contact

Privacy questions or requests: support@locumetricdata.com.

Locumetric LLC
10114 Walker Woods Dr, Great Falls, VA 22066

See also our Terms of Service.