Privacy policy

Effective date: October 13, 2026

Operator

<placeholder>

Contact email

<placeholder>

Information Nearer collects

Google sign-in supplies your Google account identifier, verified email address, display name and profile image. Nearer stores these details to identify your account, enforce invitations and display people associated with work. Google sign-in requests identity scopes; it does not grant mailbox access.

Nearer stores information you or workspace members enter: project membership, tickets, custom fields, estimates, dates, comments, mentions, watchers, dependencies, review requests, time logs, attachments, workflows, boards, dashboards, saved searches and personal favourites. Change and administrative history records actors, timestamps and before/after values.

How information is used and shared

Information is used to authenticate accounts, operate project features, enforce access, deliver notifications, diagnose failures and maintain the service. Authorized project members can see project information according to their roles. Organization administrators can access and manage organization data; authorized operators may access it for service administration, support and security.

Cloudflare processes the service's requests and stores records and attachment objects through Workers, D1 and R2. Google handles authentication and, when connected, email sending. A configured GitHub integration accesses selected repositories to show linked development activity. These providers process information under their own terms and policies. No particular storage country or exclusive regional residency is promised.

Gmail authorization and notifications

An administrator may separately connect one shared Gmail sender using send-only authorization. Nearer stores the sender identity and an encrypted refresh credential to send configured notifications. Nearer does not request permission to read the sender's mailbox or retrieve incoming messages.

Email notifications disclose the ticket key, title, event summary and secure application link to authorized notification recipients. Project access is checked before delivery. Recipients' email providers also process delivered messages. You can change your email preference in settings, revoke sessions, or ask an administrator to disconnect the integration; previously delivered emails cannot be withdrawn.

Google API data and Limited Use

Nearer's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. Google data is used for the disclosed authentication and notification features. It is not sold, used for advertising, or used to train generalized artificial-intelligence models. Human access and transfers are limited to the policy's permitted circumstances, such as authorized feature delivery, security, legal obligations and user-approved support.

Optional GitHub integration

When an administrator configures a GitHub App, Nearer stores selected repository and installation identifiers, verified webhook delivery identifiers and linked branch, commit and pull-request metadata. It does not automatically transition tickets or synchronize GitHub issues in both directions. Disconnecting a repository removes the application's association; GitHub authorization can also be revoked through GitHub.

Cookies, browser storage and logs

Nearer uses necessary authentication and temporary OAuth cookies. Sessions expire after seven days unless revoked earlier; temporary authorization state expires after ten minutes. Browser storage remembers interface preferences such as theme, selected project and dashboard, and expanded favourite sections. Favourites themselves are stored with your account.

Cloudflare and the service may process request metadata and operational logs, including timestamps, network information and errors, for delivery, debugging and security. Nearer currently adds no advertising cookies or third-party marketing analytics. Retention of provider logs is governed by the configured provider service.

Storage, security and retention

Records are stored in D1 and attachment binaries in private R2 storage. Project access is checked by authenticated APIs, and integration refresh credentials are encrypted. These controls do not guarantee that every security incident can be prevented.

Project records and audit history are retained while needed to operate the workspace; suspending an account or removing membership does not automatically delete authored records. Expired session and authorization records are periodically removed. Workspace backups and previously delivered email may retain copies. Nearer does not currently provide a self-service account-deletion process or promise a fixed deletion deadline.

Your controls and requests

You can edit information where your role permits, change email preferences, sign out and revoke your sessions. Administrators can manage membership, suspend accounts, disconnect integrations and export workspace backups. Contact your workspace administrator for access, correction, export or deletion requests; retained audit records and shared work may require additional handling.

The service contact address is currently <placeholder>. Until a working address is published, invited users should use their existing contact with the workspace administrator. Rights and obligations under applicable law are not reduced by this draft.

Changes

This page will be updated as the service changes. Material changes to Google-data use require updated disclosures and applicable consent before the new use begins.