Privacy and your deeds

You are handing us documents that describe land somebody is deciding whether to buy. This page says exactly what happens to them, in plain language, because a general-purpose privacy policy would not answer the question you actually have.

What we collect

The text you send us. Legal descriptions, deed text, CSV batches, and any survey references or notes you add. This is the substance of the service — there is no way to draft a tract without it.

Contact details. We require an email address before running a free draft, and collect name and email when you contact us, purchase a tract or start a subscription. We use the address to enforce the trial limit, connect a later subscription to the draft, provide the service, and follow up about TractEdge.

Ordinary server logs. Request paths, timestamps, IP address and error traces, kept for operating and debugging the service. We do not run advertising trackers, analytics pixels or third-party cookies on this site.

Where your description goes

To draft a tract, the text has to travel:

• Anthropic’s API reads the description and transcribes it into structured survey calls. Anthropic does not train its models on data submitted through its API.
• The Texas Railroad Commission’s public GIS service is queried for the survey abstract your deed references, and for wells near the tract. These are lookups against public geometry — we send a survey reference or a bounding box, never your deed text.
• The BLM CadNSDI PLSS service, the same way, for New Mexico section and aliquot descriptions.
• Our own infrastructure — application hosting and the database the drafts live in.
• Resend stores contact email addresses and sends service and marketing email. We mark contacts as trial users or purchasers so follow-up reflects their relationship with TractEdge. Every marketing email includes an unsubscribe link.

That is the complete list. Your descriptions are not sold, not published, and not given to data brokers, list vendors or anyone in the business of buying minerals. Who can see them inside TractEdge is covered below.

Training

Your documents are not used to train any machine-learning model — not ours, not anyone else’s. We do read submitted descriptions ourselves to understand the document formats we need to handle, and we may use anonymised structural characteristics (say, that a particular county’s deeds tend to split a closing call in two) to improve how the software reads them. If you would rather we didn’t look at yours at all, say so when you send it and we won’t.

How long we keep it

• Descriptions you send us by email: kept while we work on them and for up to 12 months afterwards, so we can pick the conversation back up. Ask and they go sooner.
• Free-trial projects: kept in the private anonymous browser session that created them. If that session later starts a subscription, the projects become part of the customer account; otherwise they are proof-of-concept work and are not available through a reusable login.
• Projects in an account: kept as long as the customer login remains available. Subscription drafting and export access end with the paid term; we do not promise an automatic deletion date, and you can ask us to delete projects at any time.
• Server logs: 30 days.

Deletion, and its limits.Email us and we remove the document, the draft, the exported geometry and the database rows behind them — every copy under our control — and we confirm when it’s done. Our backups roll over within 30 days. What we cannot do is reach into Anthropic’s systems: text already sent there for reading ages out under the retention terms of our API account rather than on our say-so.

Who can see it

TractEdge is a small operation, and the person who builds it can read the database. There is no support team, no offshore contractor and no sales operation with a login.

Your projects belong to your private identity. A free draft is tied to an anonymous browser identity, not a reusable account login. Starting a subscription lets you attach sign-in to that same identity, so the draft follows into the customer account. Every request is checked against ownership before anything is returned. Another customer cannot list, open or export your projects, and an automated test suite asserts that scoping endpoint by endpoint. Accounts are individual for now: there are no organisation accounts yet, so a plan is one login rather than a team workspace.

If a document is sensitive enough that operator access matters, tell us and we will handle it outside the system instead of asking you to take it on trust.

Security

Traffic is encrypted in transit, and projects are scoped to the account that created them, as described above. We are not going to claim certifications we do not have: there is no SOC 2 report, no penetration test on file and no security questionnaire we can complete truthfully today. If your firm needs those, we would rather you knew now.

Your choices

• Ask for a copy of everything we hold about you.
• Ask us to correct it.
• Ask us to delete it, including documents you sent us.
• Ask us not to read a submitted document beyond drafting it.
• Unsubscribe from marketing email using the link in any message. Transactional messages needed to provide a purchase or account may still be sent.

One email does any of these: thomas@thomasdulin.com. No form, no ticket.

Changes

If this page changes in a way that affects documents you have already sent us, we will email you rather than quietly update the date at the top.

Contact

thomas@thomasdulin.com. See also the terms of service.