In force since November 5, 2026 · version 28
Privacy policy
Who decides about the data
69.337.655 GABRIEL DE CASTRO SODRE, CNPJ 69.337.655/0001-56, Brazil. Contact for personal data matters: [email protected].
What we collect
From the account: e-mail, office name, logo, password (if you create one, stored in a way we cannot read), language and the phone number (WhatsApp) you give (asked after you subscribe to a plan, free days included, or buy the pack). From use: the images you send, the generated images, the texts you write, the generation choices. From purchases: plan or pack, currency, amount, billing period, seats, date, method, and payment and subscription identifiers. Card details are entered directly with Stripe and never reach Arch; we keep only a keyed digest of the card identification Stripe gives us, so that free days apply once per card. Technical: a digest of the network address, browser, access date and error records. From the e-mails we send: whether they were delivered, whether they were opened and which links were clicked, kept for 180 days. Ratings of results and presentations: the “yes” or “no”, the reason and what you write. From support: the messages you write in the chat, the e-mail and WhatsApp number you give, the photos and videos you attach and, when the conversation starts from a result, the uploaded image and the generated render or video. So that the free trial is one per person, we also keep, only as a digest, an identifier of the browser (a cookie of ours and technical traits such as screen and fonts); it is not sent to third parties nor used for advertising.
What for, and on what basis
To provide the service and charge for it (performance of a contract). To keep purchase records (legal obligation). To protect against abuse and fix faults (legitimate interest). To reach you on the phone number you gave, for support and account matters (performance of a contract). To send at most three getting-started reminders to people who created an account and have not generated their first image yet, each with a link to turn them off (legitimate interest). To measure the ads: when you create the account, generate the first render, start a payment, start the free days or pay, we tell Meta from our server, whether or not you arrived from an ad, with the e-mail and account identifier as a digest (hash), the network address, the browser, the ad click identifier when there is one and, for payments, the amount and currency (legitimate interest). Turning usage analytics off also stops this. To send news, only if you ask (consent).
Who we share with
Google (the images and generation choices, to analyse and classify the images, including before sign-up, generate and review the renders, and plan and generate the backup video when the main video service does not respond). fal.ai and the models it makes available: OpenAI (the images and generation choices, to generate the renders and the other images and to analyse and classify the images, including before sign-up) and MiniMax, a video model (the starting image, the final image when the video goes from one image to another, and the motion instruction, to generate the video). Stripe (data needed to process the purchase and subscription). Resend (your e-mail and the messages; when you send a presentation, also your client’s name and e-mail). Cloudflare (site delivery, bot check at sign-in, on the image sent before sign-up and on the client site’s code (Turnstile), storage of archived project files and encrypted backups) and the hosting provider. Sentry (error records). PostHog (usage analytics, in the United States). Meta (ad measurement, as described above). Telegram, where our team answers (the support chat messages, the e-mail and WhatsApp number given and the attachments; the “no” ratings of results and presentations, with the uploaded image, the render or video, the generation instructions, the office name, the e-mail and, for presentations, the client’s name and the photos; and an account summary for whoever answers: the latest image and render, the plan, the payment status and the amount paid, the last generations, the device and browser, and the phone number; the internal stalled-payment alerts, with the office name, the e-mail, the offer, the app and system, the browser, the account identifier and the session recording link; and the daily report, with office names and amounts paid). Google and Microsoft, only if you choose to sign in with them: we receive your e-mail and account identifier there, to recognize you. We do not sell data. These providers process data outside Brazil, mostly in the United States; the transfer relies on each one’s contractual data protection terms, with standard clauses where the provider offers them, and, for Telegram, on its terms of service and privacy policy.
What your clients see
Whoever has the presentation link sees the images and texts you chose to publish. When you send the presentation through Arch, we process your client’s name and e-mail on your behalf: you are the controller of that data and we are a processor. We use it only to deliver the link, send confirmation codes, reminders and replies, and record what the client decided (date, revision, requests, and an encrypted digest of the network address and browser). We show you when the link was opened and which rooms were seen, without time per image or location. The client can stop reminders through a link in the e-mail.
For how long
Account and projects: while the account exists, or up to 12 months without access. An image sent before creating the account: up to 7 days, so you can pick up where you left off; when you sign in it moves to your account, and otherwise it is erased with what was made from it. 3D model files sent while Arch still accepted them, and what was taken from them: kept with the project, unused, and erased with it. Deleted images: erased for good within 1 hour. Backups: up to 35 days. Purchase records: 5 years. Sign-in codes: 1 day. Activity of sent presentations (opens, rooms seen): 12 months. Client requests and approvals: while the project exists. Deleted projects: files erased within 30 days. Support conversations and ratings: while the account exists, and erased with it; conversations of people without an account, until deletion is requested. We delete the copies on Telegram by hand when the account is deleted, on request or for inactivity. Internal team alerts: 90 days.
Your rights
To confirm, access, correct, take away and delete your data, and to withdraw consent. Requests are made by e-mail to [email protected], from the account’s e-mail, and answered within 15 days. You may also complain to the Brazilian data protection authority (ANPD).
Usage analytics
Usage analytics is enabled by default. We use PostHog to understand how the product is used and improve it: visits, campaign sources, clicks and screens, created projects, uploads, generations and their results, your clients opening and downloading presentations, purchases, failures and cancellations. We link these data to your account, with e-mail, office name, plan and usage totals, so we can help people who run into trouble. Sessions in the product may be recorded as they appear on screen, including project text and images; passwords and sign-in codes are never recorded. We do not record the site shared with your clients, we only count openings and downloads. PostHog is an additional provider and processes these data in the United States. Configured retention is up to 1 year for events and 30 days for recordings. You can turn it off in the privacy preferences in your account without losing access. Previous opt-outs are preserved. Turning it off stops future collection; contact us to request deletion of previously collected data.
Cookies
We use one cookie to keep your session active, one cookie that keeps for up to 7 days access to the image sent before creating the account, one cookie that identifies the browser to prevent abuse of the free trial, store the language preference, keep for up to 90 days the campaign of the first visit (the link’s utm parameters, such as source and campaign name, and Meta’s click identifier, fbclid, when the link has it), which is recorded on the account when it is created, and, on the client’s site, a cookie that remembers for 7 days that their e-mail was confirmed with the code. While usage analytics is enabled, PostHog stores measurement identifiers in your browser. We use no third-party advertising cookies and no Meta pixel in the browser; the click identifier stays in our cookie and is only sent to Meta as described in “What for, and on what basis”.
Security
Encrypted connection, passwords stored as a digest, sign-in codes that are never written down, restricted access to the servers, encrypted backups of the database and files, several times a day.
Changes
We tell you by e-mail when this policy changes in a relevant way.