Instaflow Privacy Policy

Last updated: 11 November 2026

This policy explains what personal data Instaflow collects, why we collect it, who we share it with, how long we keep it and what rights you have. Instaflow is a tool that businesses use to build and publish landing pages for their online stores with the help of AI. We are an Irish company, so the EU General Data Protection Regulation (GDPR) and the Irish Data Protection Acts apply to us. Instaflow is for businesses only. Shoppers who visit a page that one of our Merchants publishes are mainly covered by that Merchant's privacy policy. We explain how this works in section 3.

1. Who we are

The controller of your personal data is Propeller Digital Limited, trading as Instaflow ("Instaflow", "we", "us"). We are a private company limited by shares, registered in Ireland under number 784240, with our registered office at Unit 20, Platform 94, Mervue Business & Technology Park, Wellpark Road, Galway, H91 F9PX, Ireland.

For anything about privacy, email privacy@instaflow.ai. You can also write to us at our registered office.

2. Words we use

  • Merchant: the business that signs up for Instaflow. Our Terms and Data Processing Agreement call the same business the "Customer".
  • Authorised User: a person who uses Instaflow for a Merchant, such as the account owner or a team member.
  • Visitor: a shopper or other person who visits a landing page that a Merchant has published with Instaflow.
  • Website: our marketing site at https://instaflow.ai.
  • App: the Instaflow application at https://app.instaflow.ai.
  • Published pages: landing pages we host for Merchants at {brand}.instaflow.cc/{page} or on a Merchant's own subdomain.

3. Who this policy covers

This policy covers personal data that we control about:

  1. Website visitors and people who use our contact form: people who visit instaflow.ai or send us a message through the contact form at instaflow.ai/contact.
  2. App users and team members: Authorised Users who sign up for, are invited to or use the App.
  3. Shopify merchants: Merchants and their staff who connect a Shopify store to Instaflow, including through the Shopify App Store app "Instaflow AI Landing Pages".
  4. People who contact us, for example by email to support@instaflow.ai.

Shoppers on Merchants' pages

When you visit a page that a Merchant has published with Instaflow, the Merchant is the controller of the personal data collected about you there, and we act as the Merchant's processor. This covers:

  • the analytics we run on the page for the Merchant (the instaflow_visitor_id cookie and the page events described in our Cookie Policy); and
  • the order, checkout and refund information Shopify sends us about purchases linked to the page.

We only use this data to provide the service to the Merchant, under our Data Processing Agreement. The Merchant's privacy policy explains how it uses your data. Each page links to the store's own privacy policy in its footer. Please contact the Merchant first about your data. If you contact us, we will pass your request to the Merchant and help them answer it.

Shopify runs the shop's cart and checkout. Shopify is an independent controller of the data it collects, and Shopify's own privacy policy applies to it.

What we do to limit Visitor data is described in section 6.

4. What we collect, where it comes from, why, and our lawful basis

The lawful bases we rely on under GDPR Article 6(1) are:

  • Contract: the processing is needed to provide the service you or your business signed up for, or to take steps you asked for before signing up.
  • Legitimate interests: the processing is needed for our legitimate interests (or those of a third party), and your interests and rights don't override them. You can object to this processing at any time (see section 13).
  • Legal obligation: we must process the data to comply with the law.
  • Consent: you have given consent, which you can withdraw at any time.

Where the Authorised User is not the person who signed the contract with us (for example an invited team member), we rely on legitimate interests instead of contract for their account data. Our interest is in providing the service the Merchant has bought.

4.1 Website visitors and people who use our contact form

Data Source Purpose Lawful basis
IP address and request details (such as browser type and the page requested) Your browser, received by our hosting provider Cloudflare. Cloudflare Workers logs are kept only for /api requests, such as contact form submissions Delivering the Website and keeping it secure Legitimate interests (running a secure website)
IP address Your browser, received by Google when the Website loads fonts from Google Fonts Displaying the Website's fonts Legitimate interests (presenting the Website). See the drafting note below
Theme and animation settings Stored in your own browser (local storage); we don't receive them Remembering your display choices Legitimate interests. See our Cookie Policy
Contact form: your name, email address, company type (Shopify brand, agency, freelance media buyer or other), monthly ad spend band and your message (up to 5,000 characters) You, when you send the contact form Answering your message. We store you as a contact in our email provider Loops, and Loops emails our team a notification with your details and message Legitimate interests (answering enquiries); contract (steps you asked for before signing up) where you ask about using Instaflow
How you heard about us (referral source) You, if you answer the optional follow-up question after sending the form Understanding where our enquiries come from Legitimate interests (understanding demand)
A record that you contacted us through the Website ("website-contact") Created by us Keeping track of where contacts came from Legitimate interests

Sending the contact form does not sign you up for marketing emails. We add you to Loops as a contact who is unsubscribed from marketing. If you are already a contact in Loops, we don't change your saved details; your message reaches us only as a one-off event and notification email.

4.2 App users and team members

Data Source Purpose Lawful basis
Signup details: preferred name, email address, password (not needed if you sign up with Google), and your confirmation that you accept the Terms and this Privacy Policy, with the time you accepted You Creating and running your account Contract
Google sign-in: if you choose "Continue with Google", your Google account ID, email address (which Google must have verified), name and, for Google Workspace accounts, your organisation's domain (hosted domain). We store your Google account ID with your account. If you already have a verified Instaflow account with the same email address, we link it to your Google account Google, when you choose to sign in with Google. Google acts as an independent controller as the identity provider; see Google's privacy policy Creating your account and letting you sign in with Google Contract
Password: we store only a one-way Argon2 hash, never the password itself Created from your password Letting you sign in securely Contract
Product and onboarding emails (Loops): your email address, user ID and first name, and events about your use of Instaflow (see section 8) You, and created by us as you use the App Sending you emails about getting started with and using Instaflow Legitimate interests (helping you use the service you signed up for), with an unsubscribe link in every email. Emails tied to your service, such as about your subscription, rely on contract
Marketing consent: whether you ticked "Send me Instaflow news, tips and offers by email" at signup, and when You, at signup Sending you news, tips and offers by email Consent, which you can withdraw at any time
Normalised email identity (for Gmail addresses, dots and "+tags" are ignored, and googlemail.com counts as gmail.com) Created from your email address Stopping duplicate accounts and abuse of the free plan Legitimate interests (preventing abuse)
Disposable email check Your email domain, checked against a public list of disposable email providers Refusing throwaway sign-ups Legitimate interests (preventing abuse)
Bot check (Cloudflare Turnstile): a challenge token and your IP address, sent to Cloudflare when you sign up Your browser and our server Stopping automated and fraudulent sign-ups Legitimate interests (security and preventing fraud)
Email verification and password reset codes, each valid for 10 minutes Created by us and sent to your email Confirming your email address and letting you reset your password Contract
Two-factor authentication: your TOTP secret key and a recovery code, both stored encrypted Created when you sign up or set up 2FA Protecting your account Contract; legitimate interests (security)
Sessions: a hashed session token, its expiry date and whether you completed 2FA in that session. We do not store your IP address or browser details with your session Created when you sign in Keeping you signed in Contract
Team and role: the teams you belong to, your role (owner, admin, editor or custom) and permissions Created by us and by team owners and admins Running team access Contract; legitimate interests (for invited members)
Team invitations: the invitee's email address, the role offered, who sent the invite and when it expires (7 days) The team member who sends the invite Inviting people to a team. The invite email shows the invitee the inviter's email address and the team name Legitimate interests (letting Merchants add their staff)
Chat messages and AI inputs: what you type into the App (up to 50,000 characters per message), page briefs, specifications and copy You Generating and editing landing pages Contract
Team file library: images, fonts and text files that team members upload (up to 3 MB each and 100 files per team), with their file name, type, size, checksum and who uploaded them. We keep them in private storage You and your team members Giving the AI visual references and background material, and using your images and fonts on your pages Contract
Generated work: page code, copy, AI-generated images, store overviews and product page insights produced by the AI Created by us with AI Providing the service Contract
Display settings: for example the theme, sidebar state and last selected store, stored in your browser Your browser Remembering your settings Legitimate interests. See our Cookie Policy
Billing (Stripe): the team owner's email address, Stripe customer and subscription IDs, plan and subscription status. Stripe collects card details directly; we never see full card numbers You and Stripe Taking payment and managing subscriptions Contract; legal obligation (tax and accounting records)
Error and session replay data (see section 7) Your browser and our servers Finding and fixing faults and keeping the App secure Consent for Better Stack's tag in your browser (withdraw any time with "Cookie settings"). Legitimate interests for error reports from our servers
Support correspondence: your name, email address and what you tell us You Answering your questions and fixing problems Contract; legitimate interests

You can change your preferred name in your account settings.

4.3 Shopify merchants

Data Source Purpose Lawful basis
Your store's myshopify domain and primary domain, and how the store was connected Shopify and you Linking your store to your Instaflow team Contract
Shopify access and refresh tokens (stored encrypted) and the storefront access token Shopify, when you install the app or connect the store Reading your products and store content and creating carts and checkouts on your pages Contract
Product, collection, inventory, selling plan, metaobject and store content data, plus your brand data and store pages (which we render to text with Cloudflare Browser Rendering) Shopify and your public store Building pages and preparing store overviews and product page insights Contract
The merchant contact email in Shopify compliance requests Shopify Handling privacy requests from your shoppers (see section 16) Legal obligation; contract
Order, checkout and refund data about your shoppers Shopify webhooks Reporting sales from your pages. We are your processor for this data (see section 3) Decided by the Merchant as controller

4.4 Visitors on published pages (we are the processor)

For completeness, this is the data we process for Merchants on their published pages. The Merchant decides the lawful basis.

Data Source Purpose
Random visitor ID (kept for 180 days) and session ID; page URL (including UTM tags and ad click IDs), page title, referrer; page views, product views, add-to-cart and begin-checkout events with product, cart, currency and amount details The Visitor's browser, only after analytics consent is given through Shopify Page analytics for the Merchant
Approximate location (country, region, city) and device, browser and operating system type Derived from the request by Cloudflare and by our parser Page analytics for the Merchant
Order totals, statuses, timestamps, cart and checkout tokens, line items, refunds, and hashed (pseudonymised) order email and customer ID Shopify order, checkout and refund webhooks Sales reporting for the Merchant

Special categories of data

We don't ask for, and you should not upload, sensitive data (such as health, religion or political views) or personal data about other people that your page doesn't need, in chats or in files you upload to your file library.

5. How we use AI

Instaflow uses AI models to write page copy, design and code pages, analyse stores and products and suggest improvements.

  • Model provider. We send prompts to OpenAI through its API. A prompt can include your chat messages, brief text, files from your team's file library, product and store data, brand data, store overviews, page code and the output of build commands. We do not send your store's storefront token to the AI. For research, the model can search the public web.
  • AI images. To generate or edit images for your pages, we send prompts and product images (for example from your Shopify catalogue) to OpenAI's image model. We store generated images at public web addresses, because your published pages show them.
  • Files on your pages. The AI can copy images and fonts from your file library into a page. They become public when you publish that page.
  • No storage at OpenAI by our request. We set store: false on our requests, which tells OpenAI not to store the request and response for later retrieval. OpenAI keeps prompts and outputs in its abuse-monitoring logs for up to 30 days and then deletes them, unless the law requires it to keep them longer. OpenAI also scans uploaded images automatically for child sexual abuse material and may keep a flagged image for review. OpenAI processes this data in the United States.
  • No training unless the Merchant opts in. By default, we do not use your content, the pages we generate or data from Shopify to train or improve AI. If a Merchant's account owner turns on "Help improve Instaflow", we may use that Merchant's pages, briefs and aggregated page performance to improve our AI features, including to fine-tune models we use only for Instaflow. Before we do, we take reasonable steps to remove personal data, and we never use data about Visitors or shoppers for this. The setting can be turned off at any time (see section 12 of our Terms). Under OpenAI's API terms, OpenAI does not train its own models on API data by default.
  • AI tracing (Langfuse). We use Langfuse to monitor and debug our AI features and to manage prompts. Every trace includes identifiers: your user ID, team ID, store and shop domain, product ID and handle, page, generation, run and message IDs, plus the AI step and token usage. For some AI tasks the trace also includes the prompt and the AI's output:
    • Page title generation and web research for store overviews and product page insights: prompts and outputs are sent.
    • Page specification and copywriting: prompts and outputs are sent only when the brief has no reference files.
    • The coding agent that builds and edits pages: no prompts or outputs are sent, only identifiers and usage. We delete this data from Langfuse after 90 days.
  • Build sandboxes (E2B). We build and preview pages in isolated sandboxes run by E2B. A sandbox receives the page's code and the store configuration needed to build it (the store domain, the product and, for stores connected through the Shopify app, the storefront token). Preview sandboxes shut down 10 minutes after last use. Snapshots are deleted when the page is deleted.
  • You check the output. AI output can be wrong. You must review every page before you publish it.

6. How we limit data about Visitors

As a processor for Merchants, we have built the following limits into the product:

  • Analytics only with consent. Our analytics run only on pages of stores connected through the Shopify app, and only once Shopify's Customer Privacy API reports that the Visitor has allowed analytics. Pages without a Shopify app connection load no tracking at all.
  • No IP addresses in analytics. We don't store Visitors' IP addresses in analytics. We keep only the country, region and city that Cloudflare derives from the request.
  • No raw user agent. We turn the browser's user agent into device, browser and operating system type and discard the original string.
  • Hashed identifiers for orders. We store the order email and Shopify customer ID only as keyed HMAC-SHA256 hashes. Before we store an order, we remove the billing and shipping addresses, the customer object, email, contact email, phone number, browser IP and client details.
  • Short raw retention. Raw analytics events are deleted after 1 day. Aggregated analytics and order data are deleted after 25 months.

7. Security and error monitoring

We protect personal data with technical and organisational measures that include: encryption in transit (HTTPS); encryption of Shopify access tokens, 2FA keys, recovery codes and stored Shopify compliance requests; one-way password hashing; optional two-factor authentication, required again in each new session once you turn it on; and role-based access within teams.

To find and fix faults, we use Better Stack:

  • On our servers, error reports are sent to Better Stack and are set up to leave out user details, cookies, request and response bodies, IP-address and forwarding headers, query parameters, AI inputs and outputs, and database query data.
  • In your browser, if you accept cookies in the App's cookie banner, the App loads Better Stack's JavaScript tag. We don't load it unless you accept, and you can withdraw consent at any time with the "Cookie settings" link in the App. Depending on its settings, it can collect errors, session replays, web vitals (page speed measurements), console logs, web analytics events, anonymous clicks and form submissions, and a browser fingerprint that can recognise the same browser across visits. A replay is a reconstruction of what happened on the page (such as page changes, clicks and scrolling) that helps us see what led to an error. Error reports also include technical details such as your browser type and the page you were on. The tag's settings are configured in Better Stack, not in the App: it records replays of every session in which you accepted the tag, and masks the text and form inputs shown on screen. The App does not tell Better Stack who you are: it doesn't send your name, email address or user ID to the tag.

We also log technical events about AI runs (such as the step, status, error codes, duration and internal IDs, but no content you wrote) to Better Stack, and our hosting providers keep server logs.

No system is perfectly secure. If a personal data breach is likely to put your rights at risk, we will tell the Data Protection Commission and, where the law requires, tell you.

8. Emails we send

  • Account emails. We send the emails needed to run your account: email verification codes, password reset codes, two-factor codes and team invitations. They come from noreply@notifications.instaflow.ai through our email provider Resend.
  • Product and onboarding emails. When you verify your email address, or sign up with Google, we add you as a contact in our email provider Loops, with your email address, user ID and first name. We rely on legitimate interests for these emails, and on contract where an email is about your service (such as your subscription). You can unsubscribe from them at any time with the link in each email. So we can send you helpful emails at the right time, we tell Loops when certain things happen:
    • for you: when you sign up, connect a Shopify store and publish a page;
    • for team owners: when a subscription starts, changes plan (with the new plan), has a failed payment, is set to cancel and is cancelled.
  • Marketing emails. We send news, tips and offers only if you ticked the box "Send me Instaflow news, tips and offers by email" when you signed up. We rely on your consent. You can withdraw it at any time with the unsubscribe link in each email or by emailing privacy@instaflow.ai. If you sign up with Google, we don't add you to our marketing list.
  • Contact form. If you send us a message through the Website's contact form, we reply to you by email. The form doesn't sign you up for marketing (see section 4.1).
  • Support emails you send to us are handled in our Google Workspace mailbox.
  • After you delete your account, we keep your Loops contact (email address, first name, user ID and past events) and stop sending new events about you. You can unsubscribe from all our emails at any time with the link in any email, or ask us to delete the contact by emailing privacy@instaflow.ai.

9. Who we share data with

We don't sell your personal data. We share it only as described here. The full list of our service providers, with their location and what they do, is on our Subprocessors page.

Category Who What for
Hosting and infrastructure Render (App and database, US); Cloudflare (published pages, analytics collection, file storage in the EU, custom domains, bot protection, page rendering, and hosting the Website on Cloudflare Workers) Running the Website, App and published pages
Analytics database Tinybird (Frankfurt, Germany) Storing Visitor analytics and order data for Merchants
AI OpenAI (models); Langfuse (AI tracing and prompts, EU); E2B (build sandboxes) AI features (section 5)
Monitoring Better Stack (error tracking, session replay and logs, US) Security and fixing faults (section 7)
Email Resend (account emails); Loops (product, onboarding and marketing emails, and contact form messages); Google (Workspace email and Website fonts) Sending and receiving email
Google sign-in Google Signing you in if you choose "Continue with Google". Google is an independent controller as the identity provider
Payments Stripe Payments. Stripe acts as an independent controller for most of its processing; see Stripe's privacy policy
Shopify Shopify Store connection, carts and checkout, and privacy tools on published pages. Shopify is an independent controller
Your team Other members of your Instaflow team Team members can see each other's names, email addresses, roles and the pages and chats in the team
Professional advisers Lawyers, accountants and auditors Advice and compliance, under confidentiality
Authorities Courts, regulators and law enforcement Where the law requires it, or to protect our rights, our users or the public
Business transfers A buyer or investor and their advisers If we sell, merge or restructure all or part of our business, under confidentiality

10. Your data and published pages

Your published pages stay online until you unpublish them. You can't delete your account or team while pages are published or a custom domain is connected.

11. International transfers

Some of our service providers process personal data outside the European Economic Area (EEA), mainly in the United States:

  • Render hosts the App and its database in the United States (Oregon).
  • Better Stack stores error reports, session replays and logs in the United States (US West).
  • Resend (account emails), Loops (product, onboarding and marketing emails, and contact form messages), Google (sign-in), OpenAI (AI models) and Stripe process data in the United States. E2B runs our build sandboxes in the United States.
  • Cloudflare runs a global network, so requests may be handled at the location nearest to the user. Our Cloudflare file storage is restricted to the EU.

Tinybird (Frankfurt) and Langfuse (EU) store our data in the EU.

When we transfer personal data to the United States, we rely on the EU-U.S. Data Privacy Framework where the provider is certified under it, and otherwise on the European Commission's Standard Contractual Clauses (SCCs) with additional safeguards where needed. For OpenAI, we contract with OpenAI Ireland Ltd, and transfers to OpenAI's US affiliates rely on SCCs. You can ask us for more information on these safeguards, including a copy of the relevant clauses, at privacy@instaflow.ai.

12. How long we keep data

We keep personal data only as long as we need it for the purposes in this policy, then delete or anonymise it.

Data How long
Account data (name, email, password hash, 2FA data, team memberships) While your account exists. Deleted when you delete your account
Team data (pages, chats, store connections) While the team exists. Deleted when the team is deleted. Chat messages you wrote in a team stay with the team after you delete your account, without your name attached
Team file library Until a team member deletes the file, or the team is deleted. If the person who uploaded a file deletes their account, the file stays with the team without their name attached
AI-generated images Not deleted automatically. They stay in public storage after the page, team or account is deleted
Loops contact for product and onboarding emails (email, user ID, first name and events) Kept after you delete your account, until you ask us to delete it. You can unsubscribe at any time
Marketing consent records Until you withdraw consent, then 3 years as proof of your consent and withdrawal
Contact form messages and details (in Loops) 2 years after the last contact
Website request logs (Cloudflare Workers, /api requests only) 7 days
Login sessions 30 days, renewed while you keep using the App
Email verification and password reset codes 10 minutes
Team invitations Valid for 7 days. The invitation record is kept until it is withdrawn or the team is deleted
Shopify connections that are never linked to an account Tokens removed after 1 hour
Shopify tokens after you uninstall the app Removed when Shopify tells us the app was uninstalled
Store data after a Shopify shop deletion request (shop/redact) Deleted within 30 days (see section 16)
Visitor analytics (raw events) 1 day
Visitor analytics (aggregated), orders, line items and refunds 25 months
AI run logs at Better Stack 3 days (metrics: 30 days)
Error reports and session replays at Better Stack Error reports and session replays: 90 days. Web events and browser logs from the tag: 3 days
AI traces at Langfuse 90 days
Prompts and outputs at OpenAI (abuse monitoring) Up to 30 days, unless the law requires longer
Server logs (Render, Cloudflare) Up to 14 days at Render, and 3 days for database logs copied to Better Stack. 7 days for Cloudflare Workers logs
Billing and tax records 6 years from the end of the financial year they relate to, as Irish tax and company law requires
Free-plan usage records per account owner Your free credit balance: until you delete your account (it survives team deletion so the allowance isn't given twice). Records of which Shopify stores have claimed a free generation: kept while we offer the Free plan, for the same reason
Support correspondence 2 years after the last contact
Backups Up to 7 days after deletion from live systems (database point-in-time recovery at Render)

13. Your rights

Under the GDPR you have the right to:

  • Access the personal data we hold about you and get a copy.
  • Correct inaccurate or incomplete data. You can change your preferred name in your account settings.
  • Delete your data where there is no good reason for us to keep it. You can delete your account in your account settings. You'll need to unpublish your pages first and make sure each of your teams has another owner or is deleted.
  • Restrict our use of your data, for example while we check its accuracy.
  • Data portability: receive data you gave us in a machine-readable format, or have it sent to another provider, where we process it on the basis of contract or consent.
  • Object at any time to processing based on our legitimate interests. We will stop unless we have compelling legitimate grounds that override your interests, or we need the data for legal claims. You can always object to direct marketing.
  • Withdraw consent at any time where we rely on consent. This doesn't affect processing that happened before.

To use any of these rights, email privacy@instaflow.ai. We may ask you to confirm your identity. We will reply within one month. We may extend this by two more months for complex requests, and if so we'll tell you why.

If you are a Visitor on a Merchant's page, please send your request to the Merchant (see section 3).

Complaints. You can complain to the Data Protection Commission (DPC), Ireland's supervisory authority, at www.dataprotection.ie or 21 Fitzwilliam Square South, Dublin 2, D02 RD28, Ireland. You can also complain to the supervisory authority where you live or work. We'd appreciate the chance to deal with your concern first.

14. Automated decision-making

We don't make decisions about you based solely on automated processing that have legal or similarly significant effects. Our AI generates content for Merchants. It doesn't make decisions about individuals. Automated checks at signup (the Turnstile bot check and the disposable email check) can block a sign-up attempt. If you think you were blocked by mistake, contact support@instaflow.ai and a person will review it.

15. Businesses only, and children

Instaflow is a business tool. It is for people acting for a trade, business or profession. It is not for consumers and not for anyone under 18. We don't knowingly collect personal data from children. If you believe a child has given us personal data, contact privacy@instaflow.ai and we will delete it.

16. Shopify merchants

If you connect a Shopify store, we access the Shopify data described in section 4.3 under the permissions you approve at install. We use it only to provide Instaflow to you. We do not use it to train or improve AI unless you turn on the opt-in setting described in section 5.

We support Shopify's mandatory privacy webhooks and complete each request within 30 days:

  • customers/data_request: when one of your shoppers asks for their data, we prepare the data we hold about them and send it to the store owner, so you can answer the shopper.
  • customers/redact: we delete that shopper's orders, line items, refunds and linked analytics events, matched by their hashed customer ID or email or by order ID.
  • shop/redact: sent by Shopify 48 hours after you uninstall the app. We delete the store's analytics and order data, store overviews and product insights, the AI generations for that store, and your Shopify connection. We skip this if you have reinstalled the app. Your landing pages and publications are not deleted by this webhook; they stay in your team until you delete them.
  • app/uninstalled: we remove your Shopify access tokens and disconnect your stores straight away.

We keep the webhook requests themselves encrypted while we process them. For order and checkout data about your shoppers we are your processor, under our Data Processing Agreement.

17. Changes to this policy

We may update this policy when our services or the law change. We will change the "Last updated" date at the top. If a change is material, we will tell Authorised Users by email or in the App before it takes effect, and where the law requires consent we'll ask for it.

18. Contact us

Propeller Digital Limited (trading as Instaflow) Unit 20, Platform 94, Mervue Business & Technology Park, Wellpark Road, Galway, H91 F9PX, Ireland Registered in Ireland, number 784240 Email: privacy@instaflow.ai (privacy) or support@instaflow.ai (general support)


Portions of this policy were adapted from a template prepared and made publicly available by General Legal, PC ("General Legal"). The template is provided for general reference purposes only and does not constitute legal advice. General Legal has not reviewed, and takes no position on, any modifications made to this document.