Google user data disclosure

Limited Use

LoopLens's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

What LoopLens asks Google for

• Read-only Gmail access (gmail.readonly), to read recent messages in the inbox you connect and find customer conversations waiting on a reply.
• Your Google account email address and sign-in identity (email, openid), to confirm which inbox you connected.

LoopLens does not ask for permission to send, delete, label, archive or move email, and it never does any of those things.

What LoopLens reads

The Free Audit attempts a scan of one inbox until its first successful result; a failed attempt can be retried. The Free Audit does not provide recurring free monitoring. Paid plans scan daily. On each scan, LoopLens reads messages from roughly the last 30 days in each connected inbox. For each message it reads the date, sender, recipients, subject, message identifiers and the Gmail message snippet, a short excerpt of the message text. It does not download full message bodies or attachments.

What LoopLens stores

• The connected inbox's email address.
• Gmail thread and message identifiers, so you can open a flagged conversation in Gmail.
• Codes recording why a conversation was or was not flagged.
• The email domains of people in each conversation and one-way fingerprints of subject lines and message snippets.
• A short coded summary of each conversation's state, used to notice when it changes.
• The token Google issues when you connect the inbox, used only to read that inbox.

LoopLens does not store message snippets, readable subject lines, message bodies or attachments.

How LoopLens uses Google data

LoopLens uses Google data only to provide its user-facing feature: finding inbound customer and sales conversations that have waited too long for a reply, and showing the account owner the evidence in reports and alerts. Alerts go only to the account owner; LoopLens never contacts the people who emailed you.

LoopLens does not use Google data for advertising, does not sell it, and does not itself use it to train or improve AI or machine learning models.

Who receives Google data

• TypeSafe, our AI model provider. LoopLens is built to send TypeSafe Gmail message snippets, which side of the conversation sent each message, the connected inbox's address, internal account and inbox identifiers, and your business name and type, only so TypeSafe can decide whether a conversation needs a reply. TypeSafe's public terms say it does not use the data we send it to train AI models without our consent, that it keeps data as long as reasonably necessary for its service and business purposes, and that it may derive usage telemetry, including classifications, to improve its products. Details are in the privacy policy.
• DigitalOcean, which hosts the LoopLens app and database where the stored data above is kept.

We transfer Google data to others only to provide or improve LoopLens's user-facing features, for security, or to comply with the law. In a merger, acquisition or sale of the business, we transfer Google data only after obtaining your explicit prior consent, and it stays under the same protections. We do not transfer it for any other purpose.

Human access

No person at LoopLens reads your email. A small number of staff can view reports, which contain the codes and Gmail links described above, to operate and secure the service. Staff will look at more only with your permission, for security reasons, or where the law requires it.

Removing access and deleting data

At closure, LoopLens tries to revoke its Google access for every inbox still connected. You can also remove LoopLens at any time in your Google Account under Security, Third-party apps and services. Removing an inbox in the app revokes LoopLens's Google access for that inbox and deletes its stored token. If LoopLens can't confirm the revocation, the inbox stays connected and the app shows an error. Data is deleted as described in our retention section of our privacy policy.