Tablewealth
Cookies

Cookie Policy

This policy explains the cookies and similar browser storage Tablewealth uses, which ones are optional, and how to control them.

Effective:July 22, 2026Last Updated:July 22, 2026

1. Scope

This Cookie Policy applies to tablewealth.com, app.tablewealth.com, and the web experiences that link to it. Cookies are small browser records. Similar technologies include local storage, session storage, and short-lived device or request identifiers.

We separate technologies that are necessary to provide and protect Tablewealth from optional product analytics. Rejecting optional analytics does not prevent you from creating an account, signing in, or using the product.

2. Necessary Cookies & Storage

Necessary technologies support authentication, session security, fraud and abuse prevention, requested integrations, service continuity, and preferences that you ask us to remember.

  • Authentication and security - Keep you signed in, protect account flows, validate requests, and support security features.
  • Fraud and abuse prevention - Support controls such as Cloudflare Turnstile during sign-up when enabled.
  • Preferences - Remember theme, interface state, mobile handoffs, and other settings you choose.
  • Consent preference - Store accepted or rejected optional analytics for up to 180 days in a first-party cookie shared across Tablewealth subdomains and in local storage as a fallback.
  • Operational diagnostics - Record minimized error information needed to secure, troubleshoot, and maintain the Services. Before optional analytics consent, browser diagnostics are configured without persistent PostHog storage or session replay.

Because these technologies are needed to provide a requested service or remember a privacy choice, they cannot all be disabled through the optional analytics control. You can block them in your browser, but parts of Tablewealth may stop working.

3. Optional Product Analytics

When you accept optional analytics, we use PostHog to understand how people find and use Tablewealth. It may store a first-party identifier in cookies and local storage and collect page paths, referrals, campaign parameters, device and browser details, approximate location derived from IP address, and interaction events.

On the sign-up page, accepted analytics may include session replay. Inputs are masked, sensitive selectors are blocked, request headers and bodies are not recorded, and sensitive dashboard surfaces mask page text and element attributes.

We use this information for aggregate product measurement and improvement, not targeted advertising. We do not use advertising or retargeting tags and do not sell personal or financial data.

4. Cookieless Web Analytics

The public website uses Vercel Web Analytics for anonymous, aggregated traffic measurement. Vercel Web Analytics does not use cookies. It distinguishes visits using a hash derived from a request that resets daily and is not designed to identify a person across days or websites.

We do not send names, email addresses, financial data, or account identifiers in Vercel Web Analytics events.

5. Your Choices

  • Accept or reject - Net-new visitors are asked before optional analytics starts on the public website and on sign-in or sign-up pages.
  • Change your mind - Use the Cookie settings control on those pages. The new choice applies going forward and rejection asks PostHog to clear its analytics persistence.
  • Cross-subdomain preference - Your first-party preference is shared between tablewealth.com and app.tablewealth.com so a prior rejection is honored after sign-up.
  • Global Privacy Control - If your browser sends a recognized GPC signal and you have not made a Tablewealth-specific choice, optional analytics remains off.
  • Browser controls - You may also delete or block cookies and site storage through browser settings. This may remove your saved choice, so we may ask again.
Terms and product use: Creating an account and accepting the Terms does not reverse a prior cookie choice or browser privacy signal.

6. Policy Updates

We review this policy at least annually and update it when our browser technologies or legal obligations materially change. When legally required, we will provide additional notice or ask for a new choice.