Privacy

How ArchConnect handles the information you and your team put in it.

Provisional draft

This page is still being reviewed and may change before launch. The operator's legal details and a contact address will be added after that review.

What ArchConnect stores

  • Your account: name, email address, the account type you chose and the profile details you add (job title, company, phone, photo). Passwords are handled by our authentication provider and are never stored in readable form.
  • The work you and your team put in ArchConnect: projects, tasks, documents and photos, messages, calendar events, quotes and tenders.
  • Your settings, such as notification and appearance preferences.
  • Technical data needed to run the service: sign-in sessions, and your IP address and email address when you sign in, sign up or reset a password, to limit repeated attempts.

Who can see your information

  • Project content is visible to the members of that project, according to their role.
  • Your email address and phone number are shown only to people you share a project or a company with.
  • Personal calendar events (not part of a project) are visible only to you and the people you invite. Teammates who share a project with you can see that you are busy, never what the event is.
  • When you leave a project or are removed from it, you lose access to its content straight away.

Services that process data for ArchConnect

  • Supabase: database, sign-in, file storage and live updates.
  • DigitalOcean: the server that runs the ArchConnect app.
  • Resend: delivery of ArchConnect's emails (for example invitations and the daily messages summary).
  • Stripe: subscription payments. Card details are entered with Stripe and are not stored by ArchConnect.
  • Cloudflare Turnstile: a check against automated sign-ups and password-reset requests.
  • Upstash: counting sign-in, sign-up and password-reset attempts to block abuse.
  • Sentry: error reports, so problems can be found and fixed.
  • Google Maps: maps of project locations are loaded from Google in your browser.

Optional connections and notifications

  • Sign in with Google, if you choose it.
  • Google Calendar or Outlook: ArchConnect copies your events into a separate “ArchConnect” calendar it creates in your account. It never imports events from your calendars. The access you grant is stored encrypted. Disconnecting stops the sync and deletes that access; the copied events stay in your calendar unless you choose to remove them. Copies of events you no longer have access to are removed.
  • Push notifications, per device, only if you turn them on. They never include message text or task titles.
  • A daily email summary of unread messages, which you can turn off in Settings or with the link in each email.

Cookies and browser storage

ArchConnect uses only the cookies it needs to work: your sign-in session, and a short-lived cookie while you connect a calendar.

Your browser also keeps some interface preferences on your device: the theme, whether you have seen the introduction tour, the sidebar and list layout, and recently opened projects.

There are no advertising or analytics trackers.

Your choices

  • Edit your profile and notification preferences in Settings at any time.
  • Disconnect Google Calendar or Outlook in Settings › Integrations.
  • Deleting your account and requests about your data: how to make them will be added here with the contact details (pending).

Still to be completed

After legal review this page will add: who operates ArchConnect and how to contact them, the legal basis for each use of data, how long data is kept, where it is stored and transferred, and how to exercise your rights.