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, and email
addresses of the licensees they choose to contact, along with notes, proposed fees, and license
records.
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.
Usage and technical data. Standard logs from our hosting provider, needed to run and
secure the service.
3Google user data (Gmail)
Limited scope. When a creator connects Gmail, Resid requests only the ability to
send email on their behalf (the gmail.send scope) plus their email address.
Resid does not read, search, or store the contents of their mailbox.
Limited Use. Resid's use of information received from Google APIs will adhere to the
Google
API Services User Data Policy, including the Limited Use requirements. Gmail access is used
solely to send the messages a creator explicitly approves. It is never used for advertising, is
never sold, and is not shared with third parties except as needed to provide this feature.
The refresh token is encrypted at rest and can be revoked at any time by the creator, in Resid
or in their Google Account settings.
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 or Gmail contents are
sent.
To operate, secure, support, and improve the service.
We do not sell personal data, and we do not use it for advertising.
5Service providers
We share data only with the providers needed to run Resid, including:
Stripe, for payment processing and payout routing.
Google's Gmail API, for sending email on a creator's behalf.
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.
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. 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.
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.