Legal
Privacy Policy
Effective: November 19, 2026.
1. About this policy
This policy explains what personal information Angry Pixie Electronics LLC, d/b/a Holarch, a Minnesota limited liability company (“we”, “us”), collects through the Holarch website at holarch.app and the Holarch application at app.holarch.app (together, the “Service”), and what we do with it. It does not cover copies of Holarch that an organization runs in its own environment; that organization is responsible for them.
2. Summary
- We collect what we need to run your account and your projects, and to keep the Service secure.
- We do not sell your information, show ads, or use advertising trackers or third-party analytics. We collect anonymized application usage statistics to decide what to build and improve.
- The Service uses only strictly necessary cookies: the sign-in session cookie, and short-lived cookies while you sign in with Google, Microsoft or your organization’s single sign-on, or complete a two-step sign-in. Cloudflare, which protects the website and the Service, may add a short-lived security cookie (section 5). Videos come from our storage provider and holarch.app (section 5).
- We do not use your content to train AI models. AI requests go only to Anthropic, under the key in use: your own key, your organization's key, or Holarch's key for the AI included in your plan. Anthropic does not train on API data and deletes it within 30 days.
- Payments are handled by Paddle. We never receive your card number.
- You can export your projects, correct your account details, and delete your projects and your account.
3. What we collect
Account information
- Your name and email address.
- Your password, if you set one, stored only as a one-way hash (argon2id). We cannot read your password.
- For accounts created before October 8, 2026: the time and version of the data-use acknowledgement given at sign-up.
- Invitations you send or receive: the email address invited, who invited it, and the project and role.
- Your answer to the optional sign-up question “How did you hear about Holarch?”, if you give one, and the domain of the website that led you to the sign-up form (for example, www.google.com; never the full address). We use these only to understand which channels work.
- If you came from one of our ads or links: its source, campaign and search keyword, as labelled in the link (UTM tags). It stays in your browser until you sign up, then is kept with your account. If you send the contact form, its source and campaign are sent with your message.
- Your answer to the sign-up question “How will you use Holarch?” (trying it out or personal learning, coursework or teaching, or work for a company or client), and when you gave or changed it. We use it to show which plan fits that use.
Sign-in with Google or Microsoft
- If you sign in with a Google or Microsoft account, that provider tells us your account’s identifier at that provider, your email address, whether the provider has confirmed that address, and your name. We store the identifier, the email address at the time of linking, and when you linked it and last used it, so we can recognise you next time. If the account belongs to an organization (a Google Workspace or a Microsoft work or school account), we also store that organization’s domain name.
- We do not receive your Google or Microsoft password, and we do not ask for access to your mail, files or contacts. Account → Sign-in methods lists the linked accounts and lets you remove them.
Sign-in sessions
- A random session identifier in a cookie. We store only a hash of it.
- For each session: when it started, when it was last used, the IP address and the browser’s user agent. The account page shows your sessions so you can end them.
Two-step sign-in (optional)
- If you turn on two-step sign-in, we store what checks your second step.
- Authenticator app: a secret shared with your app, encrypted on our server, and the time of the last code accepted.
- Passkeys: each passkey’s public key, its identifier, a counter, the name you gave it, and when it was added and last used. A passkey’s private part never leaves your device or password manager. We receive no fingerprint, face or screen-lock data, and no details about the device.
- Single sign-on and provisioning: if your organization signs you in through its identity provider (SAML), we receive your email address, your name and, if the organization uses them, your groups, which set your role in the organization. If the organization manages accounts through SCIM, its identity provider can create, update and deactivate your account, and we store the identifier it uses for you. For the organization, we store its identity-provider settings, its verified email domains and its SCIM tokens (only a hash of each token).
- Recovery codes: only a one-way fingerprint (hash) of each code, and whether it was used.
- Account → Two-step sign-in shows all of these and lets you remove them.
API tokens (optional)
- If you create a personal API token, we store its name, a one-way fingerprint (hash) of the token (the token itself is shown to you once and not kept), its scope (read, or read and write), the projects it is limited to, and when it was created, expires, was last used and was revoked.
- A program or AI client you connect with a token (for example through the API or MCP) acts as you, with your permissions. What it does with the data it reads is between you and that program; we do not send your data anywhere else.
Connected apps (optional)
- When you connect an app such as Claude to your account with sign-in, we store the connection: the app’s name and identifier, the address it returns to, the access and projects you chose, when it ends, and when it was created and last used. For an app that registered itself, we store its name and its return addresses; for an app identified by a public metadata document, a cached copy of that document.
- We store only fingerprints (hashes) of the connection’s access and refresh tokens, never the tokens themselves, and a short-lived record of each connection request.
- The app receives what you allow and acts as you within your project roles. What it does with the data it reads is governed by that app’s own terms.
Your content
- Projects, models, documents, diagrams, whiteboards, comments and settings you create, their earlier versions, and who changed what.
- Files you upload, such as attachments, images and clipart.
- Project membership and roles.
AI keys and AI usage
- Anthropic, Kimi (Moonshot AI) and GLM (Z.ai) API keys that you or your organization add, stored encrypted. Only the last four characters are shown after you add a key. A key added earlier for another AI provider is kept, encrypted, and not used until you delete it.
- For each AI request: the time, account, project, the key used (yours, your organization’s or the included AI), provider, model, type of task, token counts, duration, result status and an estimated cost. We use these records to count your included AI requests, to prevent misuse and to report costs. We do not log the text of your prompts or the AI’s answers.
Logs
- Web server logs: IP address, time, requested address, response status, the referring page, user agent and the other request headers your browser sends (such as language preferences) for each request. Sign-in tokens are removed from logged addresses, and cookies are not logged. We use them to keep the service secure and working, and in totals for site statistics, such as visits from ads and the sites that refer visitors.
- Application logs: request path, status and timing, without IP addresses, used to find errors.
- Support call records: for each voice call in a support chat, the call and request IDs and the time of each step of the call (such as offered, accepted, connected and ended), without what was said and without audio. We use them to find faults in calls and to answer questions about a call.
- Application usage statistics: anonymized daily totals of which features are used. They contain no account, project content, IP address or device information.
- Clipart searches: when a whiteboard clipart search finds no Holarch illustration, we count the search words for that day, so we know which illustrations to draw. A term is kept only after at least three people searched for it on the same day, and never with who searched, in which project, or from where. Terms that look like email addresses, web addresses or long numbers are not kept.
- Clipart suggestions: when you choose Suggest to Holarch, what the dialog lists (a name, an optional description and, for an item you offer, its picture), with your account name and email.
- Video statistics: anonymized daily totals of how often each of our videos is started and how far it is watched (a quarter, half, three quarters or to the end), with no account, cookie, IP address or device information.
- Security and audit log: security-relevant actions, such as sign-ins, sharing changes, AI key changes and project exports, with the account, time and IP address. It never contains prompt text or key material. If you work in an organization’s projects, that organization’s administrators can see the entries about your actions in its organization and projects, such as sharing changes, exports and failed single sign-on attempts, for as long as the entries are kept.
- Cancellation answers: if you tell us why you canceled a paid plan, we keep your answer (the reason you chose and anything you wrote) to improve Holarch. Answering is optional.
- Days of use: the days (UTC) on which your account used Holarch, with no IP address or device details. We use them only in totals for site statistics.
- Sign-in records: each time someone signs in or tries to sign in, the time, the account (or the email address entered, if the attempt fails), the IP address and the host name it belongs to, the browser and device information your browser sends, how you signed in and whether a second sign-in step was used, the result, and the approximate location our network provider derives from the IP address (country, region, city, postal code, approximate coordinates and time zone). We never record passwords or sign-in codes.
Contact form
- Your name, email address, organization (optional), topic and message, and the source and campaign of the ad or link you came from, if any. The form sends them to us by email; they are not stored in the application database. Your IP address is used briefly to limit how many messages can be sent.
Support requests
- When you send a request with Contact Support… in the application: your verified email address, account ID, plan, organizations and roles, the Holarch version, your browser and the page you were on, the topic, subject and message, and the current project only if you tick Include the current project so support can look at it. The dialog shows all of it under What we send before you send.
- Support requests are kept in Holarch’s own support system on our servers, with the information listed above and any files you attach. The text may be machine-translated and summarized by our AI provider. Attached files are checked by a virus scanner on our own server. Kept one year after the last update, then deleted.
- Live chat and voice calls: if support invites you to a live chat, its messages, the files you share in it and the times they were sent are part of your request and kept with it. The chat also shows when each side has received and read a message; these times are kept with the request too. If you accept a voice call in the chat, only its written transcript, in the languages spoken and with its translations, is kept with your request. Holarch does not record or store the audio (section 6).
- Presence in a live chat: while you are in a live chat, support can see whether you are connected to it, whether the chat page is in view or hidden behind another tab or window, whether you have used the page in the last few minutes, and when you were last active. Your browser reports only these states, not what else is on your screen. The time you were last active is kept with your request; the other states are not kept after you leave the chat.
- When you write to Holarch support from the app, our website, a private support link or a live chat, we store the time zone our network provider reports for that request (for example Asia/Shanghai) on your support ticket, so our staff can see your local time when answering. Our staff may also set or correct it on the ticket. For a ticket tied to your account, staff may see the time zone from your latest sign-in record. It is visible to Holarch support staff only and is deleted with the ticket, one year after the ticket’s last activity or closing.
- Our own records of support contact: for each request sent with Contact Support… or the contact form a log entry with the time, the topic, the length of the message and whether it was sent (for the contact form also the domain of the email address, such as example.com). These records hold no message text.
Ask Holarch (the chat on holarch.app)
- When you use the chat on the website, we keep your questions, the page you asked them on, the language they were written in and the pages the answer linked, for 90 days, to improve Holarch and its documentation. We do not keep the answers, your IP address or your browser details with them. Your IP address is used in memory only, for up to a day, to limit how many questions one visitor can ask. Do not include personal information in your questions.
- Your questions and the matching text from our website are sent to Anthropic to write the answer (section 6); questions from mainland China, Hong Kong, Macau and Taiwan are sent to Z.ai (GLM 5.3, Singapore) instead. The conversation itself stays in your browser tab and is gone when you close it.
- If you choose Contact support in the chat, the conversation is sent to our support desk with the name and email address you enter, like a message through the contact form (Support requests, above).
Billing information
- When you start a paid plan, Paddle collects your payment and billing details (card or other payment method, billing address, tax ID if you give one) as Merchant of Record, under its own privacy notice.
- We receive from Paddle your subscription status, plan, number of seats, billing period, country, email address and Paddle customer and subscription identifiers. We do not receive card numbers.
Emails we send
- We send only service emails, such as invitations, email verification, password reset and account notices. We do not send marketing email without your consent.
- Notification emails. If you have an account, we email you notices about mentions, assignments, reviews and changes to items you watch, by default once a day. Change or turn off these emails under Account → Notifications or with the link in each email; mail apps with an Unsubscribe button turn them off in one step.
4. How we use it
- To create and run your account, sign you in, and keep you signed in.
- To check sign-ins to your account with two-step sign-in, and to let programs you authorize with an API token or apps you connect work with your projects. We email you when your two-step sign-in, API tokens or connected apps change.
- To store, sync, share and back up your projects, and to run the features you use.
- To make AI requests you start, with the key in use, to count your included AI requests, and to show you your AI usage.
- To keep the Service secure: detect and stop abuse, enforce rate limits, investigate incidents and show you your sign-in history. We use sign-in records to protect accounts (for example, to spot sign-ins from unexpected places, investigate suspicious activity and help you if your account is taken over) and to keep records of access to the Service; only our administrators can see them, and their access is itself logged.
- To understand which channels and ad campaigns lead people to Holarch, from the optional sign-up answer, the referring domain and the campaign tags, counted in total.
- To check that your plan fits your use: the Free plan is for personal, educational and evaluation use. We use account details only — your email domain, the organization domain from a Google or Microsoft sign-in, your answer to “How will you use Holarch?” and the email domains of your projects’ editors — never the content of your projects. A person reviews any result and may email you about a paid plan; nothing changes on your account automatically.
- To answer your messages and support requests.
- To send service emails and notices about changes to the Service, these policies or a security incident.
- To meet legal obligations.
We do not use your content for advertising, profiling or training AI models. We look at a project’s content only when you ask for support and allow it, when needed to investigate abuse, a security problem or a breach of the Terms of Use, or when the law requires it.
5. Cookies and browser storage
- The application’s main cookie is
__Host-holarch_session, which keeps you signed in. It is strictly necessary, cannot be read by scripts, is sent only over HTTPS, and ends after 8 hours without activity (organizations may choose a shorter time) and after 90 days at most. Signing out ends it. - When you sign in with Google or Microsoft, the application also sets
__Host-holarch_oidcfor at most 10 minutes. It holds a random value that ties the sign-in to your browser, cannot be read by scripts, is sent only over HTTPS, and is deleted when the sign-in finishes. It is strictly necessary. - While you complete the second step of a sign-in, the application sets
__Host-holarch_mfa. It holds a random value for that sign-in only, cannot be read by scripts, is sent only over HTTPS, and is deleted when you finish or after 10 minutes. It is strictly necessary. - When you sign in with your organization’s single sign-on, the application sets
__Host-holarch_samlfor at most 10 minutes. It holds a random value that ties the sign-in to your browser, cannot be read by scripts, is sent only over HTTPS, and is deleted when the sign-in finishes. It is strictly necessary. - The application keeps your preferences and a copy of the projects you open in your browser’s local storage, so it loads faster and can work offline. Signing out removes the project copies.
- Cloudflare, which protects holarch.app and the Service (section 7), may set a strictly necessary security cookie such as
__cf_bm(at most 30 minutes) orcf_clearance(after a security check) when it needs to tell people from automated traffic. These cookies are not used for tracking or advertising. - The holarch.app website sets no cookies of its own. Its scripts come only from holarch.app and run in your browser: the Help and Docs search, the video player and video page navigation, and the contact form’s topic and campaign tags. None of them sends data to us or to anyone else, except the video statistics (section 3); the contact form sends only what you submit. Its videos come from our storage provider and holarch.app (next items).
- We use no third-party analytics, and no advertising or third-party tracking cookies, scripts, fonts or pixels. Application usage and video statistics go only to our own server and use no cookies or browser storage.
- Videos. All of Holarch’s videos, on the website and in the application, are our own copies. The video and narration files come from our storage provider, DigitalOcean (its content delivery network); captions and preview pictures come from holarch.app through Cloudflare, like every page (section 7). No other third party is involved, and our web server logs each request like any other page (web server logs, section 3). Nothing loads before you press play, except the preview picture on wide screens; on a phone, not even that. In the desktop version, a video opens on holarch.app in your browser. Some videos are also published on our YouTube channel. The website and the application play our own copies and do not link to the YouTube copies; the Help Center links to the channel itself, and following that link takes you to YouTube under its own terms. You can skip the videos: every tutorial works without them.
6. AI providers
AI features use Claude, from Anthropic; requests from mainland China, Hong Kong, Macau and Taiwan use GLM 5.3, from Z.ai, instead, as described below. Each request uses one key: your own Anthropic key if you added one, otherwise your organization’s key, otherwise Holarch’s own key, which provides the AI included in your plan (a number of requests each month, shown on the Pricing page). When you start an AI request, the content needed for it (for example, the selected requirements, part of a model, or your Ask AI question) is sent to Anthropic. Under Holarch’s key, Anthropic processes it as our service provider: under its commercial terms it does not train models on this content, and it deletes API inputs and outputs within 30 days, unless it needs them longer to enforce its Usage Policy or the law requires it. Under your own key, your agreement with Anthropic applies. Holarch keeps no prompt text or replies; for each request we keep the usage record described in section 3. No content is sent to Anthropic unless you start an AI feature. If you or your organization add a Kimi API key and choose it for AI requests, those requests go to Moonshot AI instead of Anthropic: your prompts and the project content they include are sent to Moonshot AI under your or your organization’s own agreement with Moonshot AI, which then governs that content, including whether Moonshot AI may use it to improve its models. Holarch shows this before you add or choose a Kimi key. If you or your organization add a GLM API key and choose it, those requests go to Z.ai in Singapore in the same way, under your or your organization’s own agreement with Z.ai; Holarch shows this before you add or choose a GLM key. The AI included in your plan uses Anthropic, except for requests from mainland China, Hong Kong, Macau and Taiwan: these use GLM 5.3 from Z.ai under Holarch’s key, and Holarch shows this before your first request. Apart from these and the voice calls described below, Holarch does not send your content to any other AI provider. The chat on holarch.app uses Holarch’s own key in the same way (Ask Holarch).
Voice calls in support chats. During a live support chat, support may offer a voice call; it starts only if you accept it, and you can keep writing instead. During a call, what each side says is sent to ElevenLabs to turn the speech into text and, when a phrase is not in the listener’s language, to speak the translation in a synthetic voice. The text of a phrase is sent to Anthropic (for customers in mainland China, Hong Kong, Macau and Taiwan, to Z.ai) to translate it into each side’s selected language and, unless it was spoken in English, into English for the support record, as described above. ElevenLabs processes the audio as our service provider and may keep it for a limited time under its own terms and privacy policy; we have opted out of ElevenLabs using it to train its models. Holarch does not record or store the audio; only the written transcript is kept with your support request (section 8).
7. Who we share information with
We share personal information only:
- with the service providers below, which process it for us to run the Service;
- with Anthropic, when you start an AI request, except requests from mainland China, Hong Kong, Macau and Taiwan (section 6);
- with Z.ai, when you start an AI request from mainland China, Hong Kong, Macau or Taiwan, for the support requests, live chats and voice calls of customers there, and when you or your organization add a GLM key and choose it (section 6);
- with Moonshot AI, only when you or your organization add a Kimi key and choose it for AI requests (section 6);
- with ElevenLabs, during a voice call you accept in a support chat (section 6);
- with people you share a project with, who see its content and the names and email addresses of its members;
- when the law requires it, or to protect the rights, safety or security of users, the public or us; and
- with a successor if the Service is sold or merged, under this policy.
We do not sell personal information and do not share it for advertising.
| Provider | Purpose | Data | Location |
|---|---|---|---|
| DigitalOcean, LLC | Hosting: application server, managed database, file storage and backups, and delivery of video and narration files (content delivery network) | All data described in section 3, except contact-form messages | United States |
| Cloudflare, Inc. | Network security and delivery for holarch.app and the Service: every connection passes through it, for protection against denial-of-service attacks and abusive traffic, encryption (HTTPS) and caching of the website | Your IP address, browser details and the requests and responses passing through, which it processes to deliver and protect them | United States and Cloudflare’s worldwide network |
| Resend | Sending service emails and contact-form messages | Recipient email address, name, email content; contact-form fields | United States |
| Google (Gmail, Google Workspace) | The support mailbox ([email protected]): receives contact-form messages and emails you send to support | Contact-form fields; emails you send to support | United States |
| Paddle.com Market Limited (Paddle) | Merchant of Record for paid plans: checkout, payment processing, tax, invoicing and refunds | Payment and billing details you give Paddle; your email address and plan | United Kingdom and the processors Paddle uses |
| Google LLC | “Sign in with Google”, only if you choose it | Google sends us your account identifier, email address, whether it is verified, your name and, for a Google Workspace account, its domain; we send Google nothing about you beyond the sign-in request | United States |
| Microsoft Corporation | “Sign in with Microsoft”, only if you choose it | Microsoft sends us your account identifier, email address, whether it is verified, your name and whether it is a work or school account, with its organization; we send Microsoft nothing about you beyond the sign-in request | United States |
| Anthropic, PBC (Claude) | AI features, only when you start them: under Holarch’s key for the AI included in your plan, or under your own or your organization’s key. Also machine translation and summaries of support requests, and translation during voice calls. Anthropic does not train on this data. | Content you send in the AI request; the text of support requests and live chats; the text of what is said in a voice call | United States |
| Moonshot AI PTE. LTD. (Kimi), Singapore; for keys from Moonshot’s Mainland China platform: Beijing Moonshot AI Technology Co., Ltd. | AI features, only when you or your organization add a Kimi API key and choose it, under that key; your or your organization’s agreement with Moonshot AI applies. Not used for the AI included in your plan. | Content you send in the AI request with that key | Singapore (api.moonshot.ai, international keys); China (api.moonshot.cn, Mainland China keys) |
| Jingsheng Hengxing Technology Pte. Ltd. (Z.ai, GLM), 10 Anson Road, #26-03 International Plaza, Singapore 079903 | AI features, only when you or your organization add a GLM API key and choose it, under that key; your or your organization’s agreement with Z.ai applies. Under Holarch’s key, the AI included in your plan for requests from mainland China, Hong Kong, Macau and Taiwan, and machine translation and summaries of support requests and translation during voice calls for customers there; the website chat (Ask Holarch) for visitors from there. | Content you send in the AI request; for customers in those places, the text of support requests, live chats and what is said in a voice call, and visitors’ questions in the website chat | Singapore (api.z.ai) |
| Eleven Labs, Inc. (ElevenLabs), New York, United States | Speech to text and synthetic voice during voice calls in support chats, only when you accept a call | The audio of what is said during the call; the translated text it speaks | United States |
Google’s and Microsoft’s own privacy policies apply to your use of their sign-in.
8. How long we keep it
| Data | Kept |
|---|---|
| Account information | While your account is open. When you delete your account, it is closed at once and kept for one year for record-keeping (see “When you delete your account” below), then deleted. |
| Projects only you belong to, after you delete your account | One year after the deletion, then deleted. Nobody can open them in that year; only our administrators can export them, for the purposes below. |
| Accounts never confirmed | An account created with an email address and password that is not confirmed within 7 days is deleted, unless it is linked to a plan, a project, an organization or an open support request. No reminder is sent. |
| Inactive Free accounts | A Free account that is not used for 24 months is closed after two email reminders and kept for one year, during which you can restore it by signing in; then the account, its projects and its files are deleted, including linked Google or Microsoft sign-ins. Projects shared with people who still use Holarch stay with them. |
| Projects | Until you delete them. Deleted projects stay in the Trash for 30 days, then are deleted. Deleting your account deletes the projects only you belong to at once. |
| Earlier project versions | For the version history of the project owner’s plan (7 days on the Free plan): the 20 newest, plus one a day |
| Uploaded files | Until no project uses them, then 30 days |
| Backups | Expire within 30 days |
| Linked Google or Microsoft sign-in | Until you remove it under Account → Sign-in methods or delete your account |
| Two-step sign-in data (authenticator-app secret, passkey public keys, recovery-code fingerprints) | Until you remove them, an administrator resets two-step sign-in at your request, or your account is erased (one year after you delete it) |
| API tokens (name, fingerprint, scope, projects, dates) | Until you revoke the token or delete your account; a revoked or expired token’s record is deleted with your account |
| Connected apps | Until you disconnect the app, it ends, or you delete your account; then 90 days. Access tokens: 1 hour. Connection requests: deleted a day after they end. |
| In-app notices (bell, My Work) | 90 days |
| Sign-in sessions (with IP and user agent) | Until you sign out or the session expires (at most 90 days) |
| Ask Holarch questions (website chat; no IP address or answer text) | 90 days |
| Web server logs | 30 days |
| Application logs | 14 days |
| Support call records (no transcript or audio) | 1 year, then deleted |
| Security and audit log | About 13 months (400 days). If an account is deleted, its entries keep the person’s name and account ID until they expire. Entries of an account you deleted are kept for the account’s retention year at least. |
| Cancellation answers | While your account exists, and for the year your records are kept after you close it; then deleted. Ask us at any time to delete yours sooner. |
| Days of use | One year, then deleted. Deleted with your account when the account is erased. |
| Sign-in records | One year, then deleted. Deleted with your account when the account is erased. |
| Subscription records (plan, status, billing country, Paddle identifiers) | While you have an account, and for 7 years after the last payment where tax or accounting law requires it |
| AI usage records | 13 months, then deleted |
| Application usage statistics (anonymized daily totals) | 25 months, then deleted |
| Clipart search counts | 1 year, then deleted |
| Declined clipart suggestions | 1 year, then deleted |
| Video statistics (anonymized daily totals) | 25 months, then deleted |
| Support requests, the files attached to them and our own records of them | One year after the last update of the request, then deleted. Ask us at any time to delete yours sooner. |
| Contact-form messages and emails to support (support mailbox) | Up to one year, then deleted. Ask us at any time to delete yours sooner. |
We may keep information longer when the law requires it or to resolve a dispute or investigate abuse.
When you delete your account. Deleting your account on the account page closes it at once: you can no longer sign in, your sessions, API tokens and connected apps stop working, and your email address can be used for a new account. Projects you share with others stay with them. We keep the account record, the security and audit log entries about it, its sign-in records, and the projects that only you belong to for one year after the deletion, so that we can respond to legal requests, resolve disputes and meet record-keeping obligations. In that year nobody can open those projects, and only our administrators can access these records, for those purposes. After the year we delete them; backups hold them until they expire, within 30 days. To have your information deleted sooner, contact us; we delete it unless we must keep it for a legal claim or obligation.
Inactive Free accounts: a Free account that is not used for 24 months is closed after two email reminders and kept for one year, during which you can restore it by signing in; then the account, its projects and its files are deleted, including linked Google or Microsoft sign-ins. Projects shared with people who still use Holarch stay with them.
9. Your choices and rights
- Access and export: export any project you can open as a project file (JSON). Ask us for a copy of other personal information we hold about you.
- Correct: change your name, email address and password on the account page.
- Delete: delete projects, or delete your account on the account page (its records are kept for one year, then deleted; see “When you delete your account”). You can also ask us to delete your information.
- Sessions: see your sign-in sessions and end them on the account page.
- Sign-in methods: sign in with a password instead, and remove a linked Google or Microsoft account at any time (Account → Sign-in methods).
- Two-step sign-in: turn it off, remove passkeys and replace recovery codes at any time (Account → Two-step sign-in). If an organization you belong to requires it, its projects open only while it is on.
- API tokens: see your tokens, when each was last used, and revoke any of them at any time (Account → API tokens).
- Connected apps: see and disconnect connected apps under Account → API tokens → Connected apps. Disconnecting ends the app’s access at once.
- Account recovery: resetting your password, Sign Out Everywhere, an administrator’s reset of your two-step sign-in or sign-out of your sessions, and a password change with “Also disconnect apps and revoke API tokens” end every connected app and API token of your account at once. The apps’ access and refresh tokens are deleted; the connection and token records are marked ended and kept as described in section 8. The security log records how many were ended, and we email you.
- Notification emails: choose daily digest, immediately or off under Account → Notifications, or use the link in any notice email.
- AI: remove your AI keys at any time. Nothing is sent to Anthropic unless you start an AI feature.
Send requests to [email protected] or through the contact form (topic “Support”). We may need to confirm your identity first. We answer within 30 days. We do not treat you differently for using these rights.
10. Visitors from the EEA, UK and Switzerland
If data protection laws such as the GDPR apply to you, we are the controller of your personal information, and we rely on these legal bases:
- Contract: to provide the account and the features you use.
- Legitimate interests: to keep the Service secure, prevent abuse, check that a plan fits its use, answer messages, and improve the Service from anonymized application usage statistics.
- Legal obligation: where the law requires us to keep or disclose information.
- Consent: where we ask for it. You can withdraw consent at any time.
You have the right to access, correct, delete, restrict or object to the processing of your personal information, and to data portability. You can also complain to your local data protection authority.
11. Where your information is stored
We are based in the United States, and the Service is hosted in the United States. If you use the Service from another country, your information is transferred to, stored and processed in the United States, where data protection laws may differ from those where you live. Where the law requires it, we use appropriate safeguards for these transfers.
12. Students and schools
When a school or instructor uses the Service for a class, student work in the Service can be an education record under the U.S. Family Educational Rights and Privacy Act (FERPA). We then act as a service provider to the school: we use student records only to provide the Service, under the school’s direction, and do not use them for advertising or sell them. The school remains responsible for its FERPA obligations. Students and parents should send requests about education records to the school; we help the school answer them.
When an organization administrator asks for class status, the course syllabus they upload is used only to verify the class, is visible only to Holarch administrators, and is deleted 30 days after the request is approved or declined.
13. Children
The Service is not for children under 13, and we do not knowingly collect personal information from them. If we learn that a child under 13 has an account, we delete the account and its information. If you believe this has happened, contact us.
14. Security
We protect your information with measures that include:
- HTTPS for every connection, and encrypted, certificate-verified connections to the database;
- passwords stored only as argon2id hashes;
- AI keys encrypted, never shown again after you add them, and never written to logs;
- roles for each project, sessions you can end on every device, email verification for every new account, and rate limits;
- protection against denial-of-service attacks and abusive traffic through Cloudflare;
- a copy of the database every 4 hours, stored in a different datacenter and kept for 30 days, plus daily backups of the managed database with point-in-time recovery for 7 days; every week, an automatic test restores the newest copy.
The Service does not hold security certifications or government authorizations such as SOC 2, ISO 27001 or FedRAMP. No online service is completely secure. If we learn of a security incident that affects your personal information, we will notify you by email without undue delay and as the law requires. See the Security page for more.
15. Changes to this policy
We may update this policy. Changes take effect when posted here with a new “Effective” date. When we make material changes, we notify you in the app: you are asked to accept the updated policy the next time you sign in.
16. Contact
Holarch
PO Box 309
Deerwood, MN 56444
Send privacy questions and requests to [email protected] or through the contact form.