Privacy

Guaranteed TC provides transaction coordination to California real estate brokerages. This explains what we hold, why, and what you can do about it. It covers the application at this domain and the coordination service that runs on it.

Who the data belongs to

A brokerage is our customer. The people whose information passes through a transaction, meaning buyers, sellers, agents and escrow officers, are the brokerage’s clients and contacts rather than ours. We hold their information to do the coordination work the brokerage engaged us for, and for no other purpose. We do not sell it, we do not use it for advertising, and we do not use it to train anything.

What we hold

• Account and login. Name, email address and a password hash for everyone who signs in. Authentication is handled by Supabase; we never see a password.
• Transaction records. Property address, contract dates and terms, transaction stage, the compliance checklist and its progress, tasks and their deadlines.
• People on a file. Names, email addresses and phone numbers for clients, agents, and escrow, as entered by the brokerage.
• Correspondence records. Who we emailed about a file, when, which template, and the subject. We keep this because the guarantee depends on being able to show that a request was made.
• Document references. Filenames and Google Drive file identifiers. Not the documents themselves. See below.
• Billing. Invoice amounts, status, and payment dates. Card and bank details are never sent to us; payments go through escrow or PayPal.

Google Drive, specifically

Transaction documents live in the brokerage’s own Google Drive, under the brokerage’s own Google account. We do not host a document store.

• We request the drive.file scope and no other Drive scope. That permission lets an application see and manage only the files it created itself. We cannot list, open, search or download anything else in your Drive, and that limit is enforced by Google rather than promised by us.
• We create a folder structure for each transaction and place documents into it. Those files are owned by the brokerage’s Google account from the moment they exist.
• Our database stores the Google identifier for each file so we know where it went. It does not store the file.
• The access token that lets us do this is encrypted at rest with AES-256-GCM before it reaches our database.
• You can revoke our access at any time, from your Google account or from the settings page here. Our access ends immediately. Your documents are unaffected, because they were always yours.
• Google user data obtained through these scopes is used only to provide the coordination features described here. It is not transferred to anyone except the processors listed below, not used for advertising, and not used to train any model.

Who else touches it

Four processors, each for one job, none of whom receive data for their own purposes:

• Supabase for the database and authentication.
• Vercel for application hosting.
• Resend for sending email on our behalf.
• Postmark for receiving documents emailed to a transaction address.

Payments are processed by PayPal or handled through the escrow company. We do not receive or store card or bank details.

How long we keep it

California requires brokerages to retain transaction records for three years. We keep coordination records for the life of the engagement and for three years after a file closes, so the brokerage can meet that obligation. After that they may be deleted. Documents in your Drive are governed by your own retention, not ours.

Your rights

California residents have the right to know what personal information is held, to have it deleted, to correct it, and not to be discriminated against for asking. If you are a client of a brokerage we work with, ask the brokerage first. They are the controller of that information and can act faster. You can also write to us directly at the address below and we will respond within 45 days.

We do not sell personal information and we do not share it for cross-context behavioural advertising, as those terms are defined by the CCPA.

Security

Access is enforced at the database with row-level security, so a brokerage can only read its own files and an agent only the files they are on. Refresh tokens are encrypted at rest. Portal links for clients are unguessable and can be revoked. We do not hold a key that bypasses these rules.

Changes

If we change this materially we will say so here and date it. The date at the top is when this version took effect.

Contact

hello@guaranteedtc.com. Guaranteed TC, California, United States.