Effective Date: September 28, 2026
Last Updated: September 28, 2026
Poardal Software Inc. ("Poardal Software," "we," "us," or "our") provides Innovique Studio (the "Service"), an AI-powered marketing intelligence software-as-a-service platform, and operates the related marketing website. This Privacy Policy describes how we collect, use, share, and otherwise process personal information in connection with: (a) our marketing website, served at both innoviquestudio.com and innoviquestudio.ca (the "Marketing Website"); and (b) our application at app.innoviquestudio.com, including when you create an account, administer a workspace, or use any of the features of the Service (AI agents, analytics dashboards, creative tools, website and content publishing, agency tools, and related functionality).
Innovique Studio is a product of Poardal Software Inc. References to "Innovique Studio" in this policy mean the Service and related offerings described above.
SaaS and Customer Relationship. The Service is provided to Customers under a commercial agreement. When we process Customer Data to provide the Service (including hosting, authentication, AI-assisted content generation, analytics integrations, collaboration features, and support), we do so on behalf of and under the instructions of the applicable Customer, and we act as a service provider (and, where applicable, a "processor"). In those cases, the Customer is responsible for determining what Customer Data is submitted to the Service and for providing required notices and obtaining any necessary consents from its Authorized Users. Poardal Software acts as an independent controller for personal information we process for our own commercial relationship purposes (for example, sales communications, account administration, billing, security, fraud prevention, and marketing website interactions).
Commercial Relationship Notice. This Privacy Policy is written primarily for our business contacts and Customer organizations that purchase or evaluate the Service (a "commercial relationship"). If you are an employee, contractor, freelancer, or other representative of a Customer or prospective Customer, we may collect and use your personal information to manage our relationship with your organization (for example, to provide demos, set up accounts, administer subscriptions, provide support, and send service-related communications).
Key Definitions (summary). "Business Contact" means an individual acting in a business capacity for a Customer, partner, supplier, or prospective Customer. "Authorized User" means an individual authorized by a Customer to use the Service under that Customer's subscription (including owners, admins, managers, and members of a workspace). "Customer Data" means content and information (including personal information) submitted to, generated within, or processed through the Service by or on behalf of a Customer or its Authorized Users. "Workspace" means a tenant within the Service; workspaces can be organized into parent/child hierarchies (for example, agencies with client sub-workspaces) and share a single subscription at the parent level.
If you use the Service through a Customer (for example, your employer, agency, or the organization that invited you), please note that the Customer's own privacy practices may also apply. Our handling of Customer Data may also be governed by a separate agreement with the Customer (including data processing terms, where applicable).
Please read this Privacy Policy carefully. It is a notice describing our practices, not a contract. Where we rely on your consent we say so and we ask for it; the legal bases and the rights available to you are described in Sections 12 to 14. The contractual terms governing your use of the Service are set out in our Terms of Service.
Applicable Laws. We design our privacy practices to comply with applicable privacy and data protection laws where we operate, including Canada's Personal Information Protection and Electronic Documents Act (PIPEDA) and Quebec's Act Respecting the Protection of Personal Information in the Private Sector (Law 25). Depending on how you use the Service and where you are located, additional laws (such as the GDPR, UK GDPR, and certain U.S. state privacy laws including the CCPA/CPRA) may also apply.
We reserve the right to make changes to this Privacy Policy at any time and for any reason. We will alert you about any material changes by updating the "Last Updated" date of this Privacy Policy and notifying you via email. You are encouraged to periodically review this Privacy Policy to stay informed of updates.
We collect personal information in several ways in the context of our commercial relationship with Customers and prospective Customers (including sales, contracting, billing, and support), when Authorized Users access and use the Service, and when visitors interact with our marketing website.
If you are a Business Contact (for example, you request a demo, negotiate or administer a subscription, or contact us for support), you may provide personal information such as your name, business email address, job title, organization, billing country, and the content of your communications with us.
If you are an Authorized User, we collect and process Customer Data that you or your organization submits to the Service, and information associated with your account. Your organization's workspace owner or admin may also provide your details (for example, name and email address) when inviting you to a workspace.
• Name and email address
• Avatar image (optional)
• Time-zone preference
• Password (stored in hashed form using Supabase's managed bcrypt implementation) and multi-factor authentication (TOTP) configuration, if enabled
• A record that you agreed to our Terms of Service and acknowledged this Privacy Policy when you created your account, when you did so, and which version of each was then in force
• Workspace name, slug, role (owner, admin, manager, or member), and membership history (including invitations sent, accepted, or revoked)
• Parent/child workspace relationships (for agency customers)
• Connected third-party credentials and metadata:
• Google Analytics 4 (GA4) and Google Search Console (GSC) OAuth access and refresh tokens, along with the connected Google account email address and selected property/site identifiers
• Conversation content and files: your prompts, the AI-generated responses, the files you attach to a conversation (text and CSV files, PDFs, and images), which we process to answer you and whose retention Section 8.1 describes, the text read from a text or CSV file, the name, type and size of each attachment, chat session titles, and model/usage metadata (input and output token counts, model identifiers, timestamps)
• Content you create or generate in the Service, including:
• Workshop (content library) items
• Presentations (slides, themes, charts, and data tables)
• Websites built with the Website Builder (pages, sections, SEO metadata, and custom domain configuration). A message sent through the contact form of a published website is forwarded to the workspace by email and is not stored in the Service
• Design Studio projects (canvases, layers, assets)
• Social Graphics Generator cards
• Blog HTML generations
• Generated images (and their prompts, providers, and credit usage) and generated audio tracks
• Agent memory: content saved to your workspace's memory, the summaries written from it, and the vector representations generated so that agents can search it. Section 15 describes what enters memory, who can see it, and how it is managed
• Persona profiles and focus-group panel transcripts
• Brand Guidelines: brand name, tagline, voice and tone, language style, target audience, key messages, key personnel, contact information, social profile links, brand colors, fonts, industry, services, unique selling propositions, content guidelines, boilerplate copy, emoji preferences, logos, and image style guides (including material extracted from any URL you ask us to crawl or documents you upload)
• Agent Knowledge Base entries
• Agency data: URLs and names of prospects you submit for SEO audits, accessibility (WCAG) audits, or sales reports, and the resulting audit and report content
• Scheduled report configurations (recipient email addresses, schedule, included data sources)
• Usage records: token consumption per agent, chat counts, image and audio credit consumption, web search counts, email send counts, Workshop and Knowledge Base item counts, monthly rollovers, and workspace-level storage usage
• Audit log entries: your name, the IP address the action came from, and a record of actions taken in the Service, including member role changes, member additions or removals, workspace creation, team invitation acceptance, plan and subscription changes, communication-preference changes, contact deletions, agent-memory resets, support-ticket changes, and actions taken on your account by our authorized personnel
• Help assistant questions: when you use the in-app help assistant, we keep a log of the question you typed, the help articles that were matched, an excerpt of the answer, and whether the assistant declined or filtered the request. We use it to improve the assistant's answers, it is readable only by our authorized personnel, and it is deleted after 6 months (see section 6.4.5)
• Voice preferences: if you turn on spoken replies, the voice settings you choose (whether spoken replies and the microphone are on, the voice used for each agent, how much of a reply is read aloud, and when you turned the feature on)
If you visit the Marketing Website, we may collect information you submit through the site (for example, demo requests or contact-form messages) and information collected via cookies and similar technologies, including:
• Your name, email address, organization, and message content if you submit a form
• Analytics data about your visit (pages viewed, session duration, traffic source, device and browser information, approximate geographic location) collected via Google Analytics
• IP address and connection metadata used for bot detection, and a country indicator derived from your browser's time-zone and language settings, used for regional currency display
When you access or use the Service or visit our website, we (and our service providers) automatically collect certain information, such as:
• Device information: device type, operating system, browser type and version (user-agent string)
• Usage data: pages visited, features used, time spent on pages, and navigation patterns within the Service
• Log data: IP address (which may be truncated or masked in certain logs where feasible), access times, request paths, and referring URLs
• Session data: session identifiers, authentication tokens, session creation and expiration times, and last-activity timestamps (managed by Supabase)
• Authentication events: we keep our own record of sign-in, sign-up, multi-factor and sign-out events, separate from the session data above. Each record holds the event type, the time, the IP address, the browser user-agent, and the email address entered at the attempt. We record failed attempts as well as successful ones, so that we can detect credential-stuffing and account-enumeration abuse. On a failed sign-in the address is recorded exactly as it was typed, so it may be misspelled or may not correspond to any account. These records are kept for 90 days.
• Performance and diagnostic data: application performance metrics, page-load times, long tasks, resource-loading events, error reports, crash logs, stack traces, and sampled session replays. When you are signed in, our performance-monitoring and error-tracking tools receive your user ID, but not your name or email address, to help us triage issues affecting specific accounts, and are configured to limit the collection of personal information where feasible; sensitive form inputs are masked by default.
• Geographic indicator for billing: a country indicator your browser reports from your device's time-zone setting, or from your browser's language setting where the time zone is inconclusive, is used to decide whether to show and charge prices in Canadian or United States dollars. Where your browser reports neither, an approximate country derived from your IP address by our infrastructure provider is used as a fallback. Where you already have a subscription, the country recorded when it was created is used instead, so that your pricing stays in one currency. Not every plan and add-on is priced in Canadian dollars; where one is not, it is shown and charged in United States dollars. The currency is always shown next to the price
• Local storage and similar technologies. The Service uses browser local storage and session storage for two different purposes, set out in full in section 9.1. A small number of items are strictly necessary: your authentication session, a throttle on repeated failed sign-in attempts, and a check that detects stale application code after a release. The rest remember choices you have already made, such as your selected workspace, your theme, and in-progress editor state, and you can clear those without preventing use of the Service. Your authentication session (issued and validated by Supabase) is stored in your browser's local storage and sent to our servers with each request; it is not stored in a cookie. Our bot-protection provider may set its own cookies on the sign-up and login form, as described in section 9.2.
We may receive personal information from third parties in a commercial-relationship context or to provide the Service, including from Customers, payment processors, connected third-party platforms, and our sub-processors.
• Workspace owners and administrators may provide your name and email address when inviting you to a workspace
• Stripe (our payment processor) provides subscription status, invoice events, billing country, and customer/subscription identifiers; we do not receive or store your full payment card number
• Google (GA4 and GSC) returns the analytics and search-performance data you have authorized us to access on your behalf
• DataForSEO returns business-listing, review, search-result, backlink, and keyword-ranking data in response to queries the Service makes on your behalf. Where a result contains a review written by a member of the public, we keep the review text and shorten the reviewer's name to a first name and last initial before storing it; the full name is never stored, and reviewer photographs are not retrieved. Only the review text is sent to an AI provider, never the reviewer's name. These queries come both from agents you interact with directly and from scheduled checks you enable, such as review monitoring, backlink tracking, and competitor tracking, which run on a recurring basis until you turn them off
• Unsplash returns stock-photo search results and download metadata when you search for images within the Service
Our Customers can publish websites built in the Service, and can embed a review widget on their own websites. If you are a visitor to one of those pages, we may process limited information about your connection.
• Published websites. Pages are served from our publishing infrastructure, which receives your IP address, browser user agent, and the page requested, as any web server does. If you send a message through a contact form on a published website, that message is forwarded to the workspace by email and is not stored in the Service.
• The review widget. Where a Customer embeds our review widget, your browser loads it from our systems, which receive your IP address and browser user agent for the purpose of serving it. The widget sets no cookies, stores nothing in your browser, builds no profile of you, and does not track you across sites. The reviews it displays are business reviews retrieved from public listings. It does not display reviewer names at all, and reviewer photographs are never retrieved. Where a Customer has chosen to show only reviews above a rating threshold, the widget displays a notice saying so.
• Bot protection. Forms on published websites (contact forms, newsletter sign-ups and other hosted forms) and public booking pages are protected by a CAPTCHA challenge, as described in Section 4.9.
We do not use this information for advertising, and we do not combine it with information about you from other sources.
We use personal information for the purposes described below. These purposes vary depending on whether you are a Business Contact, an Authorized User, or a website visitor, and whether we are acting as a controller (for our commercial-relationship purposes) or as a processor/service provider (for Customer Data).
Precedence for Google user data. Notwithstanding any other provision of Section 3 or Section 4, information obtained through the Google Analytics 4 and Google Search Console APIs is used and transferred only as described in Section 4.8.1. We do not use it for product analytics, marketing, personalization outside the connected feature, or model training, and it is not included in error reports, session replays, or performance monitoring.
• Create and manage your account, workspace profile, and parent/child workspace hierarchy
• Authenticate you (including multi-factor authentication where enabled) and maintain secure sessions
• Enable collaboration among workspace members based on their assigned roles
• Operate the Analytics Dashboard by calling the Google Analytics 4 and Google Search Console APIs on your behalf using read-only scopes
• Operate our AI agents (Nala, Maven, Quill, Echo, Pulse, Compass, Pixel, Scout, Nexus, Envoy, Nova, Sonic, and the Atlas orchestrator) and related features by sending your prompts, files, brand guidelines, and knowledge-base entries to third-party AI providers. Where you have connected Google Analytics 4 or Google Search Console, data retrieved from those accounts may also be sent to these providers so that the agents can answer your questions and generate reports about your own analytics and search performance, and, when you choose to use it in another feature, to the providers that feature uses (Section 4.8.1). We never use this data to train AI models, and neither Anthropic nor OpenAI, the providers that receive it for those answers and reports, uses it for training: Anthropic under its data processing agreement, and OpenAI under its API data-usage policy (see Sections 4.8.1 and 15). The one exception is the Brand Model feature: if you choose to train a brand model, the images you select for it, and the captions we generate from them, are used to train a private model that is available only in your workspace and is deleted with it. This exception does not apply to data retrieved from Google Analytics 4 or Google Search Console, which we never use to train any model.
• Generate images, SVG graphics, and audio assets via the Pixel and Sonic agents and their underlying providers
• Maintain your workspace's agent memory, so that agents can draw on strategy, brand, and content work already done in the workspace when producing something new. This involves sending saved content to our AI providers to summarize it and to generate the vector representations that make it searchable
• Publish the websites you build to our publishing infrastructure, at your direction
• Run SEO audits, accessibility (WCAG) audits, and landing-page analyses against URLs you submit
• Crawl websites, process uploaded brand briefs, and store the resulting brand guidelines for later reference by agents
• Process payments and manage subscriptions through Stripe, including add-on purchases (for example, audio, token and image credit packs)
• Send transactional emails (account setup, password resets, team invitations, contact-form deliveries, and other service notifications) via our transactional email provider
• Maintain audit logs for accountability, security, and compliance purposes
• Respond to inquiries, provide demos, and communicate with you about the Service
• Negotiate, enter into, and administer our contracts with Customers and partners
• Process payments, manage subscriptions, and maintain related records
• Provide support, manage support tickets, and communicate service-related updates
• Verify your identity and prevent unauthorized access
• Protect against automated abuse and credential stuffing via CAPTCHA challenges on account sign-up, sign-in, password reset, and verification-email resend, and on the forms (contact forms, newsletter sign-ups and other hosted forms) and public booking pages published from the Service
• Monitor application performance, availability, and error rates via our monitoring and error-tracking tools
• Detect, prevent, and respond to security threats, fraud, or technical issues
• Enforce tenant isolation via row-level security (RLS) and role-based access controls
• Maintain audit logs of significant workspace events, including member and role changes, plan changes, workspace creation, communication-preference changes, contact deletions, and actions taken on an account by our authorized personnel
• Enforce our Terms of Service and subscription limits (including monthly token and image credit allowances, limits on saved chats, and audio credit balances)
• Analyze usage and performance to maintain, support, and improve the Service (including troubleshooting and debugging)
• Review the help assistant's question log to improve its answers and the help articles it draws on
• Develop and improve features, including based on aggregated trends and feedback
• Understand how visitors use the Marketing Website and measure marketing effectiveness (for example, via Google Analytics)
• Respond to your inquiries and support requests via the in-app help assistant and email
• Send service communications and administrative notices (for example, onboarding, account updates, and security alerts)
• Where permitted by law, send information about features, updates, and events related to the Service; you can opt out of non-essential communications.
• Comply with applicable laws, regulations, and legal processes
• Respond to lawful requests from public authorities
• Maintain records required by applicable law (for example, tax and accounting records)
We do not:
• Sell your personal information, as "sell" is defined under applicable law, including for monetary or other valuable consideration
• Share personal information for cross-context behavioral advertising
• Share your personal information with third parties for their own direct marketing purposes
• Use Customer Data (including your prompts, files, brand guidelines, analytics data, or generated content) to train general-purpose AI models.
We may share personal information in the following circumstances, including to provide the Service, manage our commercial relationship, and comply with legal requirements. Where we process Customer Data, we share it with service providers and other parties only as needed to provide and secure the Service and consistent with our agreements with Customers.
Your information is visible to other members of your workspace based on your role and permissions. Owners, admins, and managers can see membership lists and roles. Audit-log entries are not visible to workspace members; they are retained for security and compliance and are accessible only to authorized Poardal Software personnel. Content created in a workspace is visible to every member of that workspace, whoever created it: chat sessions and the messages in them, Workshop items, Knowledge Base entries, Brand Guidelines, presentations, websites, designs, audit reports, generated images and audio, and the workspace's agent memory. A member sees the same content an administrator sees. Roles govern what can be changed or deleted, not what can be read. Files you attach to a conversation are the one thing handled differently, and it runs both ways. A file you attach to an ordinary conversation is not shown to anyone, including you: it is not displayed in the conversation and cannot be downloaded. Where text was read from it, that text is kept only so that the assistant can refer back to it later in the same conversation. The conversation itself, and the assistant's replies about the file, are visible to every member of the workspace. But where an image you attach is kept as workspace content, as Section 8.1 describes, it appears in that workspace's image gallery, and every member can see and download it. Owners and administrators of a workspace's immediate parent workspace inherit the same access to it. Treat anything you put into a workspace as visible to everyone with access to that workspace. This sharing is fundamental to the collaborative purpose of the Service.
We share information with third-party service providers who process data on our behalf. The providers listed in Sections 4.3 to 4.9 receive personal information under written data processing terms that limit their use of it to providing their service to us and to the purposes those terms permit, consistent with applicable data protection requirements, except where a provider's entry below says otherwise. Where a provider currently processes data under its published terms of service rather than a data processing agreement, the entry says so; we have requested one from each of those providers, and where a provider has told us it does not offer a separate agreement, the entry says that as well. Some AI models are reached through another provider's platform rather than directly; those entries say "reached through", and the platform provider's agreement covers the data routed to its partners.
• Supabase: managed PostgreSQL database, authentication, file storage (including uploaded brand assets and failover storage for media files, as described in Section 6.1), and edge-function runtime. Our primary Supabase project is hosted in a United States region.
• Netlify - hosting for the Innovique Studio application front-end
• Vercel - hosting for the websites you publish (content published from the Website Builder is served from Vercel's infrastructure). A published site is served at a subdomain of sites-pro.com, or at a custom domain you connect
• Upstash (Redis) - short-lived caching of analytics query responses (GA4 and GSC) and business-listing/SERP responses to reduce third-party API usage and improve performance
• Stripe - payment processing, subscription management, and secure storage of payment credentials. All payment transactions are conducted directly through Stripe's platform. At checkout, Stripe collects your billing address and, if you purchase as a business, your business name and tax registration number, to calculate any applicable taxes and show them on your invoices and receipts; these stay with Stripe and are not copied into our own systems. We receive only Stripe customer and subscription identifiers, billing country, and transaction events; we never access or store your payment card details. The Stripe customer record is created with the email address of the workspace owner who set up billing, and it is kept with the billing records described in section 6.4.4, including after that person deletes their account.
• Resend - transactional email delivery (account notifications, team invitations, contact-form messages forwarded from a published website, and other service notifications). Resend receives recipient names, email addresses, and message content for this purpose. For the message content Resend acts on our instructions. For routing information (the sender, the recipient, and the delivery events of each message) Resend acts as an independent controller under its own privacy policy.
When you interact with our AI agents or creative tools, the content you submit (including your prompts, uploaded files, chat history, brand guidelines, and knowledge-base entries, as applicable) is sent to one or more of the following providers to generate responses, images, or audio.
Where you have connected Google Analytics 4 or Google Search Console, information retrieved from those accounts may be included in what is sent to these providers: when you ask an agent a question about that data, when you request a report or page-level analysis based on it, when your dashboard produces its weekly summary as you open it, and when a recurring check runs against your connected accounts on a schedule we set rather than at your request, such as the weekly scan for unusual changes. It also reaches a provider when you choose to use it in a feature that provider performs, such as having a reply read aloud or turning an answer into an image. These transfers occur only to deliver features you have turned on or chosen, and are subject to the Limited Use commitments in Section 4.8.1.
• Anthropic - Claude models, used as the large-language-model provider
• OpenAI - used for image generation and as a text model
• Google (Gemini) - Google image models are used for image generation, editing, and search-and-replace, and are reached through Replicate (see Replicate). A direct path to Google's own API remains in the Service as a rollback. It operates under Google's paid-tier API terms, which exclude the use of your data for training, and it is not covered by a separate data processing agreement
• Replicate - used for image generation, editing, upscaling, vectorization, and background removal. Replicate processes data under its published terms; we have requested a data processing agreement
• Recraft - used for photorealistic image generation, AI vector/SVG output, image vectorization, and background removal. These requests are sent to Recraft directly. A Recraft model hosted by Replicate is also used as a secondary route for vectorization and as a fallback for raster generation (see Replicate)
• FAL - used for image generation, upscale, and speech models, including the voice synthesis that produces an agent's spoken reply, and including models operated by FAL's partners that are reached through FAL's infrastructure; FAL's agreement with us covers the data routed to those partners, and FAL has committed to us that it is not used for training. Voice synthesis is performed on our servers rather than in your browser, so the text of the reply is sent from us to FAL and the audio is returned to you through us
• Deepgram - used for speech to text: turning what you say into text, for the voice conversation feature that a workspace owner or administrator turns on for a workspace. Because voice is real-time, your browser sends your speech to Deepgram directly, using a short-lived access token we issue for that session, rather than routing the audio through our servers. Deepgram therefore receives the audio of your speech and your device's connection details, including its IP address, for the duration of the conversation. Your speech audio is not stored by us; we keep only the resulting text as part of your conversation. The agent's spoken reply is synthesized separately, as described in the FAL entry above. Deepgram processes data under its published terms, with model-improvement use disabled on every request we make; we have requested a data processing agreement
• Black Forest Labs (BFL) - image generation models, reached through FAL (see FAL above) or, when the FAL path is unavailable, through Replicate, which serves the same models (see Replicate). We do not call BFL directly
• Stability AI - used for music and sound-effect generation. It receives your description of the sound and, when you edit or vary a track, a track Sonic generated; it does not receive audio you record or upload. We requested a data processing agreement; Stability AI has told us it does not offer one, and its published terms of service and privacy policy govern its processing
• DataForSEO - provides business-listing, review, and search-result data
• Google - YouTube search API; only the search terms you enter are sent
• Unsplash - provides stock-photo search results when you use the built-in photo picker. When we search on your behalf, Unsplash receives only the search keyword. When a photo is chosen, whether by you or by the Service when it builds a page or slide, our servers tell Unsplash which photo was chosen, as its terms require; that request carries no information about you. Photos you choose are not copied to our servers: they continue to be served from Unsplash's image network, so a browser that displays one (yours in the editor, or a visitor's on a published site) connects to Unsplash directly and Unsplash receives that device's IP address and user agent. A photo credit is displayed automatically on every page of a published website that shows an Unsplash image
• Cloudmersive - used for virus scanning uploaded files. Cloudmersive receives the contents of files you upload for scanning and processes them under its published terms of service rather than under a separate data processing agreement with us
• Upstash - caching for analytics, business-listing, review, and search-result responses (see Section 4.3)
• Vercel - website hosting
When you connect a third-party account, we transmit data between the Service and that third party on your behalf and under your authorization:
• Google (Google Analytics 4 and Google Search Console) - read-only access (analytics.readonly and webmasters.readonly scopes) to the GA4 properties and GSC sites you connect. Our handling of this data is governed by the Limited Use commitments in Section 4.8.1.
Innovique Studio's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Specifically, with respect to data obtained through the Google Analytics 4 and Google Search Console APIs:
• We use this data solely to provide and improve the user-facing features you have connected it to: populating your analytics dashboards, generating the reports and page-level analyses you request, producing your weekly summary and the recurring checks for unusual changes, and enabling our AI agents to answer your questions about your own analytics and search performance. It is also used in other features of the Service when you choose to use it there, as described below.
• We transfer this data only as necessary to provide those user-facing features. Within our own systems it is stored and processed by Supabase. Responses retrieved from the Google APIs are also held briefly in a cache operated by Upstash, for up to four hours for Google Analytics 4 data and up to six hours for Google Search Console data, so that repeated views of the same report do not re-query your account. For the features above, it is transmitted outside those systems only to three providers. Anthropic generates the responses that use it. OpenAI is used where an Anthropic request cannot be completed, and it also converts text saved to your workspace's agent memory, and the searches an agent runs against that memory, into search vectors, so an analytics figure saved to memory reaches it in that form. Anthropic and OpenAI each process it under a data processing agreement. Anthropic's limits its use to providing its service to us, which excludes training any model; OpenAI's commitment not to train on data sent through its API is in its API data-usage policy rather than that agreement. Resend delivers the anomaly alert emails to the workspace members who turned those alerts on, so it carries the metric values that changed, under its data processing agreement. We also disclose it where necessary to comply with applicable law, or as part of a merger, acquisition, or sale of assets with notice to you as described in Section 5.2.
• It goes further only when you, or another member of your workspace, choose to use it in another feature. Nothing in this paragraph happens by default. For example: having an agent's reply read aloud sends the text of that reply to FAL for voice synthesis; handing an answer to another agent, or turning it into an image, a presentation, a website or an email, sends it to the providers that feature uses; adding a Search Console query to rank tracking in the SEO Lab sends that query to DataForSEO, our search data provider, each time rankings are checked; and an agent you ask to look up a business or a competitor may use a query or a page from your data as its search term. In each case only what that feature needs is sent, and the provider processes it under the terms described in its entry in Section 4.
• We do not use this data for advertising purposes, and we do not sell it or share it for cross-context behavioral advertising.
• We do not use this data to develop, improve, or train any AI or machine-learning model, whether our own or those of any third party. Anthropic and OpenAI do not use it for training either, on the terms described above. When you choose to use it in a feature another provider performs, that provider handles it under the agreement or published terms its entry in Section 4 describes, and Section 15 describes the training commitments those providers have made.
• We do not allow humans to read this data, except: with your affirmative agreement for specific data; as necessary for security purposes such as investigating abuse; to comply with applicable law; or where the data has been aggregated and de-identified.
You can revoke our access to your Google data at any time from within the Service or from your Google Account permissions page.
• Sentry - error tracking and crash reporting. Sentry receives error details, stack traces, and browser/device information, your user ID when you are signed in (but not your name or email address), and sampled session replays when errors occur, so we can triage issues affecting specific accounts; we configure Sentry to reduce the amount of personal information captured where feasible.
• Datadog (Real User Monitoring) - application performance monitoring and user-experience analytics, including a 20% sample of session replays, long-task events, and resource-load metrics. Your user ID (but not your name or email address) is attached to sessions to support debugging; we configure Datadog to limit the collection of personal information where feasible.
• Cloudflare Turnstile - bot-protection CAPTCHA presented during account sign-up, sign-in, password reset, and verification-email resend, and on the forms (contact forms, newsletter sign-ups and other hosted forms) and public booking pages published from the Service. Cloudflare processes connection metadata, including IP address, as part of challenge evaluation. On a published website the challenge runs in the visitor's browser, so Cloudflare receives that visitor's connection details; we serve the challenge through our own systems rather than embedding it directly, so the address of the website being visited is not disclosed to Cloudflare. Cloudflare also provides the media storage described in Section 6: media files generated or uploaded in the Service (images, audio, the files you upload, and brand-model training images and model files) are stored as private objects in Cloudflare's object storage and are served through time-limited signed links.
• Google Analytics - visitor behaviour analysis and traffic measurement on the Marketing Website. Subject to Google's Privacy Policy. You may opt out using the Google Analytics Opt-out Browser Add-on (https://tools.google.com/dlpage/gaoptout).
A small number of authorized Poardal Software personnel can access Customer Data where it is necessary to operate and support the Service. Access is limited to what the task requires and follows the principle of least privilege.
• Support and troubleshooting. Where you report a problem with generated output, our support staff can view the prompt you submitted and the prompt our agent constructed from it, so that they can diagnose why the result fell short. This access ends when you delete the generated images: the prompts are held with the image, so once it is gone they are no longer visible to us.
• Account administration. Our staff can view a workspace's membership, subscription, plan, and usage records, including token consumption, recent agent activity, and storage totals, in order to administer accounts, apply plan changes and credits, and investigate billing questions. They can send a sign-in link or a password-reset link to the email address already on an account. Our staff cannot sign in to the Service as you or act on your behalf inside your workspace, and they cannot read the content of your conversations.
• Security and legal. Access necessary to investigate a security incident or abuse, or to comply with a legal obligation.
Changes our personnel make to an account or a workspace, and the sign-in and password-reset links they send, are recorded in our audit log. Data obtained through the Google Analytics 4 and Google Search Console APIs is subject to the separate and stricter commitments in Section 4.8.1.
In a commercial-relationship context, we may share Business Contact information with the applicable Customer workspace administrators and with our professional advisors (such as legal, audit, tax, and accounting advisors) where necessary for contracting, billing, compliance, or relationship management. We may also share information as needed to facilitate a transaction you request (for example, coordinating a demo or support engagement). We do not share personal information with third parties for their own direct-marketing purposes.
We may disclose your information if required to do so by law or in response to valid legal requests, including court orders, subpoenas, government or regulatory agency requests, or to protect our legal rights, defend against legal claims, or prevent fraud or security threats.
In the event of a merger, acquisition, reorganization, or sale of all or a portion of our assets, your information may be transferred as part of that transaction. We will notify you via email and/or a prominent notice in the Service of any change in ownership or data-handling practices.
We may share your information for other purposes with your explicit, informed consent.
• Application database and file storage: Supabase (managed PostgreSQL with row-level security), hosted in a United States region. Supabase storage buckets hold uploaded brand assets, other user-uploaded files, and media files written there when a transfer to our primary media storage does not complete, as described below.
• Application front-end: hosted by Netlify
• Published websites: hosted by Vercel (content that you elect to publish from the Website Builder is served from Vercel's infrastructure), at a subdomain of sites-pro.com or at a custom domain you connect
• Marketing Website (innoviquestudio.com and innoviquestudio.ca, which serve the same site): published from the Service and hosted by Vercel, in the same way as the websites our Customers publish; analytics via Google Analytics
• Media files: generated images and audio, and the media files you upload, are stored in Cloudflare R2. If an upload to R2 does not complete, the file is written to our Supabase storage instead so that your work is not interrupted, and is moved to R2 in a later batch.
Because the primary application database is hosted in the United States, your personal information will be stored and processed in the United States and may be accessed from other jurisdictions where our service providers operate. If you are located outside the United States (for example, in Canada, the European Economic Area, the United Kingdom, or Switzerland), the use of the Service necessarily involves a transfer of your personal information to the United States and, where applicable, to other jurisdictions where our sub-processors operate.
All data transmitted between your device and our servers is encrypted using TLS (Transport Layer Security). Data transmitted between our edge functions and third-party sub-processors is likewise transmitted over TLS. A small number of features connect your browser directly to a provider rather than through our servers, so that they can work in real time or load faster: the voice conversation feature described in Section 4.6, and the media and font sources described in Sections 4.7 and 9. Those connections are also encrypted, and the provider receives your device's connection details directly, as each of those sections explains.
Each workspace on the platform is logically isolated via a Tenant ID and row-level security (RLS) policies enforced at the database level. Access-control (including support for parent-to-child workspace role inheritance for agency accounts) ensure that users can only access data belonging to workspaces to which they have been authorized.
We retain your personal information for as long as necessary to fulfill the purposes outlined in this Privacy Policy, unless a longer retention period is required or permitted by law.
We retain your account and workspace information for as long as your account is active or as needed to provide the Service. When a workspace's subscription ends, other than because the workspace is deleted or is left with no owner or administrator (section 6.4.3), the workspace is suspended and its content is kept for 90 days so that it can be restored if the subscription is renewed. For a workspace whose subscription had already ended when this version of the policy took effect, the 90 days run from that date. After 90 days the workspace and its content are permanently deleted in the same way as a workspace deletion (section 6.4.3). We email the workspace's owners before that happens.
When you request deletion of your account (from your account settings, or by writing to privacy@innoviquestudio.com), we verify the request and complete it within 30 days. On completion:
• Your name, email address, password, avatar, multi-factor authentication settings, active sessions, and other profile fields are deleted or replaced with anonymized values, and your account is permanently disabled. The account record itself is retained in anonymized form so that references to it in audit and consent records resolve to "Deleted user" rather than to you
• Your workspace memberships are removed. Chat conversations are workspace records: where a workspace you belonged to still has another owner or administrator (in that workspace or, for a workspace that belongs to an agency account, in its parent workspace), your conversations there, together with the files you uploaded to them (the text kept from documents, the images kept for image work, and the audio kept from uploads and recordings), are transferred to that person and retained by the workspace; where no owner or administrator remains in the workspace or its parent workspace, your conversations there, including their messages and the files you uploaded to them, are deleted. Other Customer Data you created inside a workspace, such as generated content, images you uploaded to a workspace gallery, brand guidelines, and knowledge-base entries, is workspace property and is retained by the workspace with your authorship anonymized. A workspace left with no owner or administrator by your deletion is suspended and deleted 30 days later, together with everything retained in it, as described in section 6.4.3
• Integrations you connected are disconnected: the Google Analytics and Search Console connections made with your Google account. We delete the stored credentials and, where the provider supports it, ask the provider to revoke them. A workspace owner can reconnect any integration with another account
• Your consent choices (what you agreed to, and when) are retained as evidence of those choices, with the identifying details captured at the time removed. Communication preferences no longer apply once the account is disabled
• The help assistant's log of your questions and your voice preferences are deleted. If you made a privacy request (for a copy of your data, or for this deletion), the IP addresses recorded when you verified it and when you downloaded your data are removed from the request record; the record itself is kept as described in section 6.4.4
• Service providers that received your details while your account was active are not sent a separate deletion instruction when your account is deleted. What each holds leaves under its own retention period: error and performance records that carry your user ID (and, for records made before this version of the policy took effect, your email address) age out of Sentry and Datadog within 90 days (section 6.4.5); the Stripe customer record created when your workspace set up billing is kept with the billing records described in section 6.4.4; and Resend keeps the content and delivery logs of the transactional emails we sent you for the period set out in its privacy policy, acting as an independent controller for routing information (section 4.5)
A workspace owner can delete a workspace from its settings. The workspace is removed from the account immediately, and its records and stored files are permanently deleted, usually within minutes. Deleting the workspace that holds a subscription ends the subscription immediately; the rest of the current billing period is not refunded (see the Terms of Service, section 4.4). A workspace whose last owner or administrator leaves it or deletes their account is suspended: its subscription is cancelled on the same terms, and the workspace, with any workspaces nested under it, is deleted in the same way 30 days later unless a new owner is appointed through support before then. Write to privacy@innoviquestudio.com before then if you need something from it. Workspaces created through the developer API are deleted through the API instead; they enter a 30-day recovery period, after which they are permanently deleted in the same way. Deleting a workspace takes any website published from it offline, and removes its database records (chat sessions, analytics connections, generated content, audit reports, and team membership records, on a cascading basis) and every file stored for it (images, audio, video, documents, brand assets, and trained brand models together with their training images). If you cannot delete a workspace yourself, write to privacy@innoviquestudio.com and we will do it for you.
Even after account or workspace deletion, certain records may be retained where necessary for legal, regulatory, accounting, or legitimate business purposes, including:
• Billing and tax records: Stripe customer and subscription identifiers, invoices, and related records, retained as required by applicable tax and accounting laws (typically up to 7 years)
• Billing correspondence: support tickets you opened in the billing category, and any support ticket placed under a legal hold because of a dispute or complaint, are retained with the billing records for the same period, including after account deletion and after the workspace they were opened in is deleted (any files attached to them are deleted with the workspace). Other support tickets you opened are redacted on account deletion: the subject, the body, the details you reported, our replies, and any resolution note are replaced with placeholders. A file or screenshot you attached to a ticket is kept with it, readable only by our support staff, until the workspace the ticket was opened in is deleted, at which point it is deleted with the workspace
• Privacy request records: the record of a privacy request you made (the request, its verification and completion events, and the email address it was made from) is retained indefinitely as evidence that we handled it. It is an accountability record, and it is the proof that your request was answered. The IP addresses recorded during verification and download are removed from it when your account is deleted
• Audit log entries: the record of actions described in section 2.2 may be retained as part of the workspace's audit trail for security and compliance purposes. Entries are retained for 24 months from the date of the action, after which they are purged
• Security and abuse-prevention records: logs used to investigate and respond to security incidents or abuse
• Published content: a website you published to a live URL stays online until you unpublish it through the Service, until the subscription of the workspace it was published from ends, when we may take it offline, or until that workspace is deleted, which takes it offline as described in section 6.4.3. A workspace closed because no owner or administrator remains stays online during the 30 days before it is deleted. Content you took out of the Service and published elsewhere yourself, such as an article you copied into your own publishing tool, stays where you published it. Published content may also remain cached by third parties (search engines, link previewers, content delivery networks)
• Workspaces whose subscription has ended, other than those deleted or left without an owner or administrator (section 6.4.3): kept for 90 days, then deleted as described in section 6.4.1; copies in database backups are removed on the backup schedule below
• Error and performance logs: retained for up to 90 days in Sentry and Datadog before being purged
• Help assistant question log: retained for 6 months, then deleted
• Agent memory: retained until it is cleared, or until the workspace is deleted. Archived items remain stored until they are cleared. Optional automatic archiving withdraws an item from what agents actively use once it is 90 days old and has never been retrieved or rated; it does not delete it
• Cached third-party responses: GA4 responses are cached for up to 4 hours, GSC responses for up to 6 hours, and business-listing, review, and search-ranking responses for up to 24 hours, in Upstash Redis, before being evicted. A place-name-to-location-code lookup is cached for up to 30 days, because those codes are fixed reference data rather than information about you
• Database backups: encrypted backups are retained for approximately 30 days before being securely deleted; deleted data may persist in these backups until the backup is purged
• Financial records: retained as required by tax and accounting laws (typically 7 years)
• Session records: active session data (session identifiers, authentication tokens, creation and expiry times, last-activity timestamps) is retained for the duration of the session. Sign-in and authentication history used for security review, including IP address, browser user-agent and event type, is retained for up to 90 days
Data that has been de-identified or aggregated so that it cannot reasonably be used to identify you may be retained indefinitely for product improvement purposes.
We implement comprehensive technical and organizational measures to protect your personal information against unauthorized access, alteration, disclosure, or destruction.
• Encryption of data in transit using TLS
• Encryption of sensitive fields at rest, including OAuth access and refresh tokens, using AES-256-GCM with keys derived via HKDF
• Encryption of Supabase-managed database backups at rest
• Password hashing using industry-standard cryptographic algorithms (bcrypt, managed by Supabase)
• Multi-factor authentication (MFA) via time-based one-time passwords (TOTP) available on all accounts
• Row-Level Security (RLS) policies enforced at the database level, with helper functions that correctly honor parent-to-child workspace role inheritance
• CORS origin allowlisting on edge functions that serve signed-in users, restricting responses to our own known origins; endpoints that are intentionally public and embeddable on customer websites (the review widget, and the contact form of a website published from the Service) accept requests from any origin by design and never process browser credentials
• Server-Side Request Forgery (SSRF) protection on any feature that fetches user-provided URLs (for example, brand-guidelines website crawling and audit tools) - private IP ranges, loopback addresses, cloud metadata endpoints, and non-HTTP schemes are blocked
• Magic-byte validation on uploaded files (in addition to MIME-type checking) before processing
• Strict Content Security Policy and additional HTTP security headers (HSTS, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy) on the application
• Input sanitization and DOMPurify-based output encoding to mitigate cross-site scripting
• Generic error responses to clients (no internal error details, stack traces, or database errors are returned)
• HMAC-signed, time-limited tokens for OAuth state validation
• Automated error detection and tracking
• Real-time application performance monitoring
• CAPTCHA (Cloudflare Turnstile) on account sign-up, sign-in, password reset and verification-email resend, and on the forms and public booking pages published from the Service, to mitigate automated abuse
• Audit log entries for significant workspace events that workspace users cannot alter or delete
• Access controls based on the principle of least privilege
• Documented incident-response procedures
• Regular security reviews and testing of the Service
• Due-diligence reviews of our sub-processors
• Enterprise-grade cloud infrastructure (Supabase, Netlify, Vercel)
• Primary application database hosted in the United States with managed backups
While we protect your personal information using commercially reasonable administrative, technical and organizational measures, no method of transmission over the internet or electronic storage is 100% secure. We cannot guarantee absolute security, but we are committed to maintaining appropriate safeguards. If you believe your account has been compromised, please contact us immediately at privacy@innoviquestudio.com.
We maintain a documented incident response plan and a register of confidentiality incidents affecting personal information, including incidents that do not meet a notification threshold.
If we become aware of a breach of our security safeguards involving personal information for which we are responsible, we investigate promptly and take steps to contain and remediate it. Where the breach creates a real risk of significant harm, or for individuals in Quebec a risk of serious injury, we will report it to the Office of the Privacy Commissioner of Canada and, where applicable, the Commission d'accès à l'information du Québec, and we will notify the individuals affected as soon as feasible. Where a breach affects residents of a United States state, we will provide notification as that state's law requires.
A notification to you will tell you what happened, what information was involved, what we have done about it, and what you can do.
Where we process personal information on behalf of a Customer, we will notify that Customer without undue delay after becoming aware of a breach affecting its data, and will provide the information reasonably necessary for the Customer to meet its own notification obligations.
If you believe your account has been compromised, contact us immediately at privacy@innoviquestudio.com.
Depending on your location and your relationship with us (for example, Business Contact versus Authorized User), you may have certain rights regarding your personal information. Where we process Customer Data on behalf of a Customer, privacy requests about that Customer Data should generally be directed to the Customer (your organization) because the Customer controls the data and Poardal Software Inc. processes it as a service provider/processor. Where we act as a controller (for example, for Business Contact information, billing, and marketing website interactions), you may submit requests directly to us as described below.
You have the right to request a copy of the personal information we hold about you. Within the Service you can view your account details, download individual AI responses, and export Workshop content and brand guidelines from the features that hold them. Chat conversations are held for the workspace they took place in and are available from that workspace's owner. What we keep from a file you attach to a conversation depends on the file. For a text or CSV file, the text the conversation read from it is kept with the chat so the assistant can refer back to it; it is not shown or downloadable, and it is deleted with the chat. For a PDF, and for an image attached to an ordinary conversation, the file itself is not kept: we record its name, type and size, and the conversation's reply. An image you attach for image work is kept only where the conversation needs it again, which is when the assistant asks you a follow-up question before generating; where the assistant has what it needs and generates straight away, your image is sent to the image provider and is not kept. Images you upload to a workspace gallery are always kept. Anything kept in these ways is workspace content: it appears in that workspace's image gallery, where every member can see and download it, and where you or a workspace owner can delete it. Deleting the conversation removes the images kept from it. An image a conversation used once and did not need again is not kept at all. For a complete copy of the personal information we hold about you as controller, use the request option in your account settings or contact us at privacy@innoviquestudio.com; we deliver it within the time limits in Section 8.9 as a downloadable ZIP archive containing the full dataset as a JSON file, a readable overview page, and a plain-text guide to what the archive holds and what was withheld from it. JSON is a structured, commonly used, machine-readable format, so you can open it with any tool that reads JSON or hand it to another provider.
Your workspace's agent memory is not part of that archive. It is workspace content rather than a record about you, in the same way conversations and Workshop items are, so it is reached inside the Service rather than through an access request. A workspace owner or administrator can review everything held in it from the memory page in workspace settings, where each item is listed with its title, its summary, where it came from and when it was added, and can archive or clear it. The content that reaches memory comes from items saved or published in the workspace, which stay available through the routes described above. The vector representations generated from that content are internal to how agents search it and are not exported; they are a numerical form of the same content, not additional information about you.
You have the right to request correction of inaccurate personal information we hold about you. You can update most information (including your name, timezone, notification preferences, MFA configuration, and workspace metadata) directly through your account and workspace settings.
• Authorized Users: You can request deletion of your account at any time from your account settings; we verify the request and complete it within 30 days. If your deletion request relates to Customer Data inside a workspace that is controlled by your organization (for example, a client workspace at an agency), please contact your workspace owner or the Customer directly, as they control that data
• Deleting a conversation does not delete anything that was saved from it into your workspace's agent memory. Memory is managed separately, from the memory page in workspace settings, as described in Section 15. Two things do follow their source: withdrawing a strategy section in Compass, and deleting a CRM note or the contact it belongs to, each delete the memory item derived from it.
• Business Contacts and website visitors: You may submit a deletion request to privacy@innoviquestudio.com.
Certain records may be retained after deletion where required or permitted by law and for legitimate business purposes (for example, billing records, audit logs, and backups pending the scheduled purge).
You have the right to request that we restrict the processing of your personal information in certain circumstances.
You have the right to object to the processing of your personal information for certain purposes, including direct marketing.
Where processing is based on your consent (for example, optional analytics or marketing communications where required by law), you may withdraw your consent at any time. Much of our processing in a commercial-relationship context is not consent-based (for example, processing necessary to provide the Service, administer accounts, provide support, and maintain security) and will continue after consent is withdrawn where another lawful basis applies.
You may disconnect a Google (GA4/GSC) integration at any time from within the Service. When you do so, we delete the corresponding credentials from our systems and ask Google to revoke them. You can also revoke Google OAuth permissions at any time from your Google Account permissions page (https://myaccount.google.com/permissions).
You can opt out of non-essential email notifications through your notification preferences. Transactional emails related to account security, password resets, team invitations, and critical service notifications cannot be opted out of while your account remains active.
If you are a Business Contact or your request relates to information we control, contact us at privacy@innoviquestudio.com. If you are an Authorized User and your request relates to Customer Data in the Service, please contact your workspace owner or the Customer first. If no owner or administrator of that workspace remains, the workspace is closed and its content deleted 30 days after the last of them left; contact us at privacy@innoviquestudio.com before then if you need something from it.
We will respond to your request within 30 days (or 45 days for requests under the CCPA/CPRA). Where the CCPA applies, we will acknowledge your request within 10 business days of receiving it and respond substantively within 45 days. We may need to verify your identity before processing your request.
We use cookies, browser local storage, session storage, and similar technologies to collect and store information when you use the Service and visit our website.
The Service stores information in your browser. Some of it is strictly necessary and the rest is a convenience, and the difference matters to you: you can clear the second group and carry on using the Service. None of it is advertising or tracking technology, and none of it is shared with a third party. Analytics and monitoring are separate and are described in 9.3.
Strictly necessary. Without these we cannot sign you in, protect your account, or be sure you are running working code. Blocking them prevents use of the Service.
• Local storage - authentication session: the access and refresh tokens issued by Supabase Auth that keep you signed in. They are stored in your browser's local storage, sent to our API over HTTPS as a bearer token on each request, and cleared when you sign out
• Local storage - sign-in attempt throttle: counts failed sign-in, password-reset and verification attempts made from this browser and pauses further attempts for a short period. A security control against password guessing
• Session storage - chunk-reload timestamp: detects stale application code after we release a new version and prompts a refresh, so you are not left on a broken page
Functional, and not strictly necessary. These remember choices you have already made so you do not have to make them again. Clear them in your browser at any time and the Service keeps working; you are simply returned to the defaults.
• Local storage - selected workspace: your last-active workspace, so you return to it on your next visit
• Local storage - theme preference: your light or dark theme choice
• Local storage - selected data property: which Google Analytics and Search Console property is chosen for each workspace
• Local storage - website builder environment: which environment is selected in the website builder for each workspace
• Local storage - navigation state: which sidebar groups you left expanded
• Local storage - editor state: in-progress work in the SVG editor and certain other editors, so a reload does not lose it
• Local storage - recently used colours: the colours you last picked in the website and email editors
• Local storage - last automatic scan: when an automatic check last ran for a workspace, so it is not repeated too often
• Session storage - dismissed notices: which in-app banners you have dismissed, for the rest of that session
Cloudflare Turnstile is used on the sign-up and sign-in forms, on password reset and verification-email resend, and on the forms and public booking pages published from the Service, to mitigate automated abuse. Turnstile may set cookies and read limited device characteristics solely to evaluate whether a challenge should be presented.
• Sentry collects error events (including stack traces, browser and device information, and a session replay when an error occurs) and includes your user ID when you are signed in, but not your name or email address, so we can triage issues affecting specific accounts; we configure Sentry to reduce the amount of personal information captured where feasible. The replay begins up to one minute before the error and continues for the rest of that browsing session, for no more than one hour, with text, typing and images masked. No replay is recorded for a session in which no error occurs.
• Datadog Real User Monitoring collects performance metrics, long-task events, resource-loading events, user interactions, and a 20% sample of session replays. Your user ID, but not your name or email address, is attached to sessions; sensitive inputs are masked by default and media is blocked in replays.
Why error monitoring is always on. Error monitoring cannot be switched off, because we could not keep the Service working and secure without it, and it runs only when something goes wrong. For users in Canada, we rely on your implied consent to it, given that purpose and this disclosure (Section 14). Where the GDPR or UK GDPR applies, we rely on our legitimate interest in the security and reliability of the Service (Section 13). Performance and usage monitoring is different: it samples sessions whether or not anything goes wrong, so it is optional, and you can switch it off under Usage analytics in your account settings.
We use Google Analytics on our marketing website to understand how visitors interact with the site. Google Analytics collects information such as:
• Pages visited and time spent on each page
• Traffic sources and referring websites
• Device and browser information
• Approximate geographic location (city/country level)
Google Analytics uses cookies stored in your browser. This analytics is applied only to the Marketing Website, not to the Service itself.
• Most web browsers are set to accept cookies by default
• You can configure your browser to remove or reject cookies, but doing so may affect functionality of the Service
• You can opt out of Google Analytics tracking on our marketing website using the Google Analytics Opt-out Browser Add-on (https://tools.google.com/dlpage/gaoptout)
• We do not use third-party advertising cookies, retargeting tools, or cross-site behavioral tracking technologies on the Service or the marketing website
Our primary application database is hosted in the United States. In addition, many of our sub-processors, including most of our AI providers, monitoring tools, and payment and email providers, are headquartered in or process data in the United States and, in some cases, the European Union. As a result, personal information we collect may be transferred to, stored, and processed in countries outside your country of residence, including the United States.
While your personal information is in another country it is subject to the laws of that country, and it may be accessible to the courts, law enforcement agencies, and national security authorities of that country under their own legal processes, without notice to you or to us. This is true of any service that processes personal information outside Canada, and we tell you because you are entitled to know it before you decide to use the Service.
Where personal information is transferred internationally, we take steps designed to provide an appropriate level of protection in the circumstances, which may include contractual protections (such as data processing terms and, where applicable, Standard Contractual Clauses approved by the European Commission or equivalent mechanisms), vendor due diligence, and technical measures such as encryption to protect data in transit and at rest.
Service Provider Locations (non-exhaustive)
• Supabase: primary database hosted in the United States
• Netlify: United States
• Vercel: United States
• Stripe: United States and Europe
• Anthropic, OpenAI, Google (Gemini), Replicate, Recraft, FAL, Stability AI, Deepgram: primarily United States and the European Union
• Upstash: data stored in Canada (Central region); Upstash is a United States company
• Resend: United States
• Sentry: United States
• Datadog: United States and Europe
• Cloudflare (Turnstile and media storage): global edge network, United States-headquartered
• DataForSEO: primarily the European Union
• Unsplash: primarily the United States
• Cloudmersive: United States
• Google Analytics: United States
• Google (GA4/GSC APIs): United States (subject to Google's data-processing infrastructure)
We select and review our service providers through a vendor due-diligence process that assesses their data-protection terms, security measures, and international-transfer safeguards. Some providers maintain independent certifications such as SOC 2 or ISO 27001; others commit to contractual security measures instead. Providing the Service necessarily involves transferring your information to countries outside your country of residence, and we make those transfers under the safeguards described in this section.
The Service is intended for use by professionals in a business context. It is not directed to, and we do not knowingly collect personal information from, individuals under the age of 16. Our Terms of Service require that you be at least 16 years of age to use the Service.
If you are a parent or guardian and believe that your child has provided us with personal information, please contact us at privacy@innoviquestudio.com. If we become aware that we have collected personal information from a child under the age of 16 without appropriate consent, we will take steps to delete that information promptly.
If you are a California resident, you have specific rights under the California Consumer Privacy Act, as amended by the California Privacy Rights Act (collectively, "CCPA"):
Right to Know. You have the right to request information about the categories and specific pieces of personal information we have collected about you, the sources, our business purpose, and the third parties with whom we share it.
Right to Delete. You have the right to request deletion of your personal information, subject to certain exceptions.
Right to Correct. You have the right to request correction of inaccurate personal information.
Right to Opt-Out of Sale or Sharing. You have the right to opt out of the "sale" or "sharing" of your personal information. We do not sell your personal information, and we do not share your personal information for cross-context behavioral advertising.
Right to Limit Use of Sensitive Personal Information. We do collect one category of sensitive personal information: your account log-in credentials, meaning your password in hashed form and your multi-factor authentication configuration where you have enabled it. We use them only to authenticate you and to secure your account, which are purposes the CCPA exempts from the right to limit. We do not use sensitive personal information to infer characteristics about you, and we do not use it for any other purpose that would require you to be offered a right to limit such use.
Right to Non-Discrimination. We will not discriminate against you for exercising your privacy rights.
Shine the Light. We do not share personal information with third parties for their direct-marketing purposes.
Authorized Agent. You may designate an authorized agent to make a request on your behalf. We may require verification that you have authorized the agent.
Response Time. We will acknowledge your request within 10 business days of receiving it and respond to verifiable consumer requests within 45 days.
To exercise your CCPA rights, please contact us at privacy@innoviquestudio.com.
If you are located in the European Economic Area (EEA), United Kingdom, or Switzerland, you have additional rights under the General Data Protection Regulation ("GDPR") and the UK GDPR.
Legal Basis for Processing. We process your personal information based on one or more of the following legal bases:
• Contract: processing necessary to perform our contract with you or your organization (for example, providing the Service and maintaining your account)
• Legitimate Interests: processing necessary for our legitimate business interests (for example, fraud prevention, security monitoring, audit logging, product improvement, and direct marketing to business contacts) and balanced against your rights and freedoms
• Consent: processing based on your explicit consent (for example, certain optional analytics or marketing communications, which you may withdraw at any time)
• Legal Obligation: processing necessary to comply with legal requirements
Data Controller. Depending on the context, Poardal Software Inc. may act as a controller (for example, for account administration, billing, marketing website interactions, and security) or as a processor/service provider (for example, when processing Customer Data within the Service on a Customer's instructions). Where Poardal Software Inc. acts as a controller, Poardal Software Inc. is the data controller for that processing.
Data Protection Officer. For questions about our data-protection practices, please contact our Privacy Officer at privacy@innoviquestudio.com.
Your GDPR Rights. In addition to the rights listed in the privacy rights described in this policy, you have the right to:
• Receive information about our processing activities in a concise and transparent manner
• Object to processing based on legitimate interests
• Lodge a complaint with your local data-protection supervisory authority if you are not satisfied with our response
If you are located in Canada, your personal information is protected under the Personal Information Protection and Electronic Documents Act ("PIPEDA") and applicable provincial privacy legislation, including Quebec's Act Respecting the Protection of Personal Information in the Private Sector ("Law 25," formerly Bill 64). Poardal Software Inc. is committed to full compliance with these requirements.
If you have concerns about our privacy practices, please contact our Privacy Officer at privacy@innoviquestudio.com. We will investigate and respond within 30 days.
If you are not satisfied with our response, you may file a complaint with:
Office of the Privacy Commissioner of Canada
30 Victoria Street
Gatineau, Quebec K1A 1H3
Phone: 1-800-282-1376
Website: www.priv.gc.ca
Commission d'accès à l'information du Québec (CAI) (for Quebec residents)
Phone: 1-888-528-7741
Website: www.cai.gouv.qc.ca
Innovique Studio is an AI-powered platform, and many of its core features rely on third-party AI service providers to generate text, images, audio, and other outputs in response to your prompts and inputs.
• AI providers currently used. Anthropic (Claude), OpenAI, Google (Gemini), Replicate, Recraft, FAL, Stability AI, and Deepgram (speech-to-text). Certain models are accessed through FAL's infrastructure, including Black Forest Labs image models and other models operated by FAL's partners; FAL is contractually committed to not using data routed to those partners for training. Where a provider processes data under its published terms rather than a data processing agreement, its entry in Section 4 says so.
• Use of your data for model training. We do not use Customer Data to train generalized or foundation AI models for our own or any other customer's benefit. The Brand Model feature is the one case in which Customer Data trains a model at all: when you choose to train a brand model, the images you select and the captions generated from them are sent to our model-training provider to produce a private model that is available only in your workspace, is never used to serve another workspace, and is deleted when you delete it or the workspace. Where a data processing agreement is in place with an AI provider, it prevents the provider from using Customer Data submitted through our API integrations to train their foundation or public models, except that OpenAI's commitment not to train on that data is in its API data-usage policy rather than its agreement; where a provider processes under its published terms, as the entries in Section 4.6 indicate, we rely on those terms and on the provider's opt-out controls. Each provider's data-handling commitments are set out in their own terms, which we review as part of our vendor due diligence.
• Agent memory. Your workspace can keep a memory of content saved or published in it, so that our agents can refer to it when producing new work. Saved items are summarized and converted into vector representations by our AI providers, then stored in your workspace's own records, reachable only by that workspace's members and agents. Memory is never shared between workspaces. Email addresses, phone numbers, and web addresses are removed from content before it is sent to those providers; names are not.
Content published from the Service enters memory automatically: blog posts, presentations, and social posts you publish, and email campaigns you send. So do the strategy sections you save in Compass and the notes, calls, and meetings you log against a CRM contact. Everything else enters only when you choose to add it, from a chat message or a Workshop item, and handing a chat message to another agent saves that message as well. A workspace using our developer API can add items through it.
Because a workspace's memory is shared, anything in it is available to every member of that workspace and to the agents they use. Decide on that basis whether a response containing analytics figures, client details, or other sensitive material belongs there.
Once an item is in memory it is independent of the conversation it came from. Deleting that conversation does not remove it, so you are not forced to keep old chats in order to keep what was learned from them. Withdrawing a Compass strategy section, or deleting a CRM note or the contact it belongs to, does remove the item derived from it.
A workspace owner or administrator manages memory from the memory page in workspace settings, where every item is listed and can be archived, which withdraws it from what agents actively use while keeping it stored, or cleared, which deletes the content and the vector representations generated from it. Memory can be cleared entirely, or only items of a chosen type or older than a chosen date, and it can be rebuilt from the workspace's current content at any time. Automatic archiving of items that are 90 days old and have never been used can be switched on. Memory belongs to the workspace and is deleted when the workspace is deleted.
• Retention by AI providers. AI providers may retain inputs and outputs temporarily for limited operational purposes (for example, abuse monitoring and service reliability). Retention periods are governed by each provider's terms.
• Human review of AI outputs. AI outputs can be inaccurate, incomplete, or inappropriate for your intended use. You remain responsible for reviewing and validating any AI-generated content before you rely on it, publish it, or share it externally. Do not submit content to an AI agent that you are not authorized to share.
• Automated decision-making. We do not use AI, profiling, or analysis of your personal information to make decisions about you that produce legal or similarly significant effects. We do apply one automated rule to your account's billing status: if a subscription payment remains unpaid for 14 days, access to the workspace is paused automatically. We send reminders during that period, the first of them 3 days after the payment fails. This is the operation of your subscription agreement rather than an assessment of you or your data, and no profile of you is used to reach it. Your workspace and its content are retained while access is paused. A workspace owner can open the billing portal from the paused workspace to resolve payment; other members are shown how to reach their workspace owner. Access is restored when payment is resolved. You can contact us at privacy@innoviquestudio.com at any point to discuss a pause on your account. You can also ask us for the main factors that led to it, tell us anything you think we should take into account, and ask that a person review the pause rather than leaving it to the rule. These are available to you wherever you are located, and we respond within the time limits in Section 8.9.
If you have questions, concerns, or requests regarding this Privacy Policy or our privacy practices, please contact us:
General Privacy Inquiries
Email: privacy@innoviquestudio.com
Data Protection Officer / Privacy Officer
Email: privacy@innoviquestudio.com
Mailing Address
Poardal Software Inc.
Attn: Privacy Officer - Innovique Studio
1463 Ontario St
Burlington, ON L7S 1G6
Canada
