1. Overview
This policy explains what personal data Hiera collects, why, and what rights you have. The data controller is Hiera, Inc., 1111B S Governors Ave, STE 48131, Dover, DE 19904, United States ("Hiera", "we", "us"), which also sells the credits you buy in Hiera. Contact: legal@hiera.design.
2. Data we collect
- Account data: your email address; the first and last name and username you enter when you set up your profile; an optional profile photo; and the name of any workspace you create. If you sign in with Google, we also receive your name and profile picture as provided by Google. We do not receive or store your Google password.
- Email changes: when your account's email is changed, we keep a record of the change: its date, whether you made it in the app or we made it at your request (then also how we checked it was you, and who in our team made it), and the address you left as a keyed, one-way hash, so that if you write to us from that address we can find your account. We email that address to tell it the email was changed, except when we undo a takeover (below). In the same step we delete the sign-in codes we sent to it, and in our records of the emails we sent to it, and of the errors sending them, we replace it with the same hash. A few copies keep the address: the free-credit record, if you claimed free credits with it (Security and fair use, below); a waitlist entry for it (Waitlist, below); and our payment provider, Stripe, which keeps the address it was given for your payment emails. We update that one when we move your account for you, and when you ask us after changing your email yourself.
- Moving your account to another address: if you can no longer read your account's email address and ask us to move your account to another one, we first check that it is you, with the Google account linked to it, or with an ID document that we compare with the name on a card that was saved for your workspace at Stripe before you wrote to us, and that we don't keep. We then email the address your account has and wait at least 48 hours before we make the move; if neither check is possible, we wait 14 days instead, or refuse. Until then we keep your request: the address you asked for, how we checked it was you, and when we told your current address. Section 7 says how long. If someone else changed your account's email, we move it straight back to an address it had in the last 30 days, after the same check, at once and without telling the address it left, which belongs to whoever took it.
- Content: projects, images, drawings, PDFs, notes, comments and prompts you upload or create, and metadata about them (timestamps, authorship, project membership).
- Payment data: when you buy AI credits or subscribe to Hiera Pro, payment is handled by Stripe. Stripe securely keeps the payment method you use (for example your card) on your workspace's Stripe customer record for future purchases, including automatic top-ups if you turn them on in Billing and Hiera Pro renewals if you subscribe. We receive confirmation of the transaction, your billing country, and enough to show you which method is saved (card brand, last four digits and expiry date), but never your full card number or security code. If you ask us to move your account to another address, we may look at the name on a card saved for your workspace at Stripe, and when it was saved, to check that it is you (Moving your account, above). We also keep records of refunds, payment disputes and any pause of AI features they cause. If you subscribe to Hiera Pro, we keep its subscription records: its status, renewal and cancellation dates, its invoices and the credits each payment added. When you buy credits or subscribe to Hiera Pro, we record who agreed to the purchase terms (for Hiera Pro, including its monthly renewal), when, the amount and the version of the wording you agreed to. When you turn automatic top-up on, change it or turn it off, we record who did it, when, the settings and the version of the wording you agreed to. Both records include the country of your internet connection (the country only, not your IP address).
- Usage data: product analytics events collected via PostHog on our sites (hiera.design and learn.hiera.design) and in the app: pages visited, the buttons and links you click, features used, device and browser type, and your approximate location (country and city) derived from your IP address. On our sites a click can include the visible text of what you clicked; in the app clicks are recorded without it. Once you sign in, events in the app are linked to your account by its user ID and workspace ID, never by your email address or name. Events recorded in the app before October 2026 may still include your email address and name; they stay in PostHog until we delete them. You can ask us at any time, at legal@hiera.design, to delete your analytics data: we delete the analytics profile linked to your account with its events and replays, and ask PostHog to remove any older events that carry your address but are not linked to your account (some pages before sign-in recorded it).
- Session replays: only if you switch them on (in the question shown after you sign in, or under Settings › Privacy), and only while you are signed in to the app — never on our public sites, on the sign-in screens (including when you add another account), or for people viewing a shared link without an account. PostHog then records a replay of how you use the app: what is shown on your screen, including images you upload or generate, together with your clicks and navigation. Text you type into a field is masked as you type, and the text of notes and comments and any email address shown on screen are masked in the replay; names and the rest of the canvas stay visible. Replays do not include network requests or console output, and page addresses are kept without their query string. Errors in the app are reported separately, with personal details removed (see Technical data below). Your saved card's brand, last four digits and expiry date are masked, and we never record payment card details. You can switch replays off at any time: recording stops immediately in every open tab of that browser, and on your other devices when you next load the app or return to an open tab (checked at most every few minutes). Replays are deleted automatically after 30 days. We keep a record of each answer you give to this question (on or off, when, whether in the question or in Settings, and the version of the wording), so we can show what you chose.
- Advertising and measurement data: if you accept cookies on our sites or in the app, advertising and measurement tags (loaded through Google Tag Manager) may collect information about your visit, such as pages viewed, referring campaign, device and an advertising identifier, to measure our campaigns and show you personalised ads. See Section 9.
- Security and fair use: when you sign in, Cloudflare Turnstile checks that you are not a bot (it reads browser and device signals for this). We count requests per IP address, email address and account. For free credits we keep a keyed, one-way hash of your IP address and network and a normalised form of your email address, so the same person cannot claim the welcome grant twice. Section 7 says how long we keep them.
- Sign-in sessions: for each device you sign in on, we keep a record of that sign-in, so you can see where your account is signed in and sign a device out under Settings › Security & access: the browser and system (for example “Chrome on macOS”), the country of your internet connection (the country only, not your IP address), when you signed in, when the device was last active, and when and how the sign-in ended. We keep the keys that keep you signed in only in hashed form, each with the day it was issued and when it was used. For about an hour after a key is used we also keep the exact time and the browser and system that used it, so that we can tell your own device asking again for a renewal it didn't receive from a copy of its key; after that, only the day it was used. Section 7 says how long we keep them.
- Technical data: server logs, IP addresses and error reports needed to keep the Service secure and reliable: errors on our servers via Sentry, and errors in the app via PostHog (the error message and where in our code it happened, with email addresses, sign-in codes, tokens and the query strings of web addresses removed from the message). A server error report can include your IP address, your account identifiers and the request that caused the error, which may contain content you sent, such as a prompt or your email address.
- Connected apps: if you connect Hiera to ChatGPT, we keep a record of the connection: which app, the access you approved, when you connected it, when it was last used and when it ended. We keep the keys that give the app access to your account only in hashed form. ChatGPT then sends us what you ask it to do in Hiera: the images you ask it to save, with the title, subject or short note ChatGPT writes from your conversation and the file's name, and the names of the pages and projects you ask it to create. We download each image from OpenAI's file storage and store it as received, including details embedded in the file, such as where a photo was taken. What ChatGPT saves becomes Content, like anything you add yourself. We don't use any other details ChatGPT attaches to its requests, such as your language or approximate location. Section 5 says what ChatGPT receives from us, and Section 7 how long we keep the connection record.
- Communications: messages you send us (including feedback from the in-app form, which reaches us through PostHog linked to your account even if you turned product analytics off), and delivery data for the emails we send you (for example, whether an email was delivered or bounced).
- People without an account: if someone invites you or mentions you, we receive your email address (and name, if given) from them to send you the invitation or notification (our and our users' legitimate interest). If you open a public link without an account, we collect the usage and technical data described above.
- Waitlist: if you joined our waitlist before launch, we keep the details you gave us: your name and email address and, if you gave them, details such as your company, role, how you heard about us and your level of interest. We use them only to tell you that Hiera is available and invite you to try it. You can ask to be removed at any time with the unsubscribe link in any such email or by writing to legal@hiera.design.
To have an account you need an email address, a first and last name and a username, and a workspace name if you create a workspace. To buy credits or subscribe to Hiera Pro you also need a payment method, with the billing details Stripe asks for (such as your country). Everything else, including a profile photo, is optional.
3. Why we process it (legal bases)
- To provide the Service: operating your account, storing and syncing your Content, enabling collaboration, processing payments, including recurring Hiera Pro charges, and keeping your payment method on file for future purchases and renewals (performance of a contract).
- To provide AI features: sending your prompts and selected images to our AI providers to generate results (performance of a contract).
- To connect Hiera to ChatGPT when you ask us to: checking the connection you approve, listing your projects, pages and workspaces for ChatGPT, and creating the pages and projects and saving the images you ask for (performance of a contract). We keep the record of a connection for 30 days after it ends, so we can answer questions about which apps had access to your account and look into misuse (legitimate interest in keeping your account secure). Names that other people chose, in projects and workspaces they share with the person who connected, are passed on to ChatGPT for our and our users' legitimate interest in letting collaborators work with the tools they choose.
- To keep you signed in, and to let you see and end where your account is signed in: the sign-in records in Section 2 (performance of a contract). To keep your account secure (legitimate interest): we compare the browser and system of a renewal asked for again with the one that used the key, keep the used keys of a live sign-in so that a copy of one is caught, keep the record of a sign-in for 30 days after it ends to look into misuse of your account, and keep when you last signed out of other devices to stop the sign-ins made before November 8, 2026, 09:31 UTC that came before it, until a week after December 8, 2026, 00:00 UTC at the latest.
- To keep the Service secure and fix errors: logs and error monitoring (legitimate interest).
- To protect the Service and our free credits from abuse, automated sign-ups and fraud, including bot checks, rate limits and limits on free-credit grants, and keeping the hashes described in Section 7 for 12 months after an account is deleted (legitimate interest). If our checks refuse a free-credit grant, this does not affect your account, your projects or your ability to buy credits; email legal@hiera.design if you think a check got it wrong and a person will review it.
- When your account's email is changed: we email the address it left so that its owner hears of it (except when we undo a takeover: then it belongs to whoever took it), and we keep the record of the change in Section 2 while your account exists, so that we can find your account if you write to us from that address. When you ask us to move your account to another address, or to undo a takeover, we check that it is you, including against the name on a card saved at Stripe, and keep your request until the move is made or cancelled (legitimate interest in keeping your account secure and helping you get it back).
- To understand and improve the product: the usage data in Section 2 (in the app linked to your account by its user ID, never by your email address or name), based on our legitimate interest in improving Hiera. You can object at any time: switch product analytics off in Settings › Privacy, which applies in the browser where you set it (Section 9), or email legal@hiera.design and we stop analytics for your whole account; we handle email requests by hand within 30 days.
- Session replays (Section 2): only if you switch them on when we ask after you sign in, or in Settings › Privacy (consent). You can withdraw at any time, and recording stops immediately.
- To measure our advertising and show you personalised ads: cookies and similar technologies on our sites and in the app, only with your consent (see Section 9), which you can withdraw at any time.
- To send notifications about activity relevant to you (mentions, comments, invitations) and about your account, purchases and Hiera Pro subscription (performance of a contract; for optional activity notifications, our legitimate interest in keeping collaborators informed). You can turn activity notifications off by type or with the unsubscribe link in any email. Service messages such as receipts, Hiera Pro emails (each payment's receipt, credits added and Pro ending), security notices and notice of changes to our Terms or prices cannot be turned off.
- To tell you about new Hiera features and offers, such as free credits, by email. In Georgia we do this only if you agreed to it (consent). In the UK and the EEA we do this if you agreed to it (consent), or if you are an existing user who was given the chance to refuse such emails when you signed up and did not (legitimate interest). You can withdraw your consent or opt out at any time with the link in every such email or by writing to us.
- To tell people on our waitlist that Hiera is available and invite them to try it (legitimate interest: you asked to hear from us when you joined).
- To handle refunds, chargebacks and disputes about automatic top-up or Hiera Pro (legitimate interest in establishing, exercising or defending legal claims).
- To keep invoices, transaction records and the records tax law requires (legal obligation). Where those laws are not UK or EU laws, such as US tax law, we keep these records on the basis of our legitimate interest in meeting them.
4. AI processing
When you use AI features, the prompt and the images you select are sent through Vercel's AI Gateway to Google's Gemini models to generate the result. Along with your request we may send your country, derived from your IP address. Vercel and Google process this data to deliver the feature and, under Vercel's terms and the Google terms that apply through it, may not use it to train their models. Google may keep it for a limited period to detect abuse. Our search provider Exa is different: see the next paragraph. We do not use your Content to train our own models.
When a feature searches the web or looks for products (for example in a Note or a Cost Estimate), it sends search text: text that our AI writes from your request, which can include words from your prompt or describe an image you pointed the search at, or the search words you type yourself, such as a Cost Estimate row's name and note. We are moving our search from Serper to Exa, so each search goes to whichever of the two is switched on at the time. That search text is all they receive, plus, for a search in the Georgian market (chosen from the country you connect from or the language of your request), the fact that the search is for Georgia. They never receive your images, files or account details. Exa receives the search text through Vercel's AI Gateway, where a Google Gemini model passes it on and sees the same text. Under its terms, Exa may use search queries to improve its own service.
Search results show product photos. For shops on our list of Georgian shops, we may keep a copy of the product photo in our own storage and show you that copy. Other photos load directly from the website that hosts them (usually the shop's) or, for some results, from Google's servers, so viewing them sends your IP address and browser details to those sites, as any website you visit does. Nothing else about you is sent to them.
Some features, such as selecting an object, removing a background and estimating depth, run on your device: the image is processed in your browser and is not sent to an AI provider for that step. Your browser downloads the model files for these features from our own servers. If they are unreachable, it downloads them from Hugging Face or jsDelivr instead, which then receive your IP address and browser details, as any website you visit does; no image is sent to them.
ChatGPT is not one of our AI providers: OpenAI runs it under its own terms. If you connect Hiera to ChatGPT (Section 5), ChatGPT's requests to Hiera don't use our AI features.
6. International transfers
Hiera, Inc. is based in the United States, and our service providers (Section 5) may process your data in the United States and other countries. Our application servers (Hetzner, Falkenstein, Germany), database (Neon, Frankfurt), product analytics (PostHog EU cloud) and error monitoring (Sentry EU region) are hosted in the EU. Other providers, including file storage (Cloudflare), AI generation (Vercel and Google), search (Exa or Serper) and email (SendGrid), may process data in the United States and other countries. When we share personal data from the EEA with a provider outside the EEA, we use either the EU-US Data Privacy Framework, for US providers certified under it, or the EU Standard Contractual Clauses (Commission Implementing Decision (EU) 2021/914). For UK data we use the UK Extension to the Data Privacy Framework or the UK International Data Transfer Addendum. For Swiss data we use the Swiss-US Data Privacy Framework or the Standard Contractual Clauses as adapted for Swiss law. Some members of our team work in Georgia and can access data only as far as their role needs, under the same security measures. You can ask for a copy of the safeguards, or which one applies to a given provider, at legal@hiera.design. OpenAI is not one of these providers: if you or a collaborator connects ChatGPT, OpenAI receives the data described in Section 5 as an independent controller (in a ChatGPT workspace an organisation runs, such as ChatGPT Business, Enterprise or Edu, on that organisation's behalf), and its handling of that data, including where it is processed, is governed by OpenAI's own terms and privacy policy.
7. Retention
We keep personal data only as long as we need it for the purposes above:
- Account data and Content: while your account exists. When you delete a project, page or workspace, it disappears from Hiera at once, but we keep it in a form we can restore, in case it was deleted by mistake. Deleted Content is removed for good when you ask us to delete the whole workspace or your account. There is no delete-account button yet: to ask, write to hello@hiera.design. We then delete the workspace's Content, or your personal data and Content, within 30 days, except the records listed below. We must keep transaction, invoice and tax records (tax and accounting law requires them). We also keep consent records (for purchases, automatic top-up, Hiera Pro and session replays), Hiera Pro subscription records, and refund and dispute records (we need them to show what you agreed to and to answer payment disputes and legal claims), and, for 12 months, a keyed, one-way hash of your email address and of your IP address and network, only so the free-credit welcome grant can't be claimed twice. Our database provider keeps a restorable history of our database for 24 hours and daily backups for 14 days, so data we delete from the database is gone from them within 15 days; our file storage keeps no copies of deleted files. Content you added to a workspace owned by someone else stays with that workspace until its owner deletes it.
- Earlier email addresses (the keyed, one-way hash of an address your account left, Section 2): while your account exists; they are deleted with your account, except in the records of receipts and notices we keep (Records of the emails we send you), where the address stays as this hash.
- Requests to move your account to another address (Section 2): until the move is made or cancelled, and no longer than about three weeks after the request; they are deleted with your account. An ID document you send us for it is deleted, from our mailbox's trash too, once we have looked at it.
- Error reports from our servers (Sentry): deleted automatically after 30 days.
- Server logs on our application servers: deleted automatically within 15 days.
- Logs of our real-time collaboration service (Cloudflare): deleted automatically after 7 days.
- Product analytics events: PostHog does not delete them automatically. We delete the events linked to your account when you ask us (Section 2) or when your account is deleted. Events that aren't linked to an account (for example visits before sign-in, which carry only a random ID) stay with PostHog. Session replays: deleted automatically after 30 days.
- Rate-limit counters: at most 24 hours, in memory only. Free-credit eligibility records (hashed IP address and network, normalised email): while your account exists. When your account is deleted, we replace your email address in them with a keyed, one-way hash and keep that, with the hashed IP address and network, for 12 months, only to stop the same person claiming the welcome grant twice; then we delete these hashes.
- Records of the emails we send you (the address, subject, time and whether it was delivered): while your account exists. When your account is deleted, we delete them, except records of receipts and of notices we must give (such as changes to our prices or Terms), which we keep with your email address replaced by a keyed, one-way hash.
- Delivery data held by our email provider (SendGrid): up to 30 days. Its lists of bounced and unsubscribed addresses are kept until the address is removed from them.
- Support and privacy-request emails: 3 years after the conversation ends.
- Records of deletion requests (which account or workspace, when, and what we deleted, with email addresses only as keyed, one-way hashes): 3 years after we complete the request, to show that we handled it.
- Waitlist details: until you ask to be removed, or until launch, whichever comes first.
- Transaction, invoice and tax records: 6 years after the end of the year of the payment, as tax and accounting law requires.
- Consent records for purchases and automatic top-up, and refund and dispute records: 6 years after the purchase they relate to. Hiera Pro subscription and invoice records, and your agreement to its renewal: 6 years after the subscription ends. Your answers to the session-replay question: 6 years after you gave the answer. We keep these even after your account is deleted, linked only to an account ID that no longer carries your name or email address.
- Saved payment methods: kept by Stripe until you remove them in Billing or the workspace is deleted, when we remove every payment method saved for it. Stripe keeps the underlying transaction records as financial regulations require.
- Connections to ChatGPT (which app, the access you approved, when you connected it, when it was last used and when it ended): while the connection exists and for 30 days after it ends; when your account is deleted, they are deleted with it. A connection ends when you disconnect it under Settings › Connected apps, when you sign out of other devices under Settings › Security & access, when your account is deleted, about 60 days after ChatGPT last received or renewed its access (ChatGPT renews it as it uses Hiera), or at once if we end it to protect your account, for example if its keys appear to have been copied (or the keys of one of your sign-ins). ChatGPT's access lasts an hour at a time, and ChatGPT renews it with a renewal key that lasts 60 days and is replaced each time it is used. We keep these keys, and the one-time code used to connect, only in hashed form: each key is deleted about a day after it expires, or at once when you disconnect, when we end the connection or when your account is deleted; the code is kept with the connection record. A request to connect that you cancel or don't finish is deleted about a day later. What ChatGPT keeps from your conversations is governed by OpenAI's terms and privacy policy (Section 5).
- Sign-in sessions (the device, its country, when you signed in, when it was last active, and when and how it ended): while you stay signed in on that device and for 30 days after the session ends; when your account is deleted, they are deleted with it. A session ends when you sign out, when you sign that device out or sign out of other devices under Settings › Security & access, after 30 days without use, or at once if we end it to protect your account, for example if its keys appear to have been copied. Your access lasts 15 minutes at a time, and the app renews it with a renewal key that lasts 30 days and is replaced each time it is used. We keep these keys only in hashed form, with the day each was issued and when it was used; the exact time of a key's use, and the browser and system that used it, only for about an hour, and after that the day it was used. A key that was never used is deleted about a day after it expires (about 31 days after it was issued). A used or replaced key is kept while its session is live, at most about 3 months after it was issued, so that a copy of it is still caught if it comes back; once the session has ended, it goes a day after it expires or with the session's record, whichever comes first. A session that replaced a sign-in from before November 8, 2026, 09:31 UTC keeps that sign-in's key, hashed, as long as the session record is kept. Until December 8, 2026, 00:00 UTC, sign-ins made before November 8, 2026, 09:31 UTC keep working without the 15-minute limit. They aren't listed under Settings › Security & access until the app renews them, and signing out of other devices ends them; we keep when you last did that until then, and delete it within a week after. Until then, too, an app tab opened before November 8, 2026, 09:31 UTC can put such a sign-in's key in the address of its live-collaboration connection, which our hosting provider (Cloudflare) logs and keeps for 7 days, and signing out in such a tab may not end the session that replaced its sign-in: that session then ends after 30 days without use, or when you sign it out under Settings › Security & access.
We may keep anonymised data that no longer identifies you.
8. Your rights
Depending on where you live (including under the GDPR), you have the right to access, correct, delete and receive a copy of your personal data, to restrict certain processing, and to withdraw consent at any time where processing is based on consent. To exercise any of these rights, email legal@hiera.design. To delete your account, you can also write to hello@hiera.design (see Section 7). You can remove a saved payment method yourself from Billing in the app. You can disconnect ChatGPT yourself under Settings › Connected apps, which ends its access to your account at once. What ChatGPT already saved stays where it was saved, as Content you added (Section 7), until it is deleted there, and a link to a saved image that ChatGPT already has keeps opening until the image is removed for good (Section 7). Disconnecting doesn't remove what is already in your ChatGPT conversations: OpenAI's terms and privacy policy govern it (Section 5). If you remove Hiera inside ChatGPT instead, we are not told: the connection stays in Connected apps until you disconnect it there or it ends on its own (Section 7). You also have the right to lodge a complaint with your local data protection authority.
Your right to object. Where we process your data based on our legitimate interests, such as product analytics, you can object at any time on grounds relating to your situation, and we stop unless we have compelling reasons that override yours or need the data for legal claims. For product analytics, Section 3 explains how. You can object to direct marketing at any time, without giving a reason, and we then stop.
We reply within one month; for complex requests we may extend this by two more months and tell you why. We may ask you to confirm your identity from your account email.
If you are in Georgia, you have these rights under the Law of Georgia on Personal Data Protection, including the right to ask us to block (restrict) processing. We answer your requests within 10 working days. In justified cases we may extend this by up to 10 more working days, and if we do we tell you why. You can complain to the Georgian data protection supervisory authority or go to court.
10. Security
Data travels between your browser and Hiera encrypted (HTTPS), and our database and file storage providers encrypt it at rest. Only team members who need access for their role have it. No system is completely secure; if a breach affects your personal data, we tell you and the authorities as the law requires.
Some decisions are made automatically: we pause AI features while a payment dispute, chargeback or bank inquiry is open, bot checks and rate limits can hold a sign-in or a request, our free-credit checks can refuse a grant, and Stripe screens payments for fraud. Hiera Pro also reacts to refunds and chargebacks automatically, as Section 3A of our Terms describes. If a Pro payment is refunded, other than for a withdrawal, Pro ends at once, and if that payment added credits we also cancel the workspace's free and Pro credits. If a chargeback is opened on any payment in the workspace, Pro ends at once and is not restored, and we cancel the workspace's free and Pro credits, even if the chargeback is later decided in our favour. A bank inquiry alone pauses AI features but does not end Pro. None of these affects your account beyond what our Terms describe. If you think one got it wrong, email legal@hiera.design and a person will review it.
11. Children
Hiera is not directed at children under 16, and we do not knowingly collect their data. If you believe a child has created an account, contact us and we will delete it.
12. Changes to this policy
We may update this policy as the product evolves. For material changes we will notify you by email or in-app notice before they take effect. The "Last updated" date at the top shows the current version. See also our Terms of Service.