This policy explains the public Vessa Marlowe website and Vessa Social Automation, the private, owner-operated application used to organise the Vessa YouTube channel. They are separate: browsing this website does not authorise access to your Google account.
1. Who to contact
The Vessa Marlowe project operates this website and the private application. For privacy questions, access requests, corrections or deletion requests, email vessamarlowe@gmail.com. Do not send passwords or access tokens.
2. What this website collects
There is no visitor account, checkout, newsletter database or on-site contact form in this release. When you click an email link, your email provider sends the message and the project receives the details you include. The hosting provider, Netlify, may process technical request information such as IP address, browser information, requested URL and time to deliver and secure the website.
The “Save recipe” feature stores recipe identifiers in your browser’s local storage only when you use it. They are not sent to the project. Remove a saved recipe using its heart button, or clear this website’s browser data to remove the saved list. Ingredient checkmarks remain on the current page and are not sent to a server.
3. Fonts, videos and external services
Fonts load from Google Fonts, which receives the technical information needed to serve them. No advertising pixels or third-party audience analytics are deliberately installed by this site. YouTube embeds are not loaded until you press a video button. At that point, the browser contacts YouTube’s privacy-enhanced player; YouTube may process data under its own policies. External social links lead to services with their own practices.
See the Google Privacy Policy and Netlify Privacy Policy.
4. Vessa Social Automation and Google data
Vessa Social Automation uses the YouTube Data API with the channel owner’s explicit OAuth authorisation. It currently reads the authorised channel’s identity, uploaded-video metadata, playlists, playlist items and channel sections. Its intended management actions are organising existing videos into the Kitchen and Studio playlists and managing those channel sections. The available Google permission is broader than a playlist-only permission; the application is intended to restrict its actions to the owner-approved tasks.
The application is not a public sign-in service. It does not request visitors’ Google passwords. OAuth credentials and tokens are stored separately on the operator’s workstation; they are not included in the public website files. Limited channel metadata and operation records may be inspected by the authorised operator using connected, AI-assisted tools. The application does not sell Google user data, use it for advertising, or use it to train general-purpose AI models.
Google API data is used only to provide the described channel-management functions and is handled in accordance with the Google API Services User Data Policy, including its Limited Use requirements. The application uses YouTube API Services and is not endorsed by Google or YouTube.
5. Storage, retention and deletion
Contact messages are retained while needed to respond and manage the related conversation. The private application retains authorisation credentials while the owner chooses to keep the connection active, and limited operation records for troubleshooting and continuity. It does not maintain a separate public database of viewers or YouTube subscribers.
To ask the project to delete stored authorised data, email the contact above. Verified deletion requests for data stored by Vessa Social Automation will be handled within seven calendar days. Public videos or playlists are not deleted merely because an authorisation is revoked. Copies controlled by Google and other providers remain subject to their policies.
6. Revoke Google access
You may revoke Vessa Social Automation’s Google access through Google Account third-party connections. Revocation stops the application from obtaining new authorised data with that connection. Notify the project to arrange deletion of locally stored authorisation and associated API data as well. Reconnecting later requires a new, explicit authorisation.
7. Your choices and changes
You can browse without using saved recipes, avoid loading video embeds, clear local browser storage, and contact the project about information you supplied. Privacy rights depend on your location and the applicable law. This policy will be updated if the website or application begins collecting different information or adds new services.