SOFI Analytics Privacy
SOFI Analytics Privacy Policy
Version: 20 October 2026
1. Controller and scope
Barnett Media Studio s. r. o., Dunajská 24, 811 08 Bratislava, Slovakia, company identification number (IČO): 46687955, is the controller of personal data processed for the private SOFI Analytics dashboard in ADRIANA BOARD / SOFI. Contact for privacy questions and requests: [email protected].
This notice covers the Analytics connection and saved dashboard reports. It does not replace the privacy and cookie notices of the source shops, Google, the DIGIX website hosting this page, or other SOFI features. Data collection on each source website requires its own applicable legal basis and cookie arrangements.
2. Data and sources
With account authorization, SOFI reads the Google account’s stable OpenID identifier; accessible Analytics account, property and web-stream metadata; and reports for selected properties. Reports may contain aggregate traffic, acquisition sources, page paths and titles, products, campaigns, events, conversions and revenue measurements where available.
SOFI also stores connection labels, property assignments, report periods, synchronization times, operational error status, and OAuth credentials including refresh tokens. Data comes from the authorizing account, Google Analytics APIs, and owner selections within SOFI.
The integration does not request Gmail access, individual customer order records or visitor-level user profiles. Aggregate reports are not automatically anonymous: a page title, URL or campaign label can contain personal information. Reports must be treated as private, and unnecessary personal information should not be placed in source URLs or campaign names.
3. Purposes and legal bases
Reports are used to understand the performance of the owner’s brands, compare periods and marketing sources, and provide the user-visible dashboard. Account identifiers and credentials support secure connections and scheduled or manual refreshes.
Where these activities involve personal data, the controller relies on legitimate interests under Article 6(1)(f) GDPR in privately evaluating the performance of the brands it manages and securely operating the dashboard. Processing is limited to the selected reports and necessary connection data; individuals may object as described below. Handling applicable legal data-protection requests is based on Article 6(1)(c) GDPR. These bases do not replace the legal basis required for measurement on the source websites.
Google authorization is permission to access an account; it is not, by itself, the legal basis for every downstream use under GDPR. Providing the connection is optional and is not a statutory requirement. Without it, the corresponding Analytics reports cannot be refreshed. Existing saved reports are not automatically deleted when authorization ends.
4. Google permissions and limited use
The requested scopes are openid and https://www.googleapis.com/auth/analytics.readonly. Google authorization permits reading Analytics resources accessible to the consenting account. The owner selects which properties are used in SOFI. This connection does not change Analytics settings or publish marketing content.
SOFI Analytics‘ use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not sell this data, use it for personalized advertising or send it for model training.
5. Providers, locations and international processing
Google provides authentication and Analytics APIs. Cloudflare hosts the SOFI server, connection credentials, report caches and daily synchronization records. Supabase hosts the existing BOARD database and its saved widgets and report summaries. The current Supabase project is configured in West EU (Ireland), eu-west-1.
Cloudflare’s existing deployment does not establish an EU-only processing restriction for this integration. An EU database location also does not guarantee that every provider’s support, security or subprocessor activity occurs solely in the EEA. International processing can occur through the service providers and their authorized subprocessors.
The providers‘ standard contractual documentation describes the applicable processing terms and transfer safeguards, including EU Standard Contractual Clauses where applicable: Cloudflare DPA, Supabase DPA, and Google measurement data-processing terms. The controller can provide information about the safeguards applicable to the relevant transfer on request. This notice does not assert that all processing stays in the EU or that a particular certification alone covers every transfer.
Hosting providers process data to operate and secure these features. Authorized dashboard users and the operator can view saved reports. Owner-created exports may also be stored on owner-controlled devices or backup locations; they are not made public by SOFI.
6. Security
Google OAuth credentials are encrypted in server-side storage using AES-256-GCM. The connection uses HTTPS, PKCE and a time-limited, browser-bound OAuth state. Access to Analytics functions requires the configured owner and workspace. This describes specific implemented controls, not a guarantee that every report or exported file is encrypted end-to-end or that no security incident can occur.
7. Retention and backups
| Data | Retention and limitations |
|---|---|
| Credentials and connection configuration | Retained while needed for the authorized connection, until removal is requested or the owner determines it is no longer needed. Revocation at Google prevents further authorized reads but does not erase local copies. |
| Report caches and saved BOARD reports | Latest caches are replaced on successful refresh. Saved reports remain until updated or removed when no longer needed for the dashboard or an applicable erasure request. The cache’s 15-minute reuse period is not a deletion deadline. No blanket automatic expiry currently removes all historical or exported copies. |
| Incomplete OAuth attempts | The authorization state is valid for 10 minutes. Expiry prevents its use; it does not by itself prove physical deletion of every incomplete attempt. Such records must be included in operator-assisted connection cleanup. |
| Cloudflare recovery history | The SQLite-backed storage used here supports restoration to points within the previous 30 days. An active-record deletion must not be presented as immediate physical removal from this recovery history. Old data must not be returned to use through a restore without reapplying the applicable removals. |
| Supabase project backups | The current Free plan does not include project backups. This does not mean owner exports or provider operational copies cannot exist. Paid project-backup retention is not represented as active for this project. |
| Owner-created exports and backups | There is currently no automatic expiry for downloaded files. They must be retained only while necessary for a documented recovery need and reviewed during maintenance and erasure requests. Relevant copies must be removed or sanitized where technically possible; inaccessible recovery copies must be restricted from ordinary use and their applicable expiry or limitation explained in the response. |
Expiry of a temporary export session does not delete files already downloaded. Provider security and operational records are governed by their applicable terms and controls; the controller cannot promise an immediate physical purge of all provider-managed copies.
8. Revoking access and requesting removal
You may revoke SOFI Analytics access at Google Account connections. To request removal of locally stored credentials and Analytics data, contact [email protected].
Removal is operator-assisted, not a self-service “delete every copy” button. It requires identifying the affected connection and brands, stopping their refreshes, removing relevant active credentials and report records, updating generated BOARD fields and charts, and reviewing related history, notes, exports and backups. A Google account may serve several brands; the affected scope must be confirmed before removal. Unrelated BOARDs, catalogue records and integrations must be preserved.
The selective removal preparation has been tested locally on isolated data. Its maintenance execution requires an authorized operator; it is not an enabled public deletion endpoint. A local test is not evidence of physical erasure from provider recovery systems. Any retained copies, legal exceptions or technical restrictions will be explained when handling the request. This procedure does not delete the original Analytics property or the Google account.
9. Your rights
Depending on the applicable conditions, you may request access to, correction or erasure of your personal data, restriction of processing, data portability, or object to processing. Where processing is based on consent, you may withdraw it without affecting the lawfulness of earlier processing.
Contact the controller at the email above. Proportionate information may be requested to verify identity. Requests will be answered without undue delay and normally within one month. If a lawful extension is necessary, you will be informed within that first month and told why. You may complain to a competent data protection supervisory authority, including in your country of habitual residence, place of work or the alleged infringement. Do not send passwords, authorization codes or tokens by email.
10. Planned AI-assisted analysis
AI-assisted analysis of selected GA4 reports and marketing strategy recommendations is planned but is not active in the current analytics integration. It does not currently automatically send these reports to a generative AI service.
Before activation, the controller will assess necessity, data minimization, the AI provider and its role, retention, security, transfers, legal basis and Google data-use restrictions; update the notice; and obtain any authorizations or consents required for the new use. Approval of this policy is not blanket authorization for future AI transfers. No solely automated decision producing legal or similarly significant effects about an individual is part of the current Analytics feature.
11. Changes and contact
This notice will be updated before materially changed processing begins. Where required, affected users will receive an updated disclosure and be asked for consent. Privacy and deletion requests: [email protected].