← Back

Privacy Policy

Last updated: August 11, 2026

1. Information We Collect

Your account. Your email address, and a display name if you give one. If you register with a password we store a hash of it, never the password itself. If you sign in with Google or Apple we store the account identifier that provider gives us and any name or profile picture it passes along.

Your log. The properties you add (a name and street address, and a photo if you upload one) and every entry you file against them: what happened, when, the amount, the contractor’s name, mileage, your free-text description, the tax category, any recurring reminder cadence, and a receipt or photo if you attach one. Also the contractors you save — name, trade, phone, email, and your notes.

Your mortgage terms. If you choose to add the mortgage on a property, we store what you enter about the loan: the lender’s name, the amount borrowed, the interest rate, the term, the month of the first payment, and a monthly payment if you set one. We use it only to work out what that unit costs you and show it back to you. We never contact your lender, and we do not ask for or store an account number.

What a property cost you. If you record a purchase, we store the price, the month it completed, the down payment and any closing costs you enter. It is used to work out that unit’s return and shown only back to you.

Your own valuation. If you tell us what you reckon a property is worth, we store that amount and the month you say it was true. It is your estimate, not ours — we do not price properties, do not send it anywhere, and use it only to show you your equity and returns.

Your to-do list. The work you record as still needing doing: what it is, any notes you add, which property it belongs to, the date you aimed at, the cost you expect, and when you marked it done. An estimated cost is a plan, not a payment — it never reaches the tax export.

Tenants and their requests. If you invite a tenant to a property, we store the email address you invite, the name you give them, which property it is for, and the invitation link’s secret token. If they accept, we store the link between their account and that property. Every work request they file — what is wrong, how urgent they said it is, any photo, the status you set and any visit date — and every message either of you writes on it are stored and shown to both of you. We email the invitation to the address you enter — it names you, the property, and the link — and we also show you the link so you can pass it on yourself. Nothing else about a request is emailed: once a tenant has an account, both of you are told about new requests, replies and status changes inside Transom (the bell, and a push if you use an iOS app), never by email.

If you are a tenant using the portal. You see only your own requests and the messages on them. You cannot see your landlord’s log, their finances, their other properties, or anyone else’s requests. Deleting your account erases your name, your email and the tenancy itself; the requests you filed remain on the property’s maintenance record with no name, email or account attached, because that repair history belongs to the property owner. One thing to know about your messages: when your landlord opens a request that is waiting on their reply, its description and the messages on its thread are sent to our AI provider (§4) so it can draft replies for them to consider. Your landlord chooses what to send you and sends it themselves — nothing written by the assistant reaches you unless they send it.

Your conversations with the assistant. Chat and voice conversations are saved to your account so you can come back to them, and are deleted with it. We also record one row per AI request — which feature, how many tokens, what it cost us — to keep the service running and within budget.

Preferences and usage. Your language, timezone, theme, and settings; how far you got in the welcome walkthrough; any feedback you send us; and, if you enable notifications, the device or browser push token needed to deliver them. A token identifies one device and is tied to whichever account is signed in on it; signing out releases it.

Your plan. If you subscribe, we store which plan you are on, the state your subscription is in, and the customer and subscription identifiers Stripe gives us. Your card number and billing address go to Stripe, not to us — we never receive them. Deleting your account cancels the subscription and removes these along with everything else.

Abuse prevention. Sign-in, registration, password-reset and API requests are counted per account and per IP address for short windows to stop brute-force guessing and runaway usage. Those counters are disposable, expire on their own, and are not linked to your log.

2. How We Use It

To run the app: to show your log back to you, to compute the views built from it — the profitability dashboard, the reminders, the “worth logging” nudges, the to-do list, the contractor directory, the tax export — to carry work requests and messages between a landlord and their tenant, to answer your questions through the assistant, and to send you the account email described below.

We do not sell your information and we do not share your log with advertisers. We do measure whether our own ads lead to sign-ups, as §4 and §5 describe, but that never involves your properties, entries, or anything else you have logged.

3. Who Can See Your Log

Only you. Transom is single-owner: every property, entry, to-do, contractor, and dismissal belongs to one account, and every read and write is scoped to the signed-in user. There is no way to invite a co-owner or a property manager into your log today, and no shared view.

An administrator of this deployment can see account-level operational data — email addresses, sign-up dates, whether an address is verified, aggregate usage counts, and when an account was last active — to keep the service running. That view carries counts and timestamps; it does not show the contents of your entries.

4. Third-Party Services

Transom sends data to the following services. Several are marked optional: those receive nothing unless that feature is configured on this deployment.

  • Vercel — hosts the application and serves every request, so it processes the traffic between your device and us. Vercel Analytics also records basic, privacy-friendly page-view metrics.
  • Neon — the managed Postgres database your account and log are stored in.
  • Upstash (Redis) — holds short-lived rate-limit counters and cached computations, keyed by your account id or IP address. Optional — without it, rate limiting and caching are simply skipped.
  • Anthropic, via the Vercel AI Gateway — powers the assistant. When you send it a message, your message and the relevant slice of your log — property names and addresses, entries with their dates, amounts, contractors, descriptions and categories, your outstanding to-dos, upcoming servicing, and the year’s totals — are sent so it can answer. It also drafts suggested replies on a tenant work request that is waiting on you: when you open such a request, that one request and the messages on its thread — including your tenant’s own words and their display name — are sent so the drafts can be written. Nothing else about your account goes with them; your log, your finances and your other properties are not included in that request. Your email address and password are never sent. Optional — with AI switched off, the assistant is unavailable and nothing is sent.
  • OpenAI — powers voice mode. When you start a voice conversation, your audio and the same picture of your log described above are processed in real time. Voice is read-only: it can answer, but it cannot write to your log. Optional.
  • Resend — delivers account email: address-verification and password-reset links, and tenant portal invitations. Receives the recipient’s email address and the message. For an invitation that recipient is the person you invited, and the message names you and the property.
  • Address lookup — Google Places or Photon — when you type a property’s address, what you have typed so far is sent to an address-suggestion service so it can offer completions. This deployment uses Google Places if it has been given a key and Komoot’s Photon (an OpenStreetMap index) if it has not, so one of the two always receives it. Only the characters in that one box are sent — never your account, your other properties, or anything else in your log — and the request goes through our server, so the service never sees your browser or your IP address.
  • Vercel Blob — stores the receipt and property photos you upload. Uploaded files are served from a public, unguessable URL; anyone holding that URL can view the file, so treat an uploaded receipt as shareable-if-leaked rather than private-forever. Optional — when it isn’t configured, uploads are stored in the database above instead and served only to you while you’re signed in, so no third party receives them. Either way, you can paste a link you host yourself instead.
  • Google and Apple — only if you choose to sign in with one of them. They tell us the account identifier, your email address, and sometimes your name; we tell them nothing about your log. Apple’s Push Notification service also delivers notifications to your iPhone if you turn them on, and receives your device token and the notification’s text. Optional — each is offered only when this deployment has been configured for it.
  • Meta (Facebook) and Reddit — for measuring whether our ads lead to sign-ups. When configured, their pixels load on our public pages and a sign-up is reported to their Conversions APIs. Any email address (and, for Reddit, IP) is hashed irreversibly with SHA-256 before it leaves our servers, and we never send them your properties, entries, or any other account content. Optional — absent a configured pixel id, no tracker is loaded at all.
  • Stripe — takes the payment if you subscribe to Pro, and is the only party that sees your card: it goes straight to Stripe’s own checkout page and never touches our servers. Stripe receives your email address, your name if you have set one, and whatever billing details you give it; we keep only its customer and subscription identifiers and your plan. Nothing from your log is ever sent. Optional — a deployment without Stripe keys has no paid plan at all, and Stripe receives nothing.

That is the complete list. Transom has no in-app-purchase provider — there is no iOS app and no App Store billing, so nothing about you reaches Apple or RevenueCat.

5. Cookies and Analytics

We use essential cookies for authentication, language, and theme preferences. We use Vercel Analytics for basic, privacy-friendly usage metrics, and we record first-party usage events — such as walkthrough progress and AI usage — in our own database to operate and improve the app. There is no third-party session recording and no advertising profile built from your log.

Where the ad-measurement pixels in §4 are configured, they may set cookies. If you visit from the EEA or the UK they stay disabled until you opt in through our cookie banner, and you can decline them entirely.

6. Storage and Security

Data is stored in the managed Postgres database above and travels over encrypted connections. Passwords are stored as salted hashes. No system is perfect and we won’t claim otherwise — but access to your log is enforced in the queries themselves, not merely hidden in the interface: every read and write is filtered by your account id.

On your device (offline mode): so the app keeps working without a connection, it stores some data locally on your device — recently viewed pages, and any change you make while offline. A change made offline is held on your device and sent to us (then cleared) the next time you’re online. Each pending change is tied to the account that made it, so signing out with changes still waiting will not move them into someone else’s account. This on-device data lives only in your browser or app.

7. Your Rights and Choices

Export. The Export page gives you your whole log as CSV, per year, at any time. It covers the log — what happened and what it cost. Your to-do list is work that hasn’t happened yet, so it isn’t part of the export; ask us if you want a copy of it.

Deletion. Settings → Delete account erases your account and everything filed under it — properties, entries, to-dos, contractors, chat history, preferences. It is immediate and cannot be undone, so export first if you want a copy. Photos held in the database go with it; files stored in blob storage are the one thing to ask us about separately. If you ever subscribed, deletion also cancels the subscription and deletes the customer record Stripe holds for you — your email and billing history — so nothing about you is left with them either.

Access and correction. You can see and correct the personal data we hold about you from Settings; write to us for anything the interface doesn’t cover.

8. Data About Other People

Your log will often name a contractor, and sometimes a tenant, in a description. You are the one deciding to record that, and you remain responsible for handling it lawfully — particularly if you are somewhere with rules about tenant records. Transom stores what you write and shows it only to you.

9. Children

Transom is a tool for adults managing rental property. It is not directed at children and we do not knowingly collect information from them.

10. Changes to This Policy

When what we collect or who we share it with changes, this page changes with it and the “Last updated” date above moves. Material changes are announced in What’s New rather than slipped in quietly.

11. Contact

If you have questions about this policy, contact us at cody@layer3d.io.

Terms of Service