Account and access
Email identity, authentication state, membership roles, and security events support sign-in and authorized access.
Privacy by purpose
Privacy at PourRoster
This internal MVP notice explains how account, organization, and relationship data is used to operate PourRoster. It is not a final public legal notice.
Internal MVP scope
A final legal review and public privacy notice are required before public launch.
What the service needs
Data with an operational purpose
Business profiles
Organization, location, license, catalog, and seller-path information supports verification and public discovery.
Relationship activity
Inquiries, visits, and related status changes help participants coordinate and retain an understandable history.
Governance evidence
Review decisions, audit events, and privacy-request records support accountable administration of the service.
Boundaries and controls
How information is handled
Visibility follows the feature
- Approved public directory information is visible to directory visitors.
- Account, inquiry, visit, and governance records are limited by authentication and role.
- Uploaded evidence is handled separately from public profile content.
- Operational audit records may be retained to preserve accountability and investigate changes.
Your choices
Signed-in users can manage notification preferences. Privacy requests and account access
questions should be directed to the PourRoster organization administrator during the internal MVP.
Service boundary
What PourRoster is not collecting for
PourRoster stores supplier-controlled offers, order status, and retained order history. The producer or licensed seller remains seller of record and controls acceptance, inventory, delivery, beverage invoicing, and payment; PourRoster does not receive beverage-sale funds or store payment credentials. Sampling and sponsored ranking are not provided. Those commercial transactions remain outside the current product scope.