AIVA Reporting privacy
Updated 5 October 2026
AIVA Reporting is the reporting connection used by AIVA's private project portal. It helps the authorized team track its websites and apps. It is operated by AIVA; contact aiva@aiva.is about this notice or your data. Individual apps have separate privacy policies listed on our home page.
Information we access
With the account owner's permission, we request read-only access to Google Analytics, Google Search Console and AdMob. This allows the server to read property, site and app identifiers and aggregate performance reports: website sessions and views, search clicks and impressions, average search position, ad requests, ad impressions, clicks and estimated advertising revenue. Google permissions can cover multiple properties in the connected account; the portal's reporting configuration selects which projects to import.
We store project mappings, daily reporting totals, refresh status and an encrypted authorization token so the server can refresh reports. The portal also stores team login information, project records, tasks and connected repository activity. We do not receive your Google password. This connection cannot edit your Google properties, campaigns, ads or account settings.
How information is used and shared
Reports are used to display project performance to authorized AIVA team members. They are not published on the public website. Supabase provides the portal's backend and database; Netlify hosts the website and routes portal requests. These providers process data to operate the service. Google processes authorization and reporting requests under its own policies.
Google data is not sold, used for ad targeting or used to train general-purpose AI models. AIVA Reporting's use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.
Storage and access
The portal requires sign-in and team membership. Google client secrets and authorization tokens stay on the server; refresh tokens are encrypted before database storage. Network requests use HTTPS. Essential session cookies keep team members signed in and protect the authorization flow. Hosting and backend providers may retain operational logs to run and protect the service.
Retention, revocation and deletion
Reporting records are retained for project history until an authorized owner requests their deletion or the service is retired. You can revoke AIVA Reporting's Google access at any time through Google Account connections. Revocation stops future authorized imports; it does not automatically erase reports already imported.
To request deletion of stored reports, project mappings or authorization data, contact aiva@aiva.is. We verify that requests come from an authorized owner before removing private team data. Copies in provider backups may remain until those backups expire under the provider's retention arrangements.
Changes and questions
We update this page when the reporting service changes. If we need additional Google permissions or use Google data for a new purpose, we will explain the change and request consent before doing so. Contact us to request access to or correction of your information, or to ask about this notice.