Trust Center

Google OAuth

One-Pochi uses Google OAuth so users can sign in with their Google account and authorize the permissions needed for the CRM workspace. Users can revoke Google permissions from their Google Account at any time.

• One-Pochi does not ask for or store your Google password.
• Google permissions should be limited to the product features being used.
• Workspace owners should review Google Drive sharing settings when changing team access.

Customer-owned data

CRM records are designed to live in the customer's Google Sheet. This means workspace owners can inspect, copy, export, and back up their CRM data using standard Google tools.

• No hidden One-Pochi CRM warehouse for customer records.
• Google Sheets remains the readable system of record.
• Exports and backups can be handled through Google Sheets, Google Drive, or Google Takeout.

App access and authorization

The public website is not the security boundary. Access should be checked inside the One-Pochi app before showing workspace data or CRM features.

• Approved beta users can open the app at onepochi.com/app.
• The app should verify signed-in Google identity, workspace approval, role, and payment status when billing applies.
• Users without approval should see a clear access request or support path.

Billing and payment data

One-Pochi expects to use Stripe for billing. Payment details should be handled by Stripe, not stored directly by One-Pochi.

Deletion and revocation

Users can revoke Google permissions from their Google Account. Workspace owners can request deletion or access help by contacting support. Because CRM records live in the workspace sheet, workspace owners should also manage Google Sheet and Drive access directly.

Resources