What ATNOS asks for, and why.

ATNOS acts inside accounts that belong to you. Every connection is authorised through the provider's own consent screen, scoped to the narrowest permissions the features you enable require, and revocable from either side at any time.

How authorisation works

Authorization Code with PKCE. ATNOS never requests, receives or stores passwords for a connected service.
Incremental scopes. Permissions are requested at the moment a feature is connected, not up front, and only the narrowest set that feature needs.
Rotating refresh tokens. Tokens rotate on every use with replay detection; a reused token invalidates the chain and alerts the workspace owner.
Revocable from either side. Disconnect in ATNOS or revoke at the provider. You never need our cooperation to cut off access.
Tokens are envelope-encrypted. Per-tenant data keys wrapped by a master key in a managed key service, stored separately from application data, and destroyed immediately on disconnection.

What each connection accesses

Service	Reads	Writes	Typical scope
Google Ads	Campaign structure, assets and spend	Campaign drafts, paused until you launch them	adwords
Google Analytics	Sessions, events and conversions	Nothing — read only	analytics.readonly
Search Console	Queries, impressions and positions	Nothing — read only	webmasters.readonly
Business Profile	Local listings and reviews	Listing edits you approve	business.manage
Meta	Campaigns, audiences and creative	Campaign drafts, paused until you launch them	ads_read, ads_management
HubSpot	Contacts, deals and lifecycle stages	Contact and lifecycle updates you approve	crm.objects.contacts.read
Shopify	Products, orders and customers	Nothing — read only	read_products, read_orders
WordPress	Pages, posts and metadata	Drafts against your CMS, published only on approval	site credentials
Stripe	Subscriptions and revenue records	Nothing — read only	restricted read key
Slack	Channel and user directory	Approval requests and notifications	chat:write

Confirm the scope column before submitting for verification. The identifiers above describe the access each feature needs. They must match, exactly, what your OAuth client actually requests — a review fails on a mismatch between this page and the consent screen.

Google API Services User Data Policy

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

Concretely, data received from Google APIs is used only to provide and improve the features you have enabled in your workspace. It is not transferred to third parties except as needed to provide those features, to comply with applicable law, or as part of a merger or acquisition. It is not used for advertising, and it is not used to train generalised models. No human reads it except with your explicit permission, for security purposes, or where the law requires it.

What ATNOS never does

Never asks for, receives or stores your password for a connected service.
Never publishes, launches or changes publicly visible material without an explicit approval — every such action is prepared as a draft and waits for a person.
Never holds advertising spend; billing stays between you and the platform.
Never uses your data to train generalised models.
Never sells connected data or shares it with advertisers.

Revoking access

Disconnecting inside ATNOS destroys the stored tokens immediately. You can also revoke from the provider's own settings, which cuts access without touching your ATNOS workspace.

Provider	Where to revoke
ATNOS	Settings → Connections → Disconnect
Google	myaccount.google.com/permissions
Meta	Settings & privacy → Settings → Apps and websites
HubSpot	Settings → Integrations → Connected apps
Shopify	Admin → Apps → Uninstall
Stripe	Dashboard → Settings → Authorised applications
Slack	Workspace settings → Manage apps
WordPress	Users → Profile → Application passwords → Revoke

To remove the data as well as the access, follow Data Deletion.