RaeSource
Privacy Policy
Last updated 4 October 2026 · RaeTech LLC
RaeSource is a business-to-business service operated by RaeTech LLC (“we”). It turns published building-permit records into timed sales leads for contractors and suppliers, and gives them tools to run the jobs they win: budgets, estimates, schedules, plans and documents. This policy explains what we collect, why, and what you can ask us to do about it.
We do not sell personal information, we do not serve advertising, and we do not use third-party tracking or analytics in the RaeSource app.
1. Two kinds of information
It matters which is which, so we keep them separate throughout this policy.
a. Information about you, our customer
| What | Why |
|---|---|
| Work email address | To identify your seat and let you sign in |
| Name and role | So your colleagues can see who logged a call |
| Password (stored only as a cryptographic hash) or, if you use Google sign-in, your Google account identifier | To authenticate you |
| Company, trade, territory and billing status | To decide which leads your seat is entitled to |
| What you record against a lead — notes, stage, contact details you capture, follow-up dates, bid values | To provide the service, and to share it with the other seats at your company. Your follow-up dates are the exception: they are visible only to you and your company’s account owner |
| Your jobs — the clients you add, budgets, estimates, schedules, uploaded plans and documents | To provide the service. Plans are read by your company’s own AI service only when someone at your company uses Build estimate (section 4) |
b. Information about third parties, from public records
The leads themselves come from building permits published as open data by the City of Austin and other Texas jurisdictions. A permit record names the contractor or company that pulled it and, commonly, a business telephone number and the job address. That information is published by the issuing authority as a public record; we compile, classify and time it, we do not create it.
We do not knowingly collect residential contact details of private individuals, and we exclude jurisdictions whose feeds expose personal data such as applicant email addresses or tax identifiers.
2. Job data we use to improve RaeSource
When your company builds a budget from plans or creates an estimate from a budget, we keep a copy of that budget’s line items for RaeTech’s own use in improving the service.
- What it holds: the job type, metro area and ZIP code, and each line’s description, quantity, unit, cost, price and markup, alongside what Build estimate first drafted for it.
- What it leaves out: your client’s name, contact details and job address, and the names of the people at your company.
- What we use it for: making plan reading more accurate, and improving our estimating guides — quantities, waste, and the hours each kind of work takes. We may use it to train RaeTech’s own models for those purposes.
- What we never do with it: show it to another customer, sell it, or use your prices to set or suggest prices for any other company.
- Who can read it: no one at any customer company, including yours. The database accepts these copies from the app and returns them only to RaeTech’s own systems.
If you would rather your company’s job data not be used this way, write to support@goraetech.com and we will exclude it and delete what we hold.
3. If you are a contractor named in a permit
You did not sign up for RaeSource, and you may be reading this because somebody contacted you using it. Two things you can ask for:
- Tell the company that called you. If you ask a RaeSource customer not to contact you again, that request is recorded against that company and their software will stop showing them your permits. It does not travel to other companies, and it should not: a request not to be called applies to the business that called you, not to every unrelated contractor who happens to use the same software we do.
- Ask us to take your details out. Write to support@goraetech.com and we will remove your contact details from RaeSource, so they stop being distributed to any customer at all. That is the request that applies everywhere, and it is a stronger one than a single do-not-call.
- Correction. If we hold something inaccurate about your business, tell us and we will correct or remove it.
We also keep our own do-not-contact list for the companies we approach about buying RaeSource. That one is separate, and asking us to stop does stop us everywhere.
We cannot remove the underlying permit record — that belongs to the issuing authority, and you would need to approach them directly.
4. Where your data lives
| Provider | Purpose | Location |
|---|---|---|
| Supabase (on Amazon Web Services) | Database and authentication | United States — US East (N. Virginia) |
| Netlify | Serving the application itself. No customer data is stored there. | United States |
| Stripe | Subscription billing | United States |
| Optional “Continue with Google” sign-in | United States |
These are our only subprocessors. We will update this list before adding another.
The AI service your company connects. Build estimate reads plan sheets with an AI service your company chooses and connects under its own account (Anthropic, OpenAI, Google or OpenRouter). When someone at your company uses it, the sheet images and the text printed on them are sent to that service, and your company pays for that use. Your company’s agreement with that service governs what it does with them. Nothing is sent until your company connects a service and its owner allows it.
5. Payments
Card and bank details are collected and held by Stripe, which is certified to PCI DSS Level 1. We never see, receive or store your card number or bank account number. We see only whether a subscription is paid.
6. Security
- Inside your company, a job, its budget, estimates, schedule and files can be seen by everyone at the company but changed only by the account owner, the person who started the job, and teammates they give edit access. Every change is recorded with the name of the person who made it.
- Traffic is encrypted in transit (TLS) and data is encrypted at rest by our infrastructure providers.
- Every table enforces row-level security keyed to your company. It is not that we choose not to show you another customer’s leads — the database will not return them.
- We do not store passwords. Authentication is handled by Supabase, which stores a one-way hash.
- Administrative credentials are held outside the application and are never shipped to a browser.
What we do not claim. RaeTech LLC does not currently hold a SOC 2 or ISO 27001 attestation. Our infrastructure providers maintain their own certifications, which cover their platforms and not our company. We would rather say that plainly than let the distinction blur.
7. How long we keep things
- Your account and the work you record — for as long as your company has an active seat, and for 90 days afterwards so that a lapsed account can be restored intact. After that we delete it. That deletion is carried out by hand on review today, not by a scheduled job.
- Lead records — refreshed continuously; older permits age out.
- Job data copies (section 2) — kept while your company’s account exists, and deleted when the account is deleted.
- Do-not-contact requests — kept for five years, because the only way to honour a suppression request is to remember it.
- Billing records — kept as required by tax and accounting law.
8. Your choices
Write to support@goraetech.com to access, correct, export or delete information we hold about you. We will respond within 30 days. If your company holds the account, we may need to confirm the request with its owner before deleting shared work such as call history.
9. Children
RaeSource is a tool sold to businesses. It is not directed at anyone under 18 and we do not knowingly collect information from children.
10. Changes
If we change this policy in a way that materially affects you, we will email the address on your account before it takes effect.
11. Contact
RaeTech LLC
support@goraetech.com