Privacy policy

The workspace

Base is an internal knowledge base operated for an invited team. The workspace operator is responsible for membership, content, and server administration. Contact the operator at zeroinforce@gmail.com about privacy, access, correction, or deletion requests.

Google sign-in

We request only Google identity and email permissions. Google supplies an account identifier, email address, and email verification status. Base uses these to verify sign-in and bind an active local member to that Google identity. We store this identity connection, but do not retain Google access, refresh, or ID tokens after authentication. We do not import your Google profile name or photo or access your Gmail, Drive, contacts, or calendars. Base never receives your Google password.

Information stored in Base

Your membership includes the email, first and last name entered by the team or updated by you, role, active status, and creation and update times. Shared content includes posts, uploaded images and videos, filenames, authorship, editing ownership, and update times. Search indexes the title and body of stored posts.

Each post records a visit count and the latest visit time for each reader. Other members can see the post's total views, reader names, and latest visits. Short-lived visit receipts prevent duplicate counting. Authentication records include sessions, expiry times, IP addresses, and browser user-agent information. Operational logs may include technical request and error information used to run and protect the service.

Use, access, and hosting

Information is used to provide sign-in, enforce permissions, display and search team knowledge, show collaboration activity, and operate manual backups. Active members can read shared posts and attached files. Editors and the administrator can see the member directory; the administrator can manage access and export data. The server operator can access stored data while administering the service.

Application data and server-side backups are stored on a DigitalOcean server in New York, United States. The application does not sell information, use advertising analytics, or send post content to Google for sign-in. Google handles authentication under its own privacy policy. Embedded YouTube videos contact YouTube from your browser when their player loads, even before playback; external links can take you to other services with their own data practices.

Cookies and local preferences

Essential cookies support sign-in and your session. Base also stores your light/dark theme preference in your browser. It does not use advertising or analytics cookies. Google and YouTube may use their own cookies when you interact with those services.

Retention and your choices

Base stores the latest version of a post, without revision history. Archived posts, membership records, and visit totals remain stored until the operator removes them; deactivating a member removes access but does not erase their contributions. Signing out invalidates the current session. You can update your local name in My profile and ask the operator to correct or delete other information. There is no self-service account deletion. You can also remove Base's connection in your Google account, which does not itself delete data already stored in Base.

Backups are created or imported only when the administrator requests them. They contain member names and emails, posts, media, and retained activity, and remain until deleted. The administrator can download copies outside the server. Deleting live data does not automatically remove it from existing backup copies, and restoring a backup can bring that data back. Coordinate deletion requests and retained copies with the operator.