Privacy Policy
Last updated November 12, 2026
Architect is a planner for your tasks, habits, goals and calendar. This policy covers the website at architect.do, the web app at app.architect.do and the Architect Android app. It explains what information Architect collects, how it is used, and the choices you have. "We" and "us" mean Architect Labs LLC, which runs Architect.
What we collect
- Account information. You sign in with Google or with an email address and password (confirmed with a one-time code we email you). We receive your email address and a user ID from our sign-in provider. If you sign in with Google, we also receive your name and profile picture. If you turn on two-step sign-in, our sign-in provider keeps the authenticator key; we never see your codes.
- Your planner content. The tasks, habits, goals, notes, lists, settings and other items you create. These are stored so they sync across your devices.
- Photos you upload. Pictures you upload (for example, to your vision board) are stored in our cloud storage, in a private folder only your account can read, so they appear on all your devices.
- Google data you choose to connect. See "Google user data" below.
- Assistant conversations. If you use the AI Assistant, your messages and its replies are stored in our database. See "The AI Assistant" below.
- Billing information. If you buy a paid plan, see "Payments" below.
- Notification settings. If you turn on notifications, a push subscription for your browser or device, so we can send the reminders and Assistant check-ins you ask for.
- Comments and history. Comments you add to items, and a history of changes (what changed, when, and who made it: you, a person you share with, or an AI app you connected). On shared items, everyone on the share can see them.
- Error reports. When something goes wrong in the app, a short error report (the message, the page and the app version) is added to your activity log so we can fix it.
- Feedback. Anything you send through Help & feedback, along with your email so we can reply.
- Activity log. A record of the actions you take in Architect, such as creating, moving, rescheduling, completing or deleting an item, syncing with Google Tasks, and opening the app, with the time, the device and the item's internal ID. It never includes the words of your tasks, notes or events, or any content from your Google Calendar or Tasks. We use it only to keep sync working, fix problems and understand how Architect is used. It is kept for 45 days, after which only daily counts remain.
- Technical information. Standard information your browser or device sends with any request, such as IP address, browser type and the time of the request. This is used to run and secure the service.
- Information stored on your device. Architect also keeps a copy of your plan and your photos on your device so the app works quickly and offline.
The AI Assistant
When you use the Assistant, our server sends our AI provider, Anthropic, your message, the recent conversation, and the parts of your plan the Assistant needs to reply. That includes your pillars and how you rated them, your goals, visions, projects and habits, your open tasks and today's plan, and your calendar events and time blocks for the next two weeks. Our AI provider uses this only to generate the reply and does not use it to train models. The Assistant can only suggest changes; nothing in your plan changes until you tap Apply.
AI apps you connect
You can connect an AI app of your own, such as Claude, ChatGPT, Gemini, Grok or Muse, in Global Settings › Connections › AI apps. An AI app is connected only when you sign in and press Allow. When it asks, we send it the parts of your plan it asked for: your tasks, lists, habits, notes, goals and pillars, and events on your Architect-only calendar, except anything you marked private in Assistant Settings. Events from Google Calendar are not shared with AI apps. Connecting AI apps is part of the paid plans. When you connect one you choose what it can do: read your plan, also add new items, or also change existing ones (for example mark a task done). It can never delete anything, and every change it makes is listed in AI apps with Undo. What the AI app does with that information is governed by its own privacy policy, not ours. You can disconnect it at any time in AI apps, and it loses access at once.
Google user data
If you connect Google, Architect asks for these permissions:
- Google Calendar (see your list of calendars, and view, create, edit and delete events). This lets Architect show your events beside your tasks and lets you add or change events from Architect.
- Google Tasks (view, create, edit and delete tasks). This lets Architect keep your Google Tasks in sync with your plan.
We use this data only to provide those features to you. We do not sell it, use it for advertising, or use it to train AI models. We do not let people read it, except with your permission, when needed for security or to comply with the law.
If you share a list, notebook or view with someone, the items on it, including any synced from Google Tasks or linked to a Google Calendar event, are visible to the people you share with. Nothing from Google is shared unless you choose to share it.
If you use the AI Assistant, your Google Calendar events and Google Tasks may be included in what we send to our AI provider, only to answer your own requests. Our AI provider does not use it to train models.
Your Google Calendar events are never sent to an AI app you connect (see "AI apps you connect"). Tasks synced from Google Tasks are part of your plan, so a connected AI app can read them, only after you pressed Allow.
To keep you connected without asking you to sign in again, our server stores an encrypted Google access token linked to your account. You can disconnect Google at any time from Architect's Calendar page or at myaccount.google.com/permissions. When you disconnect in Architect, we revoke the token and delete our stored copy.
Architect's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Payments
Paid plans are billed through Stripe. Stripe collects and handles your card details; we never see or store card numbers. We store your plan, its status and your billing email.
How we use information
- To provide Architect: storing and syncing your plan and photos, showing your calendar, sending reminders you set, running the Assistant, and billing paid plans.
- To keep the service secure and working, and to fix problems.
- To reply to feedback and support requests.
- To understand how the app is used and improve it, using the analytics described below.
- To support you and run Architect: the people who run it can see each account's email address, when it was created and last used, its plan, and how many tasks, lists, habits and notes it has. They do not see what any of it says.
- To learn how people find Architect and why they leave: when you first visit, we note the page you arrived on, the website that sent you and any campaign tags in the link, and keep that with your account when you sign up, along with your answer if you tell us where you heard about Architect or why you canceled a paid plan. Both questions are optional.
We do not sell your personal information.
Services we rely on
We share information only with the companies that help us run Architect, and only what they need to do their job:
- Supabase: sign-in, and storage of your account, planner content, Assistant messages and uploaded photos.
- Cloudflare: hosting, our server, email delivery for feedback, and storing our encrypted backups.
- Resend: sending sign-in codes, sharing invitations and notices to the people you choose to share with.
- Google: Google sign-in, Calendar and Tasks, when you connect them, plus analytics and advertising as described below.
- Firebase Cloud Messaging (Google): on the Android app, so we can tell your phone to remove a reminder once you finish, delete or move that item on another device. We store a device code for your phone with your account; the messages carry only item IDs, never what your tasks or habits say.
- Anthropic: the AI model that powers the Assistant. Only what the Assistant needs to answer is sent, and it is not used to train models.
- Stripe: payments for paid plans.
- Open-Meteo: weather for the Weather block. Only the place name or coordinates you choose are sent.
- News sources: when you use the News block, our server fetches the public feeds you choose.
We may also share information if the law requires it, or to protect the rights and safety of our users or others.
Cookies, analytics and advertising
Architect uses browser storage to keep you signed in and to remember your settings.
We may use Google Analytics to understand how people find and use Architect, such as which pages are visited and roughly where visitors come from. Google Analytics uses cookies and collects information about your device and visits. You can opt out with the Google Analytics opt-out browser add-on.
We may use Google Ads to advertise Architect and measure how well our ads work. Google and other vendors may use cookies to show you ads based on your past visits to our website or other websites, and to tell us when someone who saw an ad later signs up. You can turn off personalized ads at Google Ad Settings or aboutads.info. Learn more at How Google uses information from sites that use its services.
Architect itself sets one cookie, on architect.do, to remember how you first arrived (described above) until you sign up. It is not shared with anyone.
Analytics and advertising tools never receive your planner content or your Google Calendar or Tasks data.
How long we keep information
We keep your account, planner content, photos and Assistant messages for as long as your account exists. The activity log is kept for 45 days; after that only daily counts of each kind of action remain, until your account is deleted. When you delete your account, we delete your content from our systems within 30 days, apart from backups, which roll off within a further 30 days (today our backups are kept for 14 days). Stripe keeps billing records as the law requires. Feedback emails may be kept for as long as they are useful for support.
Your choices and rights
- See, edit or delete your content in the app at any time.
- Download everything — your plan, your tasks as a spreadsheet, your notes and your photos — as one ZIP from Account or Global Settings › General › Export.
- Disconnect Google at any time.
- Delete your account yourself in the app at Account › Delete account, or by following architect.do/delete-account. You can also ask us for a copy of your information, or to delete your account, by emailing support@architect.do.
Depending on where you live, you may have more rights under laws such as the GDPR or the California Consumer Privacy Act. These include the right to access, correct, delete or move your information, and to object to some uses of it. Email us to use any of these rights. We will not treat you differently for using them.
Security
Information is encrypted in transit. Google tokens are encrypted at rest. Access to your content is limited to your signed-in account. No system is perfectly secure, but we work to protect your information and will tell you promptly if a breach affects you.
Backups during the beta. Architect is in beta. We make an encrypted backup of the service each night and keep it for 14 days, but we can't guarantee that every backup is complete or that lost information can always be recovered. Keep your own copy of anything important: you can export everything, photos included, from Account at any time.
Children
Architect is not meant for children under 13, and we do not knowingly collect information from them. If you believe a child has given us information, email us and we will delete it.
Changes to this policy
If we make important changes, we will update the date above and let you know in the app before they take effect.
Contact
Questions about privacy: support@architect.do.