Maxx Lab
← Covefold

Covefold privacy policy

Effective September 16, 2026

Covefold is developed by maxx lab TBD, the studio behind Maxx Lab. This policy covers Covefold and its pages on maxxlab.dev. Other Maxx Lab products are outside its scope.

Covefold is currently in development. Online features depend on the test build and your account. This policy describes those features when available; it is not an announcement of a public release.

1. What stays on your device

Saved notes, links, images, PDFs, files, recordings, tags, collections, search data and saved AI results are stored in the current installation. You can use the local library without an account. We do not keep a permanent copy of your library on our servers or provide library synchronization or a backup service.

Camera, microphone, photo and location access are used for the capture actions you choose and are subject to device permissions. If you add location, the app can save a place label and coordinates locally; imported photos can also contain location metadata. Apple’s system location, map and geocoding services may process information needed to resolve or display a place. Covefold does not send those saved coordinates to its account, browser relay or analytics services.

Loading a saved page, its preview or its site icon contacts the website and possibly its image or other content hosts. Those hosts can receive ordinary network information, such as your IP address, under their own privacy policies. The app uses separate web sessions rather than your Safari cookies.

2. Google sign-in and account information

If you choose Google sign-in, Google shares your account identifier, email address and verification status, and basic profile information such as your name and profile picture, with our authentication service, Supabase Auth. We use this information to authenticate you, associate your session with your Covefold account and provide account-related features. We do not receive your Google password or request access to Gmail messages, Google Drive files, contacts or calendars.

Email sign-in uses your email address to send a one-time code through the authentication and email-delivery services. Account records can include your account identifier, sign-in provider, sessions, registered devices or browser extensions, language preference, account timestamps and subscription or feature-access status.

Google account information is not sent to AI models as part of a sign-in request. Our use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

3. Information used by optional online features

Browser capture. When you explicitly send a page from a paired desktop browser, its URL, title, approved page metadata and captured content pass through a temporary Supabase relay so your iPhone can receive them. A pending encrypted capture can remain in that browser profile for up to 24 hours. An accepted server package becomes unavailable after your app acknowledges receipt or seven days after acceptance, whichever comes first; cleanup retries remove the stored object. This is temporary transfer, not cloud backup. Authorized service components can process the package, so we do not describe it as end-to-end encrypted.

AI features. When available, asking for link enrichment or sending a question to the resource assistant transmits the selected content needed for that request, your question and relevant conversation context through Cloudflare Workers and AI Gateway to the configured model provider. The current development configuration uses OpenAI. These actions do not send your whole library. Request and response content is handled transiently by our service; saved results remain in your local library. Content-free gateway records, including pseudonymous usage identifiers, model, timing and estimated usage, may be retained for up to 35 days. These records are not anonymous.

We do not use your content to train models. Public AI availability depends on completing provider and infrastructure retention checks; this policy does not promise that every service provider has independently verified zero retention. We will update provider disclosures before enabling a new public data-processing route. Cloud transcription is not currently available.

Subscriptions and testing. If enabled in your build, Apple handles store purchases and RevenueCat processes purchase and entitlement information associated with your account identifier. We do not intentionally send your saved content or email address to RevenueCat. Apple may also process TestFlight installation, session and crash information under its own terms.

4. Service providers, security and sharing

We use Google for Google sign-in, Supabase for authentication, account services and temporary browser transfer, and Cloudflare for hosting, request delivery and the AI gateway. OpenAI processes explicitly requested AI content in the development configuration. Apple provides platform services and, when enabled, Apple and RevenueCat provide purchase processing. Providers may process data in countries other than yours under their service terms and safeguards.

We use encrypted network connections and restricted service access. Network services necessarily receive request information such as IP addresses. Operational and security records help keep the service reliable and prevent abuse. We do not sell personal information, use it for targeted advertising, or add third-party product analytics, session replay or cross-product tracking to Covefold.

Information may also be disclosed when needed to comply with a legal obligation or protect the security and rights of users. If you email support, we receive the address and information you choose to include and use it to respond. Please do not send passwords or unnecessary private library content.

5. Retention and deletion

These are Covefold’s product retention rules. Service-provider records and legal retention obligations can have separate requirements; we do not promise to erase records controlled independently by Google, Apple or other providers on the same schedule. Provider configuration and deletion checks remain part of preparation for public release.

6. Your choices and privacy requests

You can use the local library without signing in, choose whether to use online features, revoke paired extensions, and manage camera, microphone, photo and location permissions in device settings. Use the account-deletion control in Covefold to request removal of your online account, or contact us if you cannot access it.

You can remove Covefold’s Google connection in your Google Account connections. Revoking Google access is separate from deleting the Covefold account or its local library. Manage paid subscriptions through the store where you subscribed.

Depending on where you live, you may have rights to access, correct or delete personal information, receive a copy, object to or restrict processing, or withdraw consent. Email maxxlabtbd@gmail.com with your request. We may need to verify that it concerns your account. We cannot retrieve a device-local library from our servers.

7. Contact and changes

For questions about Covefold privacy, contact maxx lab TBD at maxxlabtbd@gmail.com. We will update this page and its effective date when practices change, and provide notice or obtain consent where required before using information for a new purpose.