Privacy policy
Effective 2026-09-14
1. Who we are and how to reach us
ReedPort is made by North Trestle LLC, 116 Agnes Rd Ste 200, Knoxville, TN 37919. For anything about this policy, email privacy@reedport.com. We announce material changes by email to shop admins and by updating this page.
2. Two kinds of data
There are two roles we play. For your own account — your login email, your name, your shop's billing status — we decide why and how that data is used, so we are the controller. For your shop's records about your customers, we act only on your instructions to run your counter, so we are a processor (or "service provider" in California's terms) and your shop is the controller.
3. On this website (reedport.com)
This site counts page views, which parts of the page were seen, Start clicks, how far down the page you got, and how long the page was open. With each count we record the page path, the site you came from, the country and device type Cloudflare reports, and whether the request looks like a bot. The count runs on Cloudflare and is stored by us. It keeps no name, email, or IP address, and it sets no cookie of its own. Cloudflare Web Analytics also measures how fast the page loads, without cookies. No ads pixel.
Two first-party cookies are set on reedport.com. If you arrive from a link with a campaign tag, rp_attr keeps that tag, the site you came from, and the page you landed on, for 90 days, so we know which link brought you. rp_var records which layout of a page you were shown. Neither holds a name, an email, or an ID for you. Site counts are kept for three months.
We do not track you across other companies' sites, so there is nothing for a Do Not Track signal to turn off. If your browser sends the Global Privacy Control signal, we honor it the same way we always operate: we do not sell or share your information with anyone, signal or no signal.
4. In the app (app.reedport.com)
Creating a shop collects your name, email, a password (stored as a hash, never in plain text), your role, and your shop's name. If the rp_attr cookie is set when you sign up, we send its contents with the signup so we can tell which link brought you. Stripe handles billing; we see the last four digits of your card and its status, never the full card number. We keep usage and security logs and any support email you send us.
The same counts described above run on the signup and email-verification pages, so we can see where signups stall. They record the step, not what you typed. Nothing else in the app is counted this way.
When you drop a vendor packing slip or invoice on the Receive page, or paste one in, we send that document to Anthropic, which reads it and returns the part lines. The document and the lines are then stored with your shop's records. Under Anthropic's commercial terms it does not train models on that content. If you do not want a document to leave our systems, type the lines in by hand instead.
5. Your shop's records
Your customers, their equipment, your work orders, invoices, products, and work-order photos are used only to run your counter. Access inside your shop follows the roles you set; shop-wide totals sit behind your Profit PIN. You can email us for an export of your records at any time. See Security for who else can see them and when.
6. Subprocessors
These companies run part of the service for us, each under a contract that limits them to that job:
| Vendor | What it does | DPA |
|---|---|---|
| Cloudflare | network, marketing site hosting, email routing, site and app counts | View |
| DigitalOcean | servers that run the app, and object storage for shop work-order photos | View |
| Neon (a Databricks company) | database, AWS US East 1 (Northern Virginia) | View |
| Stripe | payments | View |
| Postmark | transactional email | View |
| Anthropic | reads a receiving document you hand to the Receive page | View |
See the full subprocessors page for regions and our 30-day change notice.
7. Sharing
We share data only with the subprocessors above, when the law requires it, or as part of a business transfer (with notice to you). We do not sell your data, and we do not sell your shop's customer records, ever.
8. Security
See our security page for the details. If we learn of an incident affecting your data, we will notify you without undue delay.
9. Retention
| Data | Kept for |
|---|---|
| Site and app counts (page views, sections seen, Start clicks, signup steps) | 3 months |
| Attribution cookie (rp_attr) and layout cookie (rp_var) | 90 days |
| Your account data (login email, billing status) | While your account is open, then 90 days |
| Your shop's customer, equipment, ticket, and work-order photo records | While your subscription is active, then 90 days after the last day you paid for |
| Receiving documents you upload to the Receive page | With your shop's records, on the same schedule |
| Backups of the above | Rolled off on the same schedule as our hosted database's restore window |
10. Your choices and rights
You can ask us to access, correct, export, or delete your account data at any time by emailing privacy@reedport.com. If you are one of our customer's customers and want something changed in a shop's records, ask the shop directly; we forward requests we receive to the shop that holds the record. We do not sell or share personal information as those terms are defined under California law.
11. Children
ReedPort is not intended for anyone under 18, and we do not knowingly collect data from children under 13.
12. United States only
ReedPort is offered to businesses in the United States. Your shop's records and your account are stored in the United States. The site counts in section 3 run on Cloudflare's network, which is worldwide.
13. Changes and contact
We will post material changes here and email shop admins when they happen. Questions: privacy@reedport.com.
Counsel review is in progress; the policy above is the one in force.