OfferConsole Privacy Policy
1. Who this covers
This policy explains how Cedar Acquisitions LLC ("Cedar", "we") handles personal information in OfferConsole. It covers:
- Customers and their users: the real-estate investors who subscribe and the people on their seats.
- Contacts in customer data: mainly listing agents (licensed real-estate agents contacted as business contacts) whose names and work emails appear in lists customers upload, and anyone who writes to a customer's connected inbox.
For contacts in customer data, the customer decides whom to contact and why; Cedar processes that information on the customer's behalf. [ATTORNEY: confirm the controller / service-provider framing.]
2. What we collect
From customers and users
- Account details: name, work email, company name, postal address (it goes into every email), and team members' names and emails.
- Billing: handled by Stripe. We receive your plan and payment status; card numbers are entered with Stripe and we do not store them. [ENGINEERING: confirm which card details, if any, we keep.]
- Usage and technical data: log-ins, actions in the app, and error logs. [ENGINEERING: confirm whether IP addresses or browser details are logged, and where.]
Customer data (uploaded or produced through the service)
- Property lists you upload (for example PropStream, Propwire or DealMachine exports): addresses, listing details and listing agents' names, emails, phone numbers and brokerages.
- Offers drafted and sent, follow-ups, and the replies and other mail described in section 3.
- Screening results, reply rankings and deal summaries.
3. Gmail data
Customers connect their own Google Workspace inboxes. Their Workspace administrator authorises our service account with domain-wide delegation. OfferConsole requests Gmail scopes to send mail, read mail and modify mail (gmail.send, gmail.readonly, gmail.modify) for the inboxes the customer connects, and no others.
What we do with that access:
- Send the offers and follow-ups the customer has approved.
- Read incoming mail in connected inboxes to find replies to those offers, bounces, auto-replies and opt-out requests, and messages from real people that relate to an offer but arrive outside the original thread (for example an agent's colleague writing fresh). We store those messages and pass them to the customer's team inside OfferConsole.
- Label or mark mail as needed to keep track of what has been handled. [ENGINEERING: confirm exactly what gmail.modify is used for.]
Limits on our use of Gmail data:
- We use Gmail data only to provide and improve these user-facing features for the customer that connected the inbox.
- We do not sell Gmail data, use it for advertising, or use it to build profiles for anyone else.
- People at Cedar do not read it, except with the customer's permission, for security, or where the law requires. [OWNER: confirm this matches practice, including support and platform admin work.]
- We do not use it to train general-purpose AI models.
OfferConsole's use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. [ATTORNEY: see open questions.]
4. How we use information
- To run OfferConsole: screen homes, draft, send and track offers, read and rank replies, deal summaries.
- To enforce safety rules: daily caps, inbox ramp, bounce pauses, opt-outs, and abuse review.
- To bill customers and manage subscriptions.
- To send system alert emails (for example, an inbox stopped sending).
- To support customers, secure the service, fix problems, and meet legal obligations.
We do not sell personal information, and we do not share it for cross-context behavioural advertising.
5. Each company's data stays separate
Each company's data is isolated from every other company's. The only signal that crosses companies is an anonymous count shown for a home already on a customer's own list: "N other members offered on this home in the last 30 days". It never says who offered, at what price, or in what words.
6. Who we share with
We use these service providers to run OfferConsole:
| Provider | What it does for us | Data location |
|---|---|---|
| Cloudflare | Runs the application (Workers) | [PLACEHOLDER: Cloudflare region/terms] |
| Supabase | Database, sign-in and file storage | United States (AWS us-west-2) |
| Stripe | Subscriptions and payments | [PLACEHOLDER] |
| Resend | System alert emails only (not offers) | [PLACEHOLDER] |
| Gmail API, for the inboxes the customer connects | Customer's own Google Workspace |
We may also disclose information if the law requires it, to protect rights and safety, or as part of a sale or reorganisation of our business, subject to this policy.
Possible future provider. We may add an AI reply assistant using Anthropic's API. It would only draft replies; a person would approve every message before it is sent. We will update this policy and notify customers before it is used. [ATTORNEY: whether notice is enough or opt-in consent is needed, given Gmail data would be sent to it.]
7. Opt-outs from offer emails
Every offer email carries the customer's postal address and an opt-out line. When a recipient opts out, OfferConsole stops all further offer emails to that address from every inbox of that customer, permanently. Recipients may also contact us through our contact form (offerconsole.com/contact) and we will pass the request to the customer concerned.
8. How long we keep information
[OWNER: retention periods for account data, customer data, Gmail messages, logs, and backups, and what happens after cancellation.] Opt-out records are kept as long as needed to keep honouring them.
9. Security
Each company's data is separated at the database level (row-level security), and connections use encryption in transit. [PLACEHOLDER: other security measures, for example encryption at rest and who at Cedar can access production data.] No system is perfectly secure. [PLACEHOLDER: breach-notification commitment.]
10. Your choices and rights
- Customers can disconnect inboxes at any time by removing the authorisation in Google Admin. [OWNER: how customers export or delete their data.]
- Depending on your state, you may have rights to know, access, correct or delete personal information, and to appeal a decision. Contact us through our contact form. We will not discriminate against you for using these rights. If your information is in a customer's data, we may refer you to that customer.
- [ATTORNEY: which state privacy laws apply, given the business-contact data and Cedar's size.]
11. Children
OfferConsole is a business service and is not directed to anyone under 18.
12. Changes
We will post changes here and notify customers of material changes before they take effect.
13. Contact
Cedar Acquisitions LLC, a Florida limited liability company, 2423 SW 147th Ave #693, Miami, FL 33185. Privacy questions: use our contact form. Phone: 754-260-7289.
Open questions for the attorney
- Notice address: settled by the owner on 23 Oct 2026 as 2423 SW 147th Ave #693, Miami, FL 33185. Also: the effective date (set on launch day).
- Controller / service-provider roles for listing-agent data, and whether a data processing addendum is offered to customers.
- Google API Services User Data Policy and Limited Use: gmail.readonly and gmail.modify are restricted scopes. Confirm whether Google OAuth verification and an annual security assessment (CASA) apply when access is through domain-wide delegation by a Workspace admin rather than consumer OAuth, and whether the Limited Use statement must also appear on the homepage.
- Section 3 describes reading all incoming mail in connected inboxes, not only replies in offer threads (the product records person-to-person messages outside offer threads and forwards them to the team). Confirm this is disclosed clearly enough, and that customers should be told to connect dedicated sending inboxes rather than personal ones.
- Exactly what gmail.modify is used for (engineering to confirm).
- Retention periods, deletion after cancellation, backups, and breach-notification commitment.
- Data locations for Cloudflare, Stripe and Resend.
- Which state privacy laws (for example California CCPA/CPRA) apply, and whether a "Notice at Collection" or a "Do not sell or share" link is needed.
- The future Anthropic AI reply assistant: notice versus opt-in, and Limited Use implications of sending Gmail content to a third-party AI provider.
- Whether the cross-company overlap count (and same-day spacing of members' offers on one home) needs any further disclosure.