Official OAuth, revocation, and the no-content-storage claim appear after the visitor has already been asked to connect. Put those facts beside the first CTA.
Sample $149 deliverable
Trust must arrive before Google access.
The page explains a clear outcome: share selected Google Sheet ranges without exposing private tabs or formulas. The primary conversion risk is sequence. The first action asks for Google access before the page has surfaced the facts that make that access feel safe.
Prioritized friction list
Fix these in order.
The CTA asks the visitor to accept the safety claim. Offer a reversible first action instead: connect a duplicate or test sheet before inviting a real client.
A simple client-view visual should distinguish editable ranges from hidden margins and formulas. Make the product boundary visible before describing more features.
Replacement hero
Safe client access for Google Sheets
Share the cells. Keep the secrets.
Turn a Google Sheet into a secure client portal. Clients update only the ranges you choose; your formulas, margins, and private tabs never leave your control.
Connect a test sheet — freeOfficial Google OAuth · Revoke anytime · Contents never stored
First experiment
Variant: test-sheet CTA plus trust microcopy versus the existing first screen.
Primary metric: hero CTA click-through. Secondary: completed OAuth and first range shared. Do not interpret traffic without separating CTA intent from completed permission.