Privacy policy
How BASH uses account information, Google sign-in data and essential cookies.
Last updated: 9 November 2026
Information used by the website
BASH at bashservice.cloud stores the name and email you provide for your account, a password hash when you set a password, and the records needed for your saved products, cart, orders, membership and support requests. Authentication sessions and security events help protect accounts. Web-server logs can include your IP address, requested page and request time.
Signing in with Google or GitHub
When you choose Google sign-in, BASH requests only openid, email and profile permissions. We use your verified email, display name and Google account identifier to create a member account or connect an identity to an account you are already signed into. GitHub sign-in similarly uses your provider identifier, name and verified primary email. BASH does not receive your Google or GitHub password. This login does not request access to Gmail messages, Google Drive files or contacts.
How information is used and shared
Account information is used to sign you in, keep your account records together, process your requests, provide support and prevent abuse. Authorized administrators can access information needed for these tasks. Hosting and identity providers process information needed to operate the service. BASH does not sell Google user data, use it for advertising or use it to train AI models. Google sign-in data is used in accordance with the Google API Services User Data Policy, including its Limited Use requirements.
Essential cookies and browser settings
The website uses cookies for authentication and temporary sign-in verification. The remember-device option keeps a session for up to 30 days; signing out revokes that session. Browser storage also remembers settings such as language, motion and the essential-cookie notice. These functions do not require advertising cookies. Your browser can remove stored cookies and preferences, which may sign you out.
Storage, retention and your choices
Account and service records are stored on the BASH server and in private backups. HTTPS protects connections, passwords are hashed and server access is restricted. Records are kept for operating your account, fulfilling requests and addressing security or record-keeping needs. To request access, correction or deletion, contact BASH support; we may need to verify account ownership and explain any records that must be retained. Removing BASH access in your Google account stops future Google authorization but does not itself delete your BASH account.
Policy updates
This page describes the current website. Material changes to data use will be reflected here. Contact support if you have questions before connecting an identity or sharing information.