Marlow CRM Intake - Privacy Policy
Effective date: November 5, 2026
Marlow CRM Intake is a private tool used only by Marlow Singh on his own Windows computer. This policy explains what it does with information from Google. About the app: Marlow CRM Intake.
What the app receives from Google
- Sign-in: the name and email address of the one Google account allowed to open the app. These are used only to confirm that account.
- Calendar (optional, read-only): when marlow@property.ca is connected, Google sends the app the events on that calendar, including titles, locations, times, status and descriptions. The app filters these for showing appointments (titled "Showing - {client name}") and stores only selected details of those showings.
What the app stores on the computer
- For each showing: the booking name from the title; the property or unit as written in the location (up to 200 characters); start and end times; the booking status, taken from the first "Status:" line of the description; Google's calendar ID, event ID and, for a recurring event, its series ID; and Google's status for the event and when it was last updated.
- Client links Marlow approves: the CRM contact and opportunity a booking name belongs to (IDs and names), and that opportunity's Showing Count when it was linked.
- Working files: reports, review summaries and an activity log, which can contain booking names, properties and dates. Also the sign-in session.
Not stored: event descriptions beyond the Status line, including lockbox codes, access instructions and notes; and events that are not showings.
How it is used
Only to track Marlow's showings and maintain his own client records. It is not used for advertising and is not sold.
Information shared with other services
Selected information goes to these services:
- Google: requests to sign in and to read the calendar.
- GoHighLevel (Marlow's CRM): when Marlow looks up a client, the booking name is sent as a search; contact and opportunity details are read; contact and opportunity changes he approves are written. After Marlow approves a client link and enables showing automation, a daily task updates only the Showing Count field on the linked opportunity. Historical backfills require separate approval. Showing records and write records are used to prevent duplicate counting and to reverse only this automation's contributions.
- Claude (Anthropic): Marlow operates the app through the Claude assistant. Reports and summaries he asks for, which can include booking names, properties and dates, are sent to Claude. They are handled under Anthropic's terms and his Claude account settings.
How information is protected
- The Calendar access Google issues is stored encrypted with Windows Data Protection, tied to Marlow's Windows user account. It is not stored in readable form.
- The app's records are kept in Marlow's Windows user profile.
- These measures reduce risk but cannot rule it out.
Disconnecting and deleting
- Disconnect: "Disconnect Calendar" in the app deletes the stored access from the computer and asks Google to revoke it. Access can also be removed in the Google Account's third-party access settings. Google may also end access on its own, for example after a long period of non-use.
- Existing records stay: disconnecting stops new calendar reads but does not delete records already stored.
- Deleting records: close the app, then delete this folder in Marlow's Windows profile: AppData, Local, MarlowAIOS, writes, showings. That removes the showing records, client links, reports and the stored Calendar access. Summaries of steps Marlow approved are also kept in two other folders under MarlowAIOS, writes (conversational and leads) and can contain booking names; deleting the showings folder does not remove them.
- Copies elsewhere: deleting local records does not necessarily remove backups, or copies held by other services such as GoHighLevel or Anthropic.
Changes and contact
This policy will be updated when the app's use of Google information changes, including changes to showing automation. Questions: admin@marlowsingh.com