RipMap privacy notice

RipMap is a private cut-list and woodworking project application. Optional Google sign-in identifies its single authorized owner. It does not give other Google users access to projects.

Information used for sign-in

RipMap requests only basic OpenID sign-in information and your email address. It checks your verified email address and stable Google account identifier (subject) against the owner identity explicitly configured by the operator. These identifiers are used only to authenticate the owner and protect access, not for advertising or profiling.

RipMap does not request access to your Gmail inbox, Google Drive files, contacts or other Google account content. Workshop project data is not sent to Google as part of sign-in. Google processes the sign-in request under its own privacy policy.

Storage and cookies

The configured owner email address and account identifier remain in the operator-managed identity configuration until the operator removes or replaces the linked identity. RipMap processes Google authorization codes and tokens to verify sign-in but does not persist raw Google tokens or request refresh tokens.

RipMap uses secure, HttpOnly, same-site cookies for a short-lived sign-in transaction and an authenticated session. A transaction expires after five minutes. A session expires no later than the identity token expiration or one hour, and server restart invalidates active Google sessions. Signed session cookies contain the owner identity and expiry information. These cookies support authentication, not advertising or cross-site tracking.

Project data and local browser recovery copies are separate from Google sign-in. Unlinking Google does not automatically delete projects, local files, browser recovery copies or operator backups. This notice does not promise an automatic deletion schedule for those records.

Sharing and control

RipMap does not sell Google user data or share it with advertisers or data brokers. The application's operator manages the configured owner identity and access. Google receives the information necessary to process its own sign-in flow, not RipMap project contents.

The owner can ask the application's operator to disable Google access or remove the linked identity from the configuration. The owner can also revoke RipMap access in their Google Account connections. Revocation at Google does not instantly terminate an already established RipMap session; it expires as described above, or the operator can invalidate sessions by restarting the service or rotating its session key. Existing owner-password access is independent of Google sign-in.

Return to RipMap sign-in