Privacy policy

1. What this website does

Basaiye Ayurveda is an informational website and illustrative product catalogue. The current implementation does not provide accounts, checkout, payment processing, newsletter signup, contact forms, comments, user profiles, or user-submitted content.

2. Information collected by the website

The site itself does not ask visitors to enter personal information and does not intentionally store personal information in a database. The JavaScript currently supports a mobile menu, in-page herb search, category filters, and a display of the current year. It does not use localStorage, sessionStorage, cookies, analytics tags, advertising pixels, or similar tracking code.

Normal web requests can still disclose technical information to the selected hosting provider or network operators, such as an IP address, requested URL, timestamp, browser or device information, referrer, and error or security information. The website owner does not control the provider’s processing of those request records.

3. Browser storage and cookies

The current site does not intentionally set first-party cookies and does not use browser storage. A hosting provider, security layer, content delivery network, or third-party service may use its own cookies or similar technologies outside this source code. Those technologies depend on the final deployment configuration and should be documented here before launch if enabled.

4. Hosting and request logs

This project is designed for a static deployment to Cloudflare Pages or Netlify, but no final provider has been selected in this project. The selected provider may receive and retain ordinary access, security, abuse-prevention, and performance logs. Retention, regions, subprocessors, and available visitor-rights processes are determined by that provider’s current terms and privacy documentation. The owner should add the final provider name and links before launch.

5. Third-party services and external links

The stylesheet currently imports fonts from Google Fonts. A visitor’s browser may request font stylesheets and font files from Google’s domains in order to render the selected typography; Google’s own policies apply to that activity. The Google Fonts developer documentation explains that a page requests a stylesheet and then the browser downloads the appropriate font file. See Google’s technical considerations for Fonts and the Google Privacy Policy.

The herb library contains links to NCCIH and NIH resources. Those sites are separate services. Clicking an external link takes the visitor to the linked service, which may collect information under its own policies. Basaiye Ayurveda does not receive a visitor’s activity on those external sites through this static implementation.

6. How information is used

The source code uses no personal information for profiling, advertising, marketing, sales outreach, or automated decisions. The selected host may process technical request data to deliver files, maintain security, prevent abuse, diagnose errors, and operate its infrastructure.

7. Retention

The site has no application database or visitor account records to retain. Any hosting, security, font-service, or external-link records are retained by the relevant provider under its own policies and configuration. The owner should confirm those periods and document them before launch.

8. Security

The project contains no user account or payment data. The owner should deploy it over HTTPS, keep the hosting account and domain controls protected, review third-party dependencies, and configure provider security features as appropriate. No internet service can promise absolute security.

9. Policy changes

This policy may change when the website gains a new host, analytics, forms, embeds, commerce, or other functionality. The owner should update the “Last updated” date and publish the revised policy before or when the relevant change goes live.

10. Privacy enquiries

A privacy contact person, legal owner, and contact method have not yet been supplied, so no address or email is invented here. The owner must add a working privacy-enquiry route and any legally required information before public launch. Until then, this draft is not a complete operational privacy notice.

Prelaunch checklist

• Select and document the final hosting provider and relevant log-retention details.
• Decide whether Google Fonts will remain externally loaded or be self-hosted.
• Supply the legal owner/entity name, jurisdiction where required, privacy contact, and any required rights language.
• Have this draft reviewed for the jurisdictions and audiences in scope.