Privacy policy
Last updated: 22 October 2026
1. Controller and data entrusted by agencies
The controller of data connected with operating Visario is Mateusz Jach, Widokowa 8, 32-010 Głęboka, Poland. Contact: kontakt@visario.app.
This policy covers visario.app and portal.visario.app, including signature pages, source connections and published reports. Visario is the controller of data needed to operate accounts, communicate, maintain security and bill for its own service. For client and team data processed on an agency's instructions, Visario acts as a processor; the agency or its client is the controller. The agreement with the agency, including the appropriately accepted Terms, defines the processing scope and conditions. This policy provides information and does not replace a data processing agreement.
2. What data we process and where it comes from
We receive data from users or agencies, people completing forms, authorised integrations and use of the service. The scope depends on the features used:
- Account and contact: first and last name or profile name, sign-in email, notification address, avatar and correspondence. Early-access signup includes email, optional phone and selected plan, signup source, consent wording and version, a checksum of that wording, and signup, email-confirmation and withdrawal dates. Confirmation and withdrawal links are stored as token hashes. New signups do not collect IP, browser data or full referrer URLs; older records may retain these. Signup creates no account or paid subscription. Demo emails require separate consent and address confirmation; historical unconfirmed signups are not used for these emails. Google sign-in provides an identifier, email and shared profile data; the picture may be copied to our file storage.
- Authentication and security: salted password hashes, active-session data, session and reset token hashes, 2FA configuration, encrypted 2FA secrets and recovery-code hashes. Sign-in history includes outcome, method, date, IP, browser and operating system. Older entries may include approximate IP-based location; external IP geolocation is currently disabled.
- Agency and team: workspace name, roles, module and publication permissions, client assignments, invitations and statuses, and change history including actor ID, date and action. We store logos, colours, report settings and email reply-to addresses. Evidence of legal-document acceptance includes the version, Terms and privacy-information checksums, time, user, agency and the representative's authorisation to accept data processing terms.
- Clients and reports: client names, identifiers, contact and billing details; stored results and reporting periods, commentary, draft and approved AI summaries, their versions and statuses, portal configuration, publication and delivery history. We also record shared-portal openings and users' notification read status.
- Schedules, goals and budgets: selected client and sources, run day, time zone, language and AI setting, run results and errors; advertising account, month, currency, budget, conversion target, CPA or ROAS, alert thresholds, assigned owner, measurements, retrieval status and alert acknowledgement or muting.
- Consents and signatures: document content or PDF, source scope, recipient and signatory data, signature image, accepted statements and event history. The evidence package includes date, IP, User-Agent, time zone, screen data, signature method and documentation checksum.
- Materials retained from former features: attachments and versions, text and links, deadlines, internal or client comments, and approver details, decision dates and outcomes. Data may remain in agency history after a feature is withdrawn; this does not mean that feature is currently offered.
- Data sources: account, site and service IDs and names, granted scopes, encrypted OAuth and refresh tokens, and service-account details where that method is used. We store access configuration, authorisation and the reporting data described below. In the separate existing-agency-access flow, we store the owner's declaration: wording and version, content and evidence checksums, confirmation of rights and processing basis, actor ID and name, time, and agency, client, source and created-access IDs. This new evidence contains no IP or browser data and is not a client signature.
- Invoices and payments: seller and buyer details, addresses, tax IDs, bank account, line items, VAT, amounts, currency, due dates and payment status; XML documents, KSeF identifiers and responses, and available official receipts. KSeF tokens are encrypted. For plan purchases, we store subscription data, Stripe identifiers, payment history and quota usage. We do not store full card numbers or CVCs.
- Agency trials and onboarding: trial or pilot start and end, type, limits and usage, selected scenario and first-report progress. Milestone records include action type (such as connecting a source, creating, viewing or sharing a report, or purchasing), agency, actor and record IDs, and time. They support trials, prevent repeat grants and help evaluate and improve onboarding. This register contains no report content, provider tokens or IPs. Individual pilot grants record the authorised operator, date, reason and grant ID. Agency default metrics include only sources and selected metric identifiers.
- Technical data: error and security logs, IP and device information, necessary cookies and browser-storage preferences. Landing-page analytics only starts with consent. The application and public portals do not run Google Analytics.
Data required for an account, payment, signature or integration is necessary to provide that feature; other fields are optional. OAuth does not require you to give us provider-account passwords. Do not enter special-category data or information unnecessary for client work. The signature image documents a statement; Visario does not use it for automated biometric identification.
3. Google and other data sources
A client's signed source consent and an owner's separate declaration of existing agency permissions are distinct from technical access authorisation. The agency declaration is not made on the client's behalf and does not replace the required processing basis, authorisations or processing agreement. Google sign-in to Visario alone grants no marketing-data access. Selected Google services can be authorised together with one account; other sources are connected separately.
- GA4: property IDs and names and aggregated results, such as users, sessions, page views, engagement, events, conversions and revenue, with selected report dimensions.
- Google Search Console and Bing Webmaster Tools: available sites, queries and page URLs, clicks, impressions, CTR and average position for the chosen period.
- Google Ads, Meta Ads, Microsoft Advertising and TikTok Ads: accounts and campaigns, spending, impressions, clicks, conversions and value, and other available metrics. Instagram: professional-account data and available profile, reach and engagement statistics. Availability depends on permissions and provider APIs.
- Data is used to verify access, create reports, retain results history, run schedules and, for Google Ads and Meta Ads, measure goals and budgets. Current integrations read and report data. Google Ads API's broader technical scope does not mean Visario creates or modifies campaigns.
- Shared Google credentials may serve several sources in an agency. Removing one connection may not remove shared authorisation or stop other connections. Access can be revoked in your Google account; requests to delete stored credentials and data can be sent to Visario.
- We do not sell Google data, use it for ad targeting or creditworthiness assessment, or transfer it to train general-purpose AI models. Optional analysis of selected metrics is a separate, visible feature described below. Staff access to Google data is restricted to cases allowed by Google's policy, including consent, security and legal obligations.
Visario's use and transfer to other apps of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
4. AI summaries and data sent to OpenAI
- Analysis is initiated by an authorised user or a schedule they enable with AI. Only selected numeric, aggregated metrics for current and previous periods, dates and period lengths, source type, currency and provider-warning information are sent to the OpenAI API.
- This analysis does not receive client names or emails, account IDs, report titles, campaign names, page URLs, search queries, documents, signatures or access tokens. Free-form agency commentary is not sent either. Aggregation reduces data scope but does not automatically guarantee every dataset is anonymous.
- Visario stores results, drafts and approved versions, language, model, author, approval time and AI-usage billing data. Clients see only approved versions. In automatic delivery mode, the schedule generates and approves summaries and sends the report under recorded agency authorisation, without separate manual approval for every run. Drafting an email from approved summaries does not trigger new AI analysis.
- OpenAI requests disable API response storage (store: false). This does not mean zero provider retention: its documentation says abuse-monitoring logs may be retained for up to 30 days and exceptionally longer for legal or security reasons. API data is not used for model training by default; Visario does not designate integration data for that training.
- AI provides suggestions for agency review. Visario does not use these to make solely automated decisions producing legal or similarly significant effects on individuals. A budget alert or measurement status does not change an advertising campaign.
5. Processing purposes and legal bases
| Purpose | Legal basis |
|---|---|
| Accounts, orders, plans and service provision to a user who is party to the agreement | Article 6(1)(b) GDPR — performance of a contract or steps before entering into it. |
| Agency representatives, communication, security, activity history and protection of legal claims | Article 6(1)(f) GDPR — legitimate interests in managing cooperation, securing the service and establishing, exercising or defending legal claims. |
| Measuring agency onboarding stages and improving the first-report process | Article 6(1)(f) GDPR — legitimate interests in identifying where users need help and improving the service, while limiting recorded data. This is an in-app action register, separate from optional landing-page cookie analytics. You may object on grounds relating to your particular situation. |
| Visario's own billing and tax obligations | Article 6(1)(c) GDPR — compliance with a legal obligation. |
| Early-access signup and optional landing-page analytics | Article 6(1)(a) GDPR — consent for the relevant scope; analytics also requires consent to store and access device information. You can withdraw your signup by writing to kontakt@visario.app. |
| Reports, AI, goals and budgets, consents, documents and client invoices on agency instructions | Processing under Article 28 GDPR and documented agency instructions. The agency or its client determines the legal basis. Signing access consent and OAuth do not replace all controller obligations. |
6. Retention and deletion
- Consent to early-access emails can be withdrawn using the unsubscribe link or kontakt@visario.app. Withdrawal removes email, phone and plan selection from the operational signup list and ends sending on that basis. Minimal consent and withdrawal evidence, including an address hash, consent wording/version and dates, may be retained only as necessary to demonstrate compliance or address a claim; it remains protected data and is subject to retention review.
- Onboarding progress, trial periods, quota usage and default metrics remain linked to the agency workspace. We use milestone records to operate and evaluate onboarding, not as an indefinite marketing history. Export or deletion requests cover these records and individual pilot-grant evidence, subject to obligations and justified protection of claims. Promotional-period data is retained to fulfil the agreed offer and settle the contract.
- Agency working data, reports, measurements, schedules, commentary and documents are retained to provide the ongoing service and its history under agency instructions. Plan expiry or removing an employee's access does not automatically delete this data. This includes retained attachments, comments and approval evidence from discontinued features.
- Deleting an account in the administration panel blocks the account, invalidates sessions and password resets, and cancels outstanding invitations. It does not fully erase the profile, activity history or agency-owned data. Personal-data deletion requests are handled separately at kontakt@visario.app.
- Shared Google tokens and other credentials are retained while they serve authorised access. Disconnecting a source does not delete reports, signed documents, measurement history or all shared authorisations. Revoking provider permissions stops use of that authorisation; Visario can be asked to delete retained data and credentials.
- Owner-declaration evidence documents instructions, the access-flow basis, accountability and service security. It remains in client history after the link or connection is deleted. It is included in client or agency exports and deletion scope, subject to documented instructions and separate assessment of legal obligations and claims. We do not set an indefinite retention period for it.
- Signature evidence, activity history and correspondence may be needed to demonstrate consent and protect claims. Visario's own billing data is retained for periods required by tax and accounting law. Further retention depends on document type, obligation and limitation period, not indefinite use for any purpose.
- Automated database backups run every 6 hours. Standard rotation covers 30 days and takes place after a successful next backup; separate migration or archive copies may remain longer for recovery and security. Backups are for service recovery, not active use of deleted data. Deletion requests also consider files and backups, and completed requests are reapplied after restoration.
- Security logs are retained as necessary to detect and investigate incidents and protect claims. Browser preferences remain until changed or deleted. Token, link or session expiry limits use but does not automatically delete history.
- Deletion in Visario does not delete source data at providers, documents submitted to KSeF or files previously downloaded by recipients. We verify requesters' authority before deletion or export; entrusted data is handled in coordination with its controller.
7. Recipients and processing outside the EEA
Sharing depends on the feature used. Access may be given to:
- Authorised agency members and Visario personnel within their duties and permissions. Agency-shared reports and portals are visible to link holders; treat links as confidential information.
- webh.pl (ultimahost.pl Szeliga sp. j.) — server infrastructure and SMTP email; Cloudflare — R2 file storage, including logos, avatars, documents and evidence packages.
- Resend — early-access thank-you and signup-confirmation delivery. It receives email addresses and message content with links; we do not send it phone numbers or plan selections.
- Stripe — plan purchases and renewals. It receives necessary contact, order and payment information; card details are entered in its form.
- OpenAI — selected aggregated metrics only when AI is used, as described in the AI-summary section.
- Google — sign-in, integration authorisation and optional landing-page analytics; Meta, Microsoft and TikTok — authorisation and retrieval for selected sources. Their own terms also apply.
- ipwho.is — approximate IP-based location in sign-in history. IP is transmitted to identify country, region and city; this is not device GPS location. Sentry provides error diagnostics where enabled. Events are limited to error type and code location; performance tracking and interaction history are disabled, and request bodies, cookies and user data are not transmitted. Events from public signature, access, report and password-reset pages are discarded.
- Poland's Ministry of Finance / KSeF — invoice data, identifiers and information needed to submit, check status and retrieve receipts when the agency uses this feature.
- The recipient's email provider — messages sent on user instructions. Correspondence with Visario support may also be available in the Google Workspace/Gmail mailbox used for contact. Legally authorised bodies — to the required extent.
We do not sell data or share it with independent advertisers. Global services, including Cloudflare, Google, Resend, Stripe and OpenAI, may involve transfers outside the EEA. These require a basis under Chapter V GDPR, such as an applicable adequacy decision or standard contractual clauses with assessment and required safeguards. We do not claim all data remains in Poland or the EU. Details of recipients, transfer bases and copies of safeguards are available at kontakt@visario.app.
8. Your rights and revoking access
Where and to the extent provided by the GDPR, you have the following rights:
- Access and a copy of your data, rectification, erasure, restriction and data portability where its conditions are met.
- Objection to processing based on legitimate interests on grounds relating to your situation; direct-marketing processing may be opposed at any time.
- Withdrawal of consent without affecting the lawfulness of earlier processing. Landing-page cookie preferences can be changed in the footer. Unsubscribe from early access through the email link or by contacting Visario.
- Complaint to Poland's President of the Personal Data Protection Office: uodo.gov.pl. Send rights requests to kontakt@visario.app; we respond without undue delay, normally within one month. Justified cases may require up to two additional months; we will inform you of the extension and reasons.
- Revoke Google access in your Google account's connection settings; remove service-account permissions in the relevant service. Revoke other connections with the respective provider. Revoking access and deleting stored data are separate actions.
- If an agency is your data controller, you may contact it directly. Visario helps it handle requests under the processing agreement. We do not disclose other clients' or colleagues' data to unauthorised persons.
Manage Google account connections
Data enquiries: kontakt@visario.app.
9. Cookies and browser storage
The landing page and application use different mechanisms:
- Landing page: cookie choices are stored locally as visario_cookie_consent until changed or deleted. Google Analytics 4 starts only after choosing “Accept all”. The _ga and _ga_* cookies identify browsers and sessions in website statistics, not access to clients' GA4 data. GA cookies default to two years and may be renewed on subsequent visits. Analytics includes pages and interactions, referrers, browser and device information and approximate location; IP is transmitted in communication with Google. Rejecting or withdrawing consent does not prevent use of the landing page.
- Application: visario_session supports sign-in and access protection until logout or session expiry. visario_sidebar remembers menu state for up to 365 days. Local or session storage holds preferences such as theme, language, Studio settings, auxiliary save history and an invitation token while joining a team. Local preferences do not replace server-side reports or data.
- Mechanisms necessary to provide the requested service do not require analytics consent. Optional analytics cookies require consent under Article 399 of Poland's Electronic Communications Law. Local preferences can be changed in the app or deleted in browser settings.
Choose “Cookie preferences” in the footer to reopen the choice. “Necessary only” disables analytics on subsequent visits and removes accessible GA cookies from this site. It does not withdraw data already sent to Google or client-account authorisations in the app.
10. Data protection
Public communication uses HTTPS. Integration credentials, KSeF tokens and 2FA secrets are encrypted on the backend; passwords are stored as salted hashes. Agency, module and assigned-client access is checked on the server. Public reports contain no integration tokens; signature and access links have their own scope and expiry. Backups, activity history and session controls help secure the service. Protect links and downloaded documents; no system is absolutely immune to incidents.
11. Policy changes
We publish the date and current policy. Material changes are communicated in the application or by email. New processing purposes, Google scopes or recipients requiring consent involve appropriate information and obtaining required consent before processing changes. Updating this page alone does not replace consent or a processing agreement.
12. Contact
Questions about data, recipients, export or deletion can be sent to kontakt@visario.app or the controller address above. Do not send passwords, tokens or full card details in your enquiry.