SVSipventoryYour Personal Spirits Collection
Back to SipventoryPrivacy PolicyTerms of Service

Sipventory Privacy Policy

Effective date: October 16, 2026

1. Who we are and what this policy covers

Sipventory is a website for organizing a personal spirits and bottle collection. This Privacy Policy explains how Sipventory ("Sipventory," "we," "us," or "our") handles personal information in connection with sipventory.com and the features described here (the "Service").

Privacy contact: ammonsrocco@gmail.com.

This policy covers our handling of information. Third-party services, including Google, also handle information under their own notices when you use their services. A link to a third-party policy does not replace our responsibility for our own processing.

2. Information we collect

Account and sign-in information. When you sign in with Google through Supabase, we receive your Google account identifier, Supabase user and session identifiers, email address, verification or confirmation information, and name or display name. Available profile metadata, such as your profile picture, may also be returned. We use this information to authenticate you, display your account identity, and associate your collection with your account. We do not receive your Google password through Google sign-in.

Email and password accounts. When you create or use an email account, we process your email address, confirmation status, Supabase account and session identifiers, and the credentials you submit over an encrypted connection. Supabase manages password storage and authentication. Sipventory does not persist or log plaintext passwords. We use the confirmed account identifier to associate your collection with your email account.

Collection information. We store the bottle information you save, including brand, expression, producer or distillery, style, proof, size and age; ratings and free-text notes; sealed or opened status; acquisition and opening dates; bottle weights, weigh-in times and history; estimated remaining volume, fill levels and pours; estimated used or lost amounts; calibration information and uncertainty; and record timestamps and the owner identifier. These records can become personal information when linked to your account. Please avoid entering other people's information or unnecessary sensitive details in notes. The current Service does not accept user photo or file uploads.

Communications. If you contact us, we receive the contact information and content you provide and records needed to respond to your request.

Technical and security information. Authentication and infrastructure providers process technical information needed to deliver and protect the Service, which can include IP addresses, browser or device information, request information and security events. The Service also processes authentication session information and tokens.

Earlier accounts. Information saved through the earlier Sites/OpenAI sign-in system remains associated with its original identity and collection. Signing in with Google or email does not, by itself, transfer those earlier records to the new identity. A supported recovery or account-association process may be needed to access an earlier collection.

3. How we use information

We use the information described above to:

  • Create, authenticate, and maintain accounts and sessions.
  • Save, retrieve, display, and maintain your collection and the Service's catalog features.
  • Respond to support requests and privacy requests.
  • Diagnose errors, maintain reliability, and protect accounts and the Service against misuse and unauthorized access.
  • Send necessary account, security, policy, or service notices through available contact channels.
  • Meet applicable legal obligations and establish, exercise, or defend legal claims.

The current Service does not include advertising, marketing-tracking integrations, application analytics, or AI inference features.

4. Sign-in and account emails

Google provides identity information through the openid, email and profile permissions, and Supabase manages authentication. We use that information for sign-in, account display and association of your private collection with your account. We do not request access to your Gmail messages, Google Drive files, Google Contacts or Google Calendar. The Service does not use Google sign-in information for advertising.

You can review or remove Sipventory's access in your Google Account's third-party connections settings. Removing that connection may prevent future Google sign-in; it does not by itself delete information already stored by Sipventory. To request deletion, follow Section 8.

Email/password accounts require email confirmation. Supabase manages confirmation and password recovery, and account emails are delivered through the configured Resend email service. These providers process the address, message content and delivery information needed for confirmation, recovery and account security. These messages are transactional, not marketing. Using the same email address through another sign-in method does not automatically combine collections.

5. Cookies and browser storage

The Service uses authentication cookies to complete sign-in and maintain your session, and Sites/Cloudflare infrastructure uses cookies for security and visitor handling. App-managed cookies use secure, host-restricted settings. Supabase sessions can include access and refresh tokens and, when returned, provider tokens; these are authentication credentials, not your Google password. The application uses temporary sign-in and email-link verification cookies and stores hashed versions of its sign-in intent, recovery-grant and session-binding tokens. Google sign-in intent expires after 10 minutes, email confirmation or recovery intent after one hour, a password-reset grant after 10 minutes, and an application session binding after 30 days. We also use hashed email-address information in temporary counters that limit authentication attempts. Expiration is not the same as immediate physical deletion.

You can manage cookies and site data through your browser. Blocking or deleting storage needed for authentication may sign you out or prevent account features from working. Clearing browser storage does not delete information stored in your account on our systems.

The current application has no cookie-preference interface or application-level cross-site advertising integration.

6. When information is shared

Service providers. Google supplies the identity service you choose; Supabase provides managed authentication; Resend delivers transactional account emails through the configured email service; OpenAI/ChatGPT Sites provides site infrastructure and the earlier sign-in system; and Cloudflare provides hosted application, database and edge-security infrastructure. These providers process the information needed for their roles.

Private collections and operational access. Collection features are account-specific and do not include public collection sharing. The application's catalog-administrator feature is read-only and does not expose users' personal inventories or weigh-in histories. Infrastructure-level privileges are separate: authorized operators or providers may have access needed for operation, troubleshooting, security or legal obligations.

Legal and safety reasons. We may disclose information when required by applicable law or when reasonably necessary to address fraud or security threats, protect rights or safety, or establish, exercise, or defend legal claims.

Business transitions. If the Service is involved in a merger, acquisition, financing, reorganization, or transfer of assets, relevant information may be disclosed subject to appropriate safeguards and applicable law. We will provide notice where required if responsibility for your information changes.

At your direction. We may disclose information if you specifically direct or authorize us to do so.

The current application has no advertising or marketing-tracking integrations.

7. Retention and security

Your inventory, notes and weigh-in history remain stored until deleted; the current application does not automatically purge them based on age. Removing one of your bottles also deletes its associated weight history from the active application database. This does not necessarily remove related provider logs or backups.

Expired sign-in intent, email confirmation or recovery intent, password-reset grant, session-binding and temporary authentication-attempt records are cleaned up during subsequent authentication activity, rather than guaranteed to be physically erased at the exact expiration time. Provider-managed account records, logs and backups have separate retention practices. A deletion from the active application database does not mean every provider-held copy is immediately erased.

We use account-scoped access controls, protected application cookies and hashed application binding tokens to help protect information. No method of internet transmission or electronic storage is completely secure. Please protect your sign-in account and tell us promptly if you suspect unauthorized access.

8. Your choices, requests, and rights

You can manage your collection and remove individual bottles and their associated weigh-in history through the Service. The current Service does not offer a dedicated full-account deletion or full-account export/download interface. For access, correction, deletion or account-closure requests, contact ammonsrocco@gmail.com. If your collection is linked to an earlier account, tell us which sign-in method you used so we can locate the relevant records. Do not send us your password.

Depending on where you live and which laws apply, you may have rights to obtain a copy of your information, correct it, delete it, restrict or object to certain processing, withdraw consent, or receive information in a portable format. You may also have rights to opt out of certain sales, targeted advertising, or profiling, to use an authorized agent, or to appeal a denied request, where applicable. These rights can be subject to legal exceptions.

We may take reasonable steps to verify your identity before fulfilling a request and request only information appropriate to that verification. We will respond within the period required by applicable law, explain applicable limitations, and will not unlawfully discriminate against you for exercising your rights.

9. International processing

The Service relies on the providers identified above. Information may be processed in countries other than the country where you live, where privacy laws may differ. Using the Service does not waive legal protections that apply to your information. You can contact us with questions about processing locations and applicable safeguards.

10. Children

The Service is intended for adults and is not directed to children. If you believe a child has provided us personal information, please contact us so we can investigate and take appropriate steps. This statement does not represent that the Service verifies every user's age.

11. Changes to this policy

We may update this policy as the Service or our practices change. We will publish the revised policy here and update its effective date. For material changes, we will provide additional notice by a prominent notice on the Service where appropriate or required, and obtain consent when required by law. Changes will not retroactively authorize uses that require separate permission.

12. Contact

Questions or privacy requests: ammonsrocco@gmail.com. Service: Sipventory.

Questions? ammonsrocco@gmail.com

Privacy PolicyTerms of ServiceBack to top
Privacy Policy | Sipventory