Legal

Privacy Policy

DRAFT · prepared 2026-10-13 · effective date: [on adoption]

1. Scope
2. Information about account holders
3. Public-records information about properties and owners
4. How we use information
5. How we share information
6. Cookies and local storage
7. Retention
8. Security
9. Your choices and rights
10. Children
11. Changes
12. Contact

1. Scope

This policy covers Presage Finder, proplore.ai and app.proplore.ai, operated by [Presage Property legal entity name] (“Presage”, “we”). It explains what we collect about account holders and visitors, what public-records information we process about properties and the people connected to them, and the choices both groups have.

2. Information about account holders

• Account. Name, e-mail address, brokerage or team name, role, and either a salted password hash or a Google sign-in identity. With Google sign-in we receive your name, e-mail and the fact that Google verified it — never your Google password.
• Team settings. County, farm ZIP codes, seats, invitations.
• Your work in the Service. Saved searches, parcel claims, notes, outcome logs, consent records you enter, contacts you enter for your own leads, and the exports you generate.
• Billing. Handled by Stripe. We store Stripe customer and subscription identifiers and your plan status; card numbers never reach our systems.
• Usage and security logs. IP address, browser type, pages and actions, timestamps, sign-in events and failed attempts — kept to operate, measure and secure the Service.

3. Public-records information about properties and owners

3.1 Sources. County tax and parcel records, the Register of Deeds, the Clerk of Superior Court (estates and civil filings), court calendars, municipal code-enforcement records, the North Carolina Secretary of State business registry and comparable public sources. We record the source and the time of capture for every fact.

3.2 What. Parcel identifiers and characteristics, owner names and mailing addresses as recorded, assessed values, tax and bill status, recorded instruments, filings and their dates, and entity officers as registered. We do not buy consumer credit data, and we are not a consumer reporting agency.

3.3 Contact details. The Service does not display telephone numbers drawn from public records. Where a team has entered a telephone number for its own lead, the Service shows it only after a Do-Not-Call scrub no older than 31 days that is clear on the National Do Not Call Registry, the applicable state list and our internal do-not-contact log; texts and e-mails are permitted only with consent recorded in the Service. Numbers are stored as a hash plus the last four digits and never appear in logs, reports or exports.

3.4 Why. To organise public records for licensed real estate professionals, who have a legitimate business interest in identifying properties whose owners may welcome a conversation, and to help them make that contact lawfully and no more often than necessary.

4. How we use information

To provide and secure the Service; to run billing; to answer support requests; to measure, in aggregate, which features are used; and to comply with the law. We do not sell personal information and we do not use it for advertising.

5. How we share information

• Service providers under contract. Cloud hosting and database services, Stripe for payments, Google for sign-in if you choose it, and [e-mail delivery provider, if any, to be named] for account messages. Each processes data only to provide its service to us.
• Your team. Members of your team see the team's claims, notes, outcome logs, activity and roster as described in the Service. No other customer can see your team's data.
• Legal. When required by law, or to protect rights, safety or the Service.
• Business transfers. If we merge, are acquired or sell assets, under this policy.

6. Cookies and local storage

The Service keeps your session token in your browser's local storage so you stay signed in; signing out removes it. We set no advertising or cross-site tracking cookies. [Analytics: none at the date of this draft; update if added.]

7. Retention

Account and team data for as long as the account is active and for [twelve months] afterwards, unless you ask us to delete it sooner or the law requires longer. Outcome logs and claims stay with the team when a member leaves. Security logs for [ninety days]. Public-records data for as long as it serves the Service, with each fact dated.

8. Security

Passwords are stored as salted PBKDF2 hashes; every team's data is isolated by tenant; access requires a signed-in session or an administrative key; connections are encrypted in transit. No system is perfectly secure — tell us at once if you suspect a problem with your account.

9. Your choices and rights

• Account holders. Review and update your profile and farm in the Service; export your team's data with the Service's exports; ask us to delete your account at [contact]. Team owners may remove members.
• Property owners and other people named in public records. You may ask us to suppress your record from display in the Service, to correct a fact against its source, or to add you to our do-not-contact log, at [contact]. We honour do-not-contact requests across every team. We cannot change the public record itself; the office that issued it can.
• Marketing e-mail. We send none; account and billing messages are transactional.
• State privacy laws. Residents of states with privacy statutes may have additional rights — access, deletion, correction, portability, appeal — which we honour to the extent they apply. [Counsel to review applicability given the business-to-business scope and public-records exemptions.]

10. Children

The Service is for licensed professionals and is not directed to anyone under eighteen.

11. Changes

We will post updates with their date and notify team owners of material changes before they take effect.

12. Contact

[Contact e-mail and mailing address — to be set before adoption.]