This policy describes the reviewed Next.js application served from Vercel at the public business domains, plus protected generated and Preview deployment URLs. Historical Wix observations do not describe the current production deployment.
Current essential technologies
Supabase administrator session cookies
The Next.js application uses Supabase server-side authentication for private administrator access. Supabase session information is read and refreshed through cookies so an authorized administrator can remain signed in and protected routes can validate the session. These cookies are not intended for advertising.
Vercel Authentication cookie
Generated and Preview deployment URLs are protected by Vercel Authentication. After an authorized Vercel viewer signs in, Vercel sets an access cookie scoped to the protected deployment URL. This operational access control is not a public marketing cookie and is distinct from the public business domains.
Application state
Contact and inquiry form progress is maintained in client application state. The reviewed source does not create a visitor-profile or marketing cookie for those forms.
Security and authentication
The application uses server-side rate limiting and short-lived Redis keys for configured administrator login security. Redis keys are server-side records, not browser cookies. Hosting providers may also use essential network, load-balancing, abuse-prevention, and diagnostic technologies under their own configurations.
Third-party integrations
Following a link to Apple, Google, a client website, or another external destination allows that service to apply its own cookies and policies. A normal link does not by itself authorize this business to describe or control the destination's cookie behavior.
The retired Wix application model named forms, chat, bookings, stores, payments, members, a cookie-policy banner, and optional advertising or social-event modules. A named historical module does not prove collection or describe the current website. Inventory retained Wix records separately and scan the current Vercel application for active code, embeds, cookies, categories, durations, and pre-consent behavior.
Consent-control assessment
The reviewed Next.js code does not justify installing a generic consent banner merely for appearance. Essential authentication and security technologies may be treated differently from analytics or advertising technologies depending on purpose, duration, deployment, and visitor jurisdiction.
No analytics, advertising, session replay, embeds, preference tracking, or other non-essential technology is activated. If one is introduced, it must be reviewed before activation and blocked until any required consent is obtained, with appropriate accept and reject controls where applicable.
Unnecessary tracking will not be installed merely to populate a cookie banner.
Browser controls
Browsers can display, block, or delete cookies. Blocking essential authentication cookies can prevent administrator or protected-deployment access. Browser controls do not necessarily satisfy every legal consent requirement.
Changes and contact
Contact: info@metiennewebdesigns.com.
This policy is effective October 29, 2026. The inventory will be reviewed whenever hosting, authentication, analytics, advertising, embeds, payment, scheduling, chat, personalization, or consent tooling changes.
Technology inventory controls
For every deployed cookie or similar technology, the business should record:
- exact name or pattern;
- provider and domain;
- first- or third-party status;
- purpose and legal classification;
- data stored or accessed;
- session or persistent duration;
- production environments and visitor groups;
- whether it is set before consent;
- consent or exemption analysis; and
- deletion and preference-control behavior.