ARCHIVE / PRIVACY POLICY
Privacy Policy
What archive uses, what stays on your device, and the choices you have.
Effective November 13, 2026
This policy covers the archive iOS app (listed as archive That), the archive web app, the archive extension for Chrome, text-to-save, and this website, operated by Clova Inc. Contact us at contact@joinclova.com about privacy or your data.
Information we use
Account information. In versions that offer sign-in, we use Supabase to handle your account, email address, account identifier, authentication credentials, and sessions. If you choose Google sign-in, Google provides basic profile information such as your name, email address, and profile image. Google sign-in does not grant archive access to your Gmail or social saves. If you choose Sign in with Apple, Apple provides an account identifier and either your email address or a private relay address. We retain an encrypted Apple authorization token on our server so we can revoke the connection when you delete your account. Earlier versions work without an account.
Your reference library. When you are signed in, the things you save are stored in your archive account on our servers so you can see them in the web app, the apps and the Chrome extension. Earlier versions that work without an account keep quiz answers, taste profile, source follows, saves, opened references, and feedback on your device and use them there to personalize your collection. Some things stay only on the device that made them: the Chrome extension keeps pending drafts and saves that have not been confirmed yet in that browser until they are saved to your account or removed. Signed-in versions separate local libraries by account. On iOS, session tokens are stored using iOS Keychain. Device backups are governed by your Apple settings.
Network information. Our website host, Vercel, and services you contact receive standard request information, such as IP address, browser or device information, requested URL, and request time, for delivery, security, and reliability. Account services also process technical information needed to authenticate you and prevent abuse. If you email support, we receive the information you send and use it to respond.
Browser taste test. Take the test opens the archive web app and uses the same quiz as web onboarding. Choices and setup preferences are saved in local storage on the web app origin so you can resume after a refresh or return visit. Starting the test again through the website replaces that browser draft; it does not delete an existing account profile. You can see a browser-calculated result before signing in. Continuing to save your result with an account sends your quiz and setup information to the archive account service, where your taste profile is calculated and stored. Existing account profiles require confirmation before replacement. Clear the web app site data in your browser to remove its local draft. Earlier sample-result pages remain labelled as illustrative; opening them does not submit answers.
Web app analytics. The archive web app uses PostHog, a product analytics provider, to understand how the web app is used. It reports page views (the page’s address without the part after “?” or “#”), sign-ups and sign-ins with the method used, and when you create a save (only its type: link, note or image), create a collection, request Feeds, or link text-to-save, along with basic browser, device, screen, language and time zone details. When you are signed in, these are linked to your account identifier, and your email address is added once to your analytics profile. It does not report what you save, notes, titles, link addresses, searches or messages, and it does not record your screen or clicks. It does not start when your browser sends Do Not Track or Global Privacy Control, and it keeps its identifiers in your browser’s local storage rather than a cookie.
Service analytics. Our servers also use PostHog to record completed text-to-save saves, Feeds runs, and Chat or messaging-agent turns. These events are linked to your account identifier and include only the save type and count, feature or channel used, status, and counts of cards, requests or steps. The events do not include message text, saved content, page addresses, notes, titles, phone numbers or email addresses. They can be associated with the web analytics profile described above. These service events are separate from analytics running in the browser.
Website waitlist. When you join the waitlist, we collect your email address and signup date. Vercel processes the submission and we store these details in a private Notion database. We use this information to manage early access and contact you about archive, including launch updates.
archive for Chrome. The Chrome extension saves things you choose on web pages to your archive account. Its toolbar button and right-click menu work on the page you choose. If you turn it on for web pages (it asks once after install, and Chrome asks you to allow it), it also shows a Save button on pictures and posts and a small archive folder in a corner of the pages you visit. To place the folder and move its eyes, the extension looks at the page’s layout and your pointer position in your browser; none of that is sent. Nothing from a page is sent to archive until you save it. When you save, it sends what you saved to your account: a picture’s address, or the picture itself when our servers cannot fetch the address or when you paste or drop an image; a post’s link; text you selected or pasted; a link you pasted; a note you typed; or the page’s address. For pictures and selected text we also store the title and address of the page they came from (without the part after “?” or “#”), and the toolbar button saves the tab’s title unless you change it. Pasted text and links wait for you to press Save; a pasted picture is saved right away and you can undo it for a few seconds. We remove location data from photos before they are uploaded. The folder can show your recent saves; their previews load from our own storage, not from the sites they came from, and the page you are on cannot see them. The extension does not collect your browsing history, the contents of pages you don’t save, or what you type into websites. Signing in uses the Apple or Google window you choose; the extension keeps your session in Chrome’s extension storage in that browser. The list of sites where you hid the folder is kept in Chrome’s sync storage and follows your Chrome sync settings.
Chrome Web Store. The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
How information is shared
Saved links and AI processing. When you save a link or a picture’s address, our servers fetch that page or picture to make a preview and keep a copy, so the website receives a request from archive rather than from your browser. For some sites, requests can pass through Decodo, a network proxy provider, to retrieve content on our behalf. Pictures and files you upload are stored with Amazon Web Services. To describe your saves and make them searchable, and to show you related things in Feeds and answer questions in Chat, we send saved content to AI model providers: Google (Gemini) and OpenAI. We use them only to provide archive, never for advertising.
Text-to-save. When you use text-to-save, Photon, our messaging service provider, receives your phone number and the contents of the messages you send to deliver them to Archive.
We use service providers to host the website, authenticate accounts, store waitlist submissions in Notion, and handle support. They process information needed to provide those services. We may also disclose information when legally required, to protect people and our services, or as part of a business transfer subject to applicable privacy protections. We do not sell personal information or share it for cross-context behavioral advertising.
The app can check collection metadata with the Art Institute of Chicago. Opening a source or creative link sends you to a third-party website, which receives your request information and applies its own privacy policy. Sharing a taste card uses the iOS share sheet; information goes only to the destination you choose. The current apps have no advertising. The Chrome extension’s own analytics is disabled in the current store build. The web app and our servers report the analytics described above. This website has no added analytics SDK or advertising cookies.
Retention and deletion
In earlier versions that work without an account, your local library stays on your device until you clear it in archive Settings or remove the app. Removing the app does not itself delete a server account. In signed-in versions, use Settings → Delete account to request deletion of the authentication account and associated server data. Deleting the shared Clova account also removes any associated data from earlier Reminder or Taste versions and disconnects their linked services. It clears this account’s archive library on the device making the request. Offline library files on other devices are not remotely erased. Apple authorization is revoked when its token is available. Contact us if you cannot access the deletion option. We may verify ownership before handling requests.
Removing the archive extension from Chrome deletes the sign-in session and settings it keeps in that browser’s local extension storage; items already saved to your account stay in your archive until you delete them or your account.
Account information is retained while your account is active. Support correspondence and necessary security records are retained only as needed to respond, protect the service, and meet legal obligations. Backup or security copies may remain for a limited period under our providers’ retention processes and are not used to restore a deleted account for normal use.
We keep waitlist details while we manage early access and launch updates. You can leave the waitlist or ask us to correct or delete your entry at any time by emailing contact@joinclova.com from the address you used to sign up. We remove your waitlist entry when you ask to leave or when it is no longer needed for this purpose.
Your choices and rights
You can clear your local library, choose email, Google or Apple sign-in where offered, and choose which links to open or cards to share. In the Chrome extension you can turn off archive on web pages, hide the folder on any site, move it to another corner, or remove the extension; the toolbar button and right-click saving keep working while it is installed. Depending on where you live, you may have rights to access, correct, delete, or receive a copy of personal information, or object to or restrict certain processing. Email us to exercise those rights or raise a concern. You may also contact your local privacy regulator. We do not discriminate for exercising privacy rights.
Security and international processing
We use reasonable safeguards, including encrypted network connections and platform secure storage, but no system is completely secure. Our providers may process information in the United States or other countries. Where required, appropriate safeguards apply to international transfers.
Children
archive is not directed to children under 13. We do not knowingly collect personal information from children under 13. If you believe a child has provided it, contact us so we can investigate and remove it. Regional App Store age ratings may be higher.
Changes and contact
We will update the effective date when this policy changes and provide additional notice where required. Questions or requests: contact@joinclova.com.