Resid · Legal

Privacy Policy

Last updated 1 September 2026

Resid ("Resid", "we", "us") is a tool that helps photographers and videographers license their real estate and architectural work. It helps you find who to license to, price it, send outreach, collect payment, and deliver the files. This policy explains what data we handle and why. Questions are welcome at hello@getresid.com.

1Who this covers

Two groups of people appear in Resid:

Creators, meaning the photographers and videographers who sign up and use Resid to run their licensing.
Licensees, the companies and contacts a creator reaches out to and licenses work to, such as architects, builders, and brokers. A creator enters this contact information into Resid to manage their own outreach.

2What we collect

Account data. A creator's email, name, business or studio details, and any profile or logo images they upload.
Licensing data a creator enters. Properties, and the names, companies, roles, email addresses, phone numbers, and contact page addresses of the licensees they choose to contact, along with notes, proposed fees, license records, and a record of which messages the creator sent by hand.
Gmail authorization. If a creator connects Gmail, we store an encrypted refresh token so Resid can send outreach and delivery emails from their own Gmail account, on their behalf. See the Google user data section below.
Payment data. Payments are processed by Stripe. Resid does not store card numbers. We store payment references, amounts, and status to record which licenses were paid.
Pay page activity. When a licensee opens a pay page we record that it was opened and tell the creator, and show the creator that it is being read while the page is open. We record that the page was viewed, not who was at the keyboard.
Usage and technical data. Standard logs from our hosting provider, needed to run and secure the service.

3Google user data (Gmail)

What Resid asks for. When a creator connects Gmail, Resid requests one Gmail permission: the ability to send a message on their behalf (the gmail.send scope), together with their email address. Resid does not read, search, or list their mailbox, does not store its contents, and creates no drafts in it.

What Resid actually receives from Google. Three things, and nothing else: the address of the connected account, the tokens that authorize sending, and, for each message sent, the identifiers Gmail returns for that message. No mailbox content ever reaches Resid, because the only call Resid makes is the one that sends a message a creator has written and approved.

Limited Use. Resid's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. That information is used only to provide the sending feature the creator asked for. It is never sold. It is never used for advertising, ad targeting, or profiling. It is not transferred to anyone except as needed to provide that feature, to comply with the law, or as part of a merger or acquisition where we give prior notice. And no human reads it, except with the creator's explicit consent for a specific message, to investigate a security incident or abuse, or where the law requires it. There is no mailbox content for anyone to read, because none is ever received.

Never used to train a model. Information received from Google APIs is not used to develop, improve, or train any artificial intelligence or machine learning model, ours or anyone else's, and none of it is sent to an AI provider. Resid does use an AI provider to draft outreach wording, and what that provider is given is the creator's own property and company details. Nothing received from Google is included.

Sign in with Google is separate. A creator can sign in to Resid with a Google account. That connection confirms who they are and requests no access to Gmail at all. Connecting Gmail for sending is a second, explicit step.

Keeping it, and deleting it. The refresh token is encrypted at rest. A creator can disconnect Gmail inside Resid at any time, or revoke Resid's access in their Google Account settings. Disconnecting deletes the stored token straight away, along with the stored address. Deleting the account deletes it with the rest of the account's data.

4How we use data

To provide the service: research, pricing, outreach drafting, payments, and delivery.
To send the emails a creator approves, from their connected Gmail.
To draft outreach and quote text. Draft prompts (recipient name, company, role, property) are sent to a third-party AI provider to generate the wording. No payment data is sent, and nothing received from the Gmail API is sent. Draft text written before a message is sent is the creator's own outbound content, not data received from Google.
To operate, secure, support, and improve the service.

We do not sell personal data, and we do not use it for advertising.

Your photographs and films are treated the same way, and more narrowly still: we do not use them in our own marketing, we do not license them to anyone, and we do not train AI models on them. Your imagery reaches an AI provider in one circumstance only, when you use "Scan photos for brands", and then only the photographs you pick for that scan. Everything else we send an AI provider is text, such as a property address or a company name. Your copyright is set out in full in section 3 of the Terms.

5Service providers

We share data only with the providers needed to run Resid, including:

Stripe, for payment processing and payout routing.
A cloud database, authentication, and storage provider that holds account and licensing data.
An AI provider that generates outreach and quote wording.
A hosting provider that runs and delivers the application.

Each provider may only process data as needed to deliver its part of the service.

Google is not on that list, and the difference matters. Resid does not hand a creator's data to Google. Google holds the creator's own mailbox, the creator connects it, and Resid sends through it on their instruction. What comes back is covered in section 3.

6Retention and security

We keep data for as long as an account is active, or as needed to provide the service and meet legal and accounting obligations. Sensitive credentials such as the Gmail refresh token are encrypted at rest. Disconnecting Gmail deletes the stored token and address straight away, and deleting an account deletes them with the rest of its data. No system is perfectly secure, but we take reasonable measures to protect data.

7Your choices

Creators can disconnect Gmail at any time, which revokes Resid's sending access.
Creators can delete a property and everything under it from inside Resid. A property with a paid license cannot be deleted, because the license record has to survive it, and Resid offers to archive it instead.
You may request access to, correction of, or deletion of your personal data by emailing us.
A licensee who wants their contact details removed can contact the creator who added them, or reach us and we will help route the request.

8Changes

We may update this policy as the service evolves. Material changes will be reflected by the "last updated" date above.

9Contact

Questions about this policy or your data: hello@getresid.com.