OYYO AI NotzUp: Capture All · guide
Connectors
Distinguish OYYO identity sign-in from deliberate provider permissions and truthful connection status.
Before you begin
- A signed-in account and an available configured provider.
- Permission to use the specific provider account and selected files/calendar data.
Step by step
Inspect the capability
Open Connectors and choose the needed Google, Microsoft, Zoom or Slack capability. Available, Setup required, Connected, Error and Reauthorization required have different meanings.
Review OYYO Connectors consent
Approve only needed scopes through the supported provider consent flow. OYYO AI sign-in is identity; it does not authorize provider data access.
Confirm live access
Return to the account and inspect capability verification. A saved grant alone is not proof the requested provider action works.
Choose data deliberately
Import only selected supported accessible information. Inference on customer content still runs on your own authorized device, not the provider connector server.
Review disconnect semantics
Use the existing local disconnect/revoke control. Unless the provider confirms external revocation, also manage provider permissions in that provider's account settings if needed.
Expected result
A deliberately authorized, truthfully reported provider capability, or a clear setup/error state.
Privacy and permissions
Recordings, files, searches, scans, OCR, barcode counts and supported local-AI results do not leave the device by default. Only a deliberate online action—Share, Search online, connector authorization or encrypted backup—transmits the selected data or value. Language-pack downloads do not upload the source text. Provider tokens remain protected online for coordination. Do not paste keys into notes, exports or public documentation; connector authorization does not allow cloud customer-content inference.
Troubleshooting
Setup required or reauthorization
Check provider configuration and requested scopes, then reconnect explicitly when available. Do not mistake social sign-in for connector access.
Disconnect still appears at the provider
Local disconnection stops NotzUp's local use; it does not claim external provider permission was revoked. Review the provider account's own permission controls.