Observer

Privacy Policy

Effective May 27, 2026

Observer LLC("Observer," "we," or "us") operates Observer OS, a creative operations platform offered through the website at os.observer.studioand accompanying iOS and Android applications (collectively, the "Service"). This policy explains what information we collect, how we use it, who we share it with, and the rights you have over it.

Observer OS is currently offered through a private waitlist and invited workspaces. By joining the waitlist, accepting an invitation, or otherwise using the Service, you agree to this policy. If any term is unacceptable, please do not use the Service.

Who we are

Observer LLC is a limited liability company registered in the Arab Republic of Egypt. For all privacy-related questions or requests, contact us at hi@observer.studio. We act as the controller of personal data processed through the Service.

Information we collect

Account & workspace data

When you sign up (via waitlist or workspace invitation), we collect your email address, display name, profile picture (if provided), and the workspaces, roles, and permissions associated with your account. Authentication is handled by Clerk; if you sign in with a third-party identity provider (e.g. Google), we receive the basic profile fields that provider returns.

Workspace content

When you use the Service, you and the people you invite create content — projects, tasks, comments, time entries, files, notifications, client records, custom fields, automation rules, and similar. We store this content on your behalf to operate the Service. We treat it as confidential and access it only to provide, secure, and improve the Service or where required by law.

Imported data

If you connect a third-party system (e.g. ClickUp, Google Drive), we receive only the data you explicitly authorize us to import or access on your behalf. We do not pull data from any service you have not explicitly connected. Connections can be revoked at any time from the integrations settings.

Communications

If you contact us, join the waitlist, or receive product or transactional emails (invitations, notifications, password resets), we retain those records for support, audit, and product purposes.

Device & usage data

We automatically collect technical information necessary to operate the Service: IP address, browser and operating system information, device identifiers, app version, timestamps, error reports, and in-app actions (e.g. a project was opened, a task was completed). On mobile, we may access local secure storage for authentication tokens and use push notification tokens to deliver notifications.

Cookies & similar technologies

We use strictly necessary cookies and similar technologies for authentication and session management. We do not use third-party advertising or cross-site tracking cookies. Where required by law, we will request your consent before setting any non-essential cookies.

How we use information

  • To operate, maintain, and improve the Service.
  • To provision accounts and workspaces, send invitations, and enforce access controls.
  • To deliver transactional and product notifications you have opted into.
  • To respond to support requests and communicate operational changes.
  • To detect, prevent, and respond to fraud, abuse, security incidents, and other harmful activity.
  • To comply with legal obligations and to establish, exercise, or defend legal claims.
  • To analyze aggregated, de-identified usage so we can prioritize features and fixes. We do not sell personal information.

Where the General Data Protection Regulation (GDPR) or analogous law applies, we rely on the following lawful bases: (a) performance of a contract with you to provide the Service; (b) our legitimate interests in operating, securing, and improving the Service; (c) compliance with legal obligations; and (d) your consent where required (e.g. for non-essential cookies or marketing communications). You may withdraw consent at any time without affecting prior processing.

How information is shared

We do not sell personal data. We share information only as described below:

  • Within your workspace. Content you create is visible to other members of that workspace according to their role and the access controls you configure.
  • Service providers (sub-processors). We use a small set of vetted vendors to operate the Service. Each is bound by data protection terms.
  • Legal & safety. We may disclose information when we have a good-faith belief it is required to comply with law, legal process, or a lawful government request, or to protect the rights, property, or safety of Observer, our users, or the public.
  • Business transfers. If Observer is involved in a merger, acquisition, or asset sale, your information may be transferred subject to standard confidentiality protections and the continuing application of this policy.

Sub-processors we use today

  • Clerk (authentication, session management, user profiles).
  • Neon (managed Postgres database hosting).
  • Vercel (web hosting, edge runtime, logs).
  • Resend (transactional email delivery for invitations and notifications).
  • Google (only if you choose to connect Google Drive or use Google sign-in).
  • ClickUp (only if you choose to import data from ClickUp using your API token).
  • Apple (TestFlight and App Store distribution metadata) and Google (Play Store distribution metadata) for the mobile applications.

International data transfers

Our sub-processors operate infrastructure in jurisdictions including the United States and the European Union. Where personal data is transferred from a country with data export restrictions (e.g. the European Economic Area or the United Kingdom), we rely on contractual protections such as the Standard Contractual Clauses and, where applicable, additional technical safeguards.

Data retention

We retain account and workspace data for as long as your account or workspace is active. When a workspace is deleted, we delete or anonymize its content within 30 days, except where a longer period is required to comply with legal obligations, resolve disputes, or enforce our agreements. Backups are purged on a rolling 35-day cycle.

Security

We apply industry-standard technical and organizational measures to protect the Service: encrypted transport (TLS), encryption at rest for databases and backups, role-based access controls, least-privilege operational access, secret rotation, and dependency monitoring. No method of transmission or storage is 100% secure; we cannot guarantee absolute security, but we work continuously to improve our defenses.

Your rights

Depending on where you live, you may have the following rights with respect to your personal data:

  • Access a copy of the personal data we hold about you.
  • Correct inaccurate or incomplete information.
  • Delete your personal data, subject to limited legal exceptions.
  • Restrict or object to certain processing, including direct marketing.
  • Receive a portable copy of your data in a structured format.
  • Withdraw consent where processing is based on consent (this does not affect lawfulness of prior processing).
  • Lodge a complaint with your local data protection authority.

To exercise any of these rights, email hi@observer.studio. We will respond within the timeframe required by applicable law, typically within 30 days. We may need to verify your identity before acting on a request.

Children's privacy

Observer OS is intended for adult professional use and is not directed to children under 16. We do not knowingly collect personal data from children under 16. If you believe a child has provided information to us, please contact us so we can remove it.

Mobile app permissions

The Observer iOS and Android apps request only the permissions necessary to function. These currently include:

  • Notifications— to deliver task, mention, and workspace activity updates you have opted into.
  • Secure storage / Keychain— to keep your session token on-device so you remain signed in.

We do not access your photo library, microphone, camera, contacts, or precise location. We do not perform cross-app tracking, and we do not use the Apple Identifier for Advertisers (IDFA). The apps do not contain third-party advertising SDKs.

Changes to this policy

We may update this policy as the Service evolves or to reflect legal and operational changes. When we make material changes we will notify active accounts by email and update the "Last updated" date above. Continued use of the Service after a change indicates acceptance of the updated policy.

Contact

Questions, requests, or complaints regarding this policy can be sent to hi@observer.studio. We treat every privacy request seriously and reply individually.