Private account information
Configured app services can store account identifiers, product reactions, choose-again preferences, private notes, comparison sets/items, observed prices and usefulness feedback. Current development authentication is not a production account service; do not place personal data in a shared development workspace.
Personalization
Eligible private experiences and permitted canonical product attributes are used to derive category-specific palate signals and deterministic rankings. My Palate is rebuilt from that evidence rather than a separate permanent belief profile. Comparison-usefulness feedback is private and is not fed into inference/model training by the reviewed implementation.
Venue reports and catalog proposals
Firsthand venue reports and unknown-product proposals are stored separately from private tasting history. Catalog acceptance requires reviewed canonical evidence. Operators may publish or withdraw aggregate venue snapshots after review; reports do not auto-publish. A published version can persist after a source report is withdrawn until an operator refreshes or withdraws that version.
Services and operational records
The configured API and database process account-owned records. Source/catalog integrations are limited by their rights and provenance rules. The deterministic recommendation path does not send your notes or photographs to an external language model. Ordinary API logs omit private request bodies, URLs and authentication values, while retaining bounded operational request/status/timing information.
History corrections and deletion
Personal-tools builds support owned history edits and deletion. Deletion removes experience content but can retain a minimal user/event retry marker to prevent a delayed save from recreating it. These are not an immutable audit history of your personal notes.
Export and account closure
The account export includes stored private activity within bounded limits. Implemented closure removes owned experiences, comparison sets, reports, proposals and usefulness feedback and retains minimal disabled-account metadata to prevent reprovisioning. Canonical catalog provenance, other accounts and already published aggregate versions are separate. Identity-provider revocation and backup retention remain deployment obligations.
Age and release limits
Alcohol-related use is intended for adults of legal drinking age where they live. The service does not sell alcohol or encourage increased consumption. Before a public release, the actual identity provider, storage/backup retention and supported regions must be configured and reflected in the app and policy.
These public pages and support email
These static product pages add no advertising, analytics scripts, account sign-in, tracking cookies or embedded third-party fonts. The website host still receives ordinary connection/request information needed to serve and protect the site. If you email support, your address, message and any attachments are processed by the mailbox/email services to respond and handle the request; provide only what is necessary.
Your choices and requests
Use available app controls, device permissions and the separate data-deletion page for product-specific choices. You may contact support to ask about access, correction, deletion or other privacy rights available to you. Identity and authority must be verified before records are disclosed or changed. No response deadline or outcome is guaranteed by sending an email.
Security and policy changes
No device, hosting service or software system can guarantee absolute security. Protect your device and credentials. Material changes to data practices require an updated policy and appropriate notice before the changed behavior is distributed.
Contact and responsible developer
Developer: Anthony LaVear · Product: Drinkfolio
Email: support@anthonylavear.com
Product support · Data & account deletion