Privacy Policy
How Mighty Lucky Ventures Pty Ltd (ABN 51 653 328 628), trading as Heista collects, uses, shares and protects personal information when you use Heista. Each section opens with a short summary in plain English; the full wording beneath it is what applies.
Last updated:
1. About this Policy
In short
This Policy covers heista.co, the Heista app, API and browser extension. We handle personal information under Australian privacy law, and we don’t sell it.
- This Policy applies to personal information handled by Mighty Lucky Ventures Pty Ltd (ABN 51 653 328 628), trading as Heista (“Heista”, “we”, “us”) through heista.co, the Heista web app, the Heista API, the Heista browser extension and our communications (together, the “Service”).
- We handle personal information in accordance with the Privacy Act 1988 (Cth) and the Australian Privacy Principles. Where other privacy laws apply to you, such as the GDPR, section 11 explains your additional rights.
- We do not sell personal information.
- Heista is a business tool. When an organisation puts personal information about other people into Heista, such as its clients, customers or staff, that organisation decides what is collected and why, and we handle that information on its behalf to provide the Service (see section 6).
2. Information we collect
In short
We collect your account details, the content you put into Heista, billing records, and information about how you use the Service and the device you use.
Account information
- Examples
- Name, email address, profile picture (if you sign in with Google), password (stored only as a secure hash by our authentication provider), role and workspace membership
- Source
- You, or Google if you sign in with Google
Workspace content
- Examples
- Brands, briefs, documents and files you upload, prompts, chats with Heista’s AI, generated outputs, boards, saved assets and links you submit for decoding
- Source
- You and your workspace members
Billing information
- Examples
- Plan, seats, add-ons, usage of brands, library items and storage, Credit purchases and balances, invoices, billing address and business tax ID. Card details are collected by Stripe; we never see or store full card numbers
- Source
- You and Stripe
Usage information
- Examples
- Pages and features used, actions taken, generation history and costs, and error reports
- Source
- Collected automatically
Device and technical information
- Examples
- IP address, approximate location derived from it, browser, operating system, device type and referring page
- Source
- Collected automatically
Communications
- Examples
- Support requests, feedback and emails you send us
- Source
- You
Applications and business contacts
- Examples
- Creative Partner applications and agreements (name, work email, agency, role, website, social or course links you share, your answer, and when you accepted the partner terms), and business contact details of people we may contact about Heista
- Source
- You, or public sources and business-contact data providers
Referral information
- Examples
- If you arrive through a partner’s referral link, a referral identifier that is passed to our checkout
- Source
- Our affiliate tracking provider
Connected accounts
- Examples
- If you connect a Meta ad account: account IDs, campaigns, ad creatives and performance data for the accounts you select. If you connect Foreplay: your Foreplay API key (stored encrypted) and the saved ads you import
- Source
- Meta or Foreplay, with your authorisation
Consent records
- Examples
- When you accept an in-app acknowledgement, such as for reference uploads: what you accepted, which version and when
- Source
- You
API information
- Examples
- API key metadata (keys are stored only as hashes), request logs, costs and IP addresses
- Source
- Collected automatically
| Category | Examples | Source |
|---|---|---|
| Account information | Name, email address, profile picture (if you sign in with Google), password (stored only as a secure hash by our authentication provider), role and workspace membership | You, or Google if you sign in with Google |
| Workspace content | Brands, briefs, documents and files you upload, prompts, chats with Heista’s AI, generated outputs, boards, saved assets and links you submit for decoding | You and your workspace members |
| Billing information | Plan, seats, add-ons, usage of brands, library items and storage, Credit purchases and balances, invoices, billing address and business tax ID. Card details are collected by Stripe; we never see or store full card numbers | You and Stripe |
| Usage information | Pages and features used, actions taken, generation history and costs, and error reports | Collected automatically |
| Device and technical information | IP address, approximate location derived from it, browser, operating system, device type and referring page | Collected automatically |
| Communications | Support requests, feedback and emails you send us | You |
| Applications and business contacts | Creative Partner applications and agreements (name, work email, agency, role, website, social or course links you share, your answer, and when you accepted the partner terms), and business contact details of people we may contact about Heista | You, or public sources and business-contact data providers |
| Referral information | If you arrive through a partner’s referral link, a referral identifier that is passed to our checkout | Our affiliate tracking provider |
| Connected accounts | If you connect a Meta ad account: account IDs, campaigns, ad creatives and performance data for the accounts you select. If you connect Foreplay: your Foreplay API key (stored encrypted) and the saved ads you import | Meta or Foreplay, with your authorisation |
| Consent records | When you accept an in-app acknowledgement, such as for reference uploads: what you accepted, which version and when | You |
| API information | API key metadata (keys are stored only as hashes), request logs, costs and IP addresses | Collected automatically |
You can choose not to provide some information, but we need account and billing information to provide the Service. Please do not upload the types of sensitive information listed in section 11.2 of our Terms of Service.
3. How we use information
In short
We use information to run the Service, bill you, keep the platform secure, support you, and improve Heista. We don’t train AI models on your content.
- To provide the Service: running the AI features you use, storing your workspace, showing your work to your workspace members, and processing payments.
- To bill accurately: recording usage and costs, issuing tax invoices and preventing billing fraud.
- To keep the Service secure: authenticating users, detecting abuse, enforcing usage limits and investigating incidents.
- To support you: answering questions and resolving problems.
- To communicate with you: service, billing and security messages, and product updates. You can opt out of marketing emails at any time; service messages are part of the Service.
- To run our partner and sales activities: reviewing Creative Partner applications, attributing referrals, and contacting businesses that may want to use Heista. You can ask us to stop contacting you at any time.
- To improve the Service: understanding how features are used and fixing errors, using analytics and aggregated information.
- To meet legal obligations, including tax record-keeping, and to establish or defend legal claims.
AI training
Heista does not use your content, prompts, uploads or outputs to train AI models. Section 5 explains how AI providers handle the requests we send them.
Automated decisions
Heista’s AI produces creative and strategic suggestions for people to review and decide on. Some routine decisions are made automatically by our systems, using your account, workspace, usage and billing information: whether an action can start, based on your Credit balance, plan allowances, member spending limits and rate limits; whether a request is blocked by an AI provider’s safety filters; whether to pause an action that looks like automated misuse; and pausing Credit spending while a payment is disputed with a bank. These checks affect only the action or payment in question. We do not suspend or close an account, or refuse a refund, by computer program alone; a person reviews those decisions. You can ask us to review any automated outcome by emailing us.
5. AI processing
In short
When you use an AI feature, we send only what that task needs to the provider of the model being used. Providers are instructed not to train on it wherever they support that. Processing may happen outside Australia.
- Each AI request contains what the task needs: your prompt, any references or documents you attach, and relevant context from your workspace, such as brand information.
- Requests are routed through our AI gateway provider, Vercel, to the provider of the model being used. Vercel does not retain or train on the requests that pass through its gateway.
- Text and chat requests carry an instruction that the provider must not train on them, and are only served by providers that have agreed to that. Image and video requests carry the same instruction wherever the provider supports it. A small number of providers do not offer this; they are identified on our Subprocessors page, and content sent to them may be used under their own terms.
- AI providers may keep requests for a limited period under their own terms, for example to detect abuse (commonly up to 30 days, and up to 55 days for some providers).
- When you upload a document, an AI model reads it so that Heista can extract its text, which is then kept in your workspace for your team’s AI tools to use.
6. Personal information in your workspace
In short
If you put other people’s personal information into Heista, such as client or customer details, you decide what goes in and why. We handle it only to provide the Service to you.
Organisations using Heista may include personal information about other people in their workspace content, such as names, images or voices in briefs, references and uploads. The organisation is responsible for having the right to use that information and for giving any notices and obtaining any consents required. We handle that information on the organisation’s behalf, as its service provider (a “processor” under the GDPR), only to provide the Service, on its instructions and as described in this Policy. We do not use it for our own purposes, and we delete it with the workspace as described in section 8. If you are an individual whose information is in a customer’s workspace, please contact that organisation first; we will help where we can.
7. Where information is stored and sent
In short
Heista’s data is stored in Sydney, Australia. Some service providers, including AI providers, process information in other countries, such as the United States.
- Heista’s database, sign-in system and file storage are hosted by Supabase in Sydney, Australia. Our application runs on Vercel’s Sydney servers and is delivered through Vercel’s global network.
- Payments (Stripe), product analytics (PostHog), email delivery (Resend), support requests (Linear), affiliate tracking (the script that runs today is Rewardful’s) and rate limiting (Upstash) are handled by providers based in the United States.
- Media sent to some video models is placed briefly in Vercel’s file storage, at a temporary link that is deleted when the render finishes.
- AI requests are processed by the provider of the model being used, on whichever of its servers is available. Depending on the provider, this may be in the United States, Canada, Europe, the United Kingdom, Singapore, China or other countries. The Subprocessors page lists each AI provider and where it is based.
- Before disclosing personal information overseas, we take reasonable steps to ensure the recipient handles it consistently with the Australian Privacy Principles, including through the contractual terms of the providers we use.
- Dedicated hosting in the UK, US or EU is available to Enterprise customers by agreement.
8. How long we keep information
In short
We keep your workspace data while your account is open. When you delete your account, you have 90 days to change your mind, then it is permanently deleted. Some records are kept longer where the law requires.
Account and workspace data, including uploads, decodes of ads you uploaded, and generated files
- How long we keep it
- While your account is open. After you delete your account, 90 days for recovery, then permanently deleted
Work you created in a shared workspace
- How long we keep it
- Belongs to the workspace. It stays when you leave the workspace or delete your account (your name is removed from it when you delete your account), and is deleted when the workspace itself is deleted
Items you delete in the app
- How long we keep it
- Brand documents and their extracted text: removed immediately. Boards, brands and Visual Flow flows: permanently removed 30 days after deletion. Deleting a flow does not delete the images and videos it made; they stay in Assets until you delete them
Database backups
- How long we keep it
- Rolling daily backups kept for up to 7 days
Server logs
- How long we keep it
- Short-term, generally no more than 30 days
Product analytics events
- How long we keep it
- Up to 12 months
Brand activity history
- How long we keep it
- 90 days
Meta ad account data
- How long we keep it
- Until you disconnect, then deleted within 30 days
Support requests
- How long we keep it
- As long as needed to support you and keep records of our dealings
Billing and tax records
- How long we keep it
- 7 years, as required by Australian tax law, kept separately from your user account
Record of an account deletion
- How long we keep it
- 7 years, with identifying details removed after 120 days
Consent records
- How long we keep it
- While your account exists; deleted with your account
Decodes of public ads created from a link
- How long we keep it
- Kept by Heista as part of its shared ad library, including after your account is deleted. When a workspace is deleted, these decodes move to Heista’s own library and anything linking them to you or your workspace is removed
| Information | How long we keep it |
|---|---|
| Account and workspace data, including uploads, decodes of ads you uploaded, and generated files | While your account is open. After you delete your account, 90 days for recovery, then permanently deleted |
| Work you created in a shared workspace | Belongs to the workspace. It stays when you leave the workspace or delete your account (your name is removed from it when you delete your account), and is deleted when the workspace itself is deleted |
| Items you delete in the app | Brand documents and their extracted text: removed immediately. Boards, brands and Visual Flow flows: permanently removed 30 days after deletion. Deleting a flow does not delete the images and videos it made; they stay in Assets until you delete them |
| Database backups | Rolling daily backups kept for up to 7 days |
| Server logs | Short-term, generally no more than 30 days |
| Product analytics events | Up to 12 months |
| Brand activity history | 90 days |
| Meta ad account data | Until you disconnect, then deleted within 30 days |
| Support requests | As long as needed to support you and keep records of our dealings |
| Billing and tax records | 7 years, as required by Australian tax law, kept separately from your user account |
| Record of an account deletion | 7 years, with identifying details removed after 120 days |
| Consent records | While your account exists; deleted with your account |
| Decodes of public ads created from a link | Kept by Heista as part of its shared ad library, including after your account is deleted. When a workspace is deleted, these decodes move to Heista’s own library and anything linking them to you or your workspace is removed |
We may keep information for longer where the law requires it or to establish or defend legal claims. Some third-party providers keep copies under their own retention terms, for example Stripe for payment records.
You can ask us to delete your analytics profile and support history at any time by emailing support@heista.co. The Data deletion page explains how to delete your account and connected data.
9. How we protect information
In short
Your data is encrypted, each workspace is isolated at the database level, and administrative access is protected by multi-factor authentication. No system is perfectly secure, and we will tell you if a serious breach affects you.
- Encryption in transit (TLS) on all connections, and encryption at rest (AES-256) for the database and file storage.
- Workspace isolation enforced by the database itself (Postgres Row-Level Security on every table), so one workspace cannot read another’s data.
- Private file storage for your uploads and workspace files, accessed through signed, time-limited links. Public ad-library media, workspace branding assets and some previews use public links.
- Multi-factor authentication on administrative access to our core infrastructure (hosting, database, source code and identity), and production access restricted to authorised personnel.
- Passwords checked against known breach data, and API keys stored only as hashes.
- A web application firewall, rate limiting and automated monitoring.
No method of transmitting or storing information is completely secure, and we cannot guarantee absolute security.
Data breaches
If we become aware of a data breach that is likely to result in serious harm to individuals, we will assess it promptly and notify affected individuals and the Office of the Australian Information Commissioner as required by the Notifiable Data Breaches scheme, and other regulators where required.
11. Your rights and choices
In short
You can ask to access, correct or delete your personal information. We acknowledge requests within 5 business days and respond within 30 days.
- Access and correction. You can ask for a copy of the personal information we hold about you, and ask us to correct it. You can update most account information yourself in Settings.
- Deletion. You can delete your account in Settings, or ask us to delete specific information. Some information is kept where the law requires (section 8).
- Marketing. You can unsubscribe from marketing emails using the link in any email.
- Anonymity. You can browse our public website without identifying yourself, but you need an account to use the app.
To make a request, email support@heista.co with the subject line “Privacy request”. We may need to verify your identity. We acknowledge requests within 5 business days and respond within 30 days. We do not charge for making a request.
If you are in the EU or UK
If the GDPR or UK GDPR applies to you, you also have the right to object to or restrict certain processing, to data portability, and to complain to your local data protection authority. We rely on performance of our contract with you, our legitimate interests in operating, securing and improving the Service, legal obligations and, where requested, your consent. The controller is Mighty Lucky Ventures Pty Ltd (ABN 51 653 328 628), trading as Heista.
12. Heista browser extension
In short
The extension only reads a page when you choose to save something from it. It doesn’t collect your browsing history or run analytics.
- When you click save, the extension reads the ad or post you selected (text, images, video links, author and page address) and sends it to your Heista workspace.
- It stores your sign-in session in your browser so you stay signed in.
- It does not collect browsing history or keystrokes, does not run in the background on pages you don’t save from, and does not include analytics or third-party tracking.
- Permissions: storage (your session), activeTab and context menus (to save the page you choose), alarms (to refresh your session) and access to supported social sites (to add save buttons).
- The extension does not load remote code. It communicates only with Heista’s servers over HTTPS.
13. Children
In short
Heista is not for anyone under 18.
The Service is not intended for people under 18, and we do not knowingly collect their personal information. If you believe a child has given us personal information, contact support@heista.co and we will delete it.
14. Changes to this Policy
In short
If we make a material change, we tell you at least 14 days before it takes effect.
We may update this Policy to reflect changes to the Service, our practices or the law. We will publish the updated Policy with a new “Last updated” date and, for material changes, notify you by email or in the app at least 14 days before they take effect.
15. Complaints and contact
In short
Contact us with any privacy question or complaint. If you’re not satisfied with our response, you can complain to the Office of the Australian Information Commissioner.
- Privacy questions and requests. Use the subject line “Privacy request”.
- Complaints. Tell us what happened and the outcome you are seeking. We acknowledge within 5 business days and respond in writing within 30 days.
If you are not satisfied with our response, you can contact the Office of the Australian Information Commissioner at oaic.gov.au or on 1300 363 992. If you are in the EU or UK, you can also contact your local data protection authority.
Mighty Lucky Ventures Pty Ltd (ABN 51 653 328 628), trading as Heista. Australia.