Skip to content

Privacy policy

What information Tamaam receives, how it is used, and how to reach us about it.

Updated Pre-launch review

The short version

Early-access details and Help requests are stored so the team can follow up. Workspace content can be shared with authorised members. Analytics and enabled AI services have their own processing roles.

This is a pre-launch review version. Company formation and several operational privacy details are still being finalised.

About this notice

This notice covers Tamaam’s website, early-access list, Help Center, support and available workspace services. It explains the current pre-launch service, including services that already store information and product previews that use sample or session data.

Tamaam LLC is the intended Delaware company name. Formation is not yet complete. The legal operator’s details and contact address must be confirmed before this pre-launch notice is finalised. For now, you can reach the Tamaam team at hi@tamaam.io.

When a business uses Tamaam to manage information about its clients or team, that business also determines how it uses that information. Ask your workspace owner about the business’s own privacy practices.

Information you provide

Early access

The early-access form collects your name, email and type of business. A submission can also include the plan you selected, where you clicked from, the referring website’s hostname and campaign tags. We use this to manage your request and communicate about access.

Accounts and workspace content

Account information supports sign-in and account access. Available workspace services may process business details, client and team records, conversations, tasks, documents and other content that you or authorised members provide. Some preview screens use fictional records or hold changes only in the current session.

Help and support

Article feedback includes the article, a helpfulness vote and any reason or comment you add. Unanswered searches can be saved after addresses, URLs and long identifiers are removed by our search sanitisation checks. Avoid putting sensitive information in a search or comment.

A support request includes your name, email, subject and message. It may also include the article, guide version, search phrase or feedback reason that brought you to the form. The team can add internal notes, status, priority and a history of review actions.

Usage and technical data

We use analytics to understand pages visited, interactions and early-access actions. Signed-in activity can be associated with a user identifier. Error monitoring and technical logs help diagnose faults. Hosting and other providers may process network information, including IP addresses.

To limit repeated Help submissions, the intake service stores a rotating hashed network fingerprint. This is specific to those rate-limit records; it does not mean other infrastructure never receives an IP address.

How information is used

Information is used to:

  • Provide sign-in and the workspace services that are enabled.
  • Manage early-access interest and respond to support requests.
  • Improve Help articles and find gaps in the information readers need.
  • Diagnose faults, protect account access and reduce misuse.
  • Understand website activity and interest in Tamaam.

You can choose whether to join early access or submit feedback. Without an email address, the team cannot reply to your support request. Account information is needed for authenticated services.

The applicable legal bases, regulator details and international transfer arrangements will be completed alongside the confirmed operator details before this notice is finalised.

Access and service providers

Workspace information can be shared with members according to the relevant access permissions. Early-access submissions, Help feedback and support requests are privately reviewed by authorised platform administrators.

The implementation uses the following providers for the corresponding functions:

Supabase
Authentication and database storage, including early-access and Help records.
Vercel
Website hosting and deployment infrastructure.
Resend
Support notification emails.
PostHog
Website analytics and session recording according to project settings.
Sentry
Configured production error monitoring and tracing.
Anthropic
AI processing when a live Nefer feature invokes the server-side AI service.

These services may process information in countries other than yours. Provider regions, contractual safeguards and retention need confirmation before the final notice; Tamaam does not currently make a data-residency promise.

AI and connected services

When you use a live AI feature, your prompt, relevant conversation history and workspace context used to answer the request may be processed by the AI provider. AI output can be incomplete or incorrect. Check it before relying on it or sending it to someone.

Where a working external integration is enabled, information can move between Tamaam and that service under the permissions granted. A connection shown in an animated demonstration does not establish that the integration is live. External services have their own privacy practices.

This notice does not promise that AI providers never retain data or use it for training. Those claims require confirmation of the agreement and configuration applying to the enabled service.

Cookies and analytics

Authentication uses session storage or cookies to support access. PostHog collects page and interaction analytics and can record sessions if enabled in the project. Inputs are masked in the implementation. Additional private regions require explicit masking; the Help admin queues are masked and excluded from automatic interaction capture.

The current website does not provide an analytics cookie-preferences panel. Browser cookie controls may affect sign-in and do not necessarily stop all telemetry. The consent and analytics-control approach is under review before the final notice is published.

How long records are kept

There is currently no automatic deletion schedule for early-access or Help submissions. Records remain stored while the team manages access interest, reviews feedback or handles support. Resolving or archiving a support ticket changes its status; it does not delete the request.

You can request deletion by emailing hi@tamaam.io. Retention criteria and the treatment of backups, email copies, provider logs and analytics records need to be completed before the final notice. This page does not promise deletion after a fixed number of days.

Your requests and choices

Email hi@tamaam.io to ask about information associated with you, request a correction, access, export or deletion, or ask to leave the early-access list. Identify the account or submission involved, but do not send a password. We may need to verify your identity or authority before disclosing or changing information.

Depending on the law that applies, you may also have rights to restrict processing, object to certain uses, withdraw consent where it is the basis for processing, or complain to a data-protection authority. Available rights and exceptions depend on the circumstances.

Objecting to processing. You can raise an objection to the team at the same email address. Explain the use you object to so it can be assessed.

Access, export and deletion are currently contact requests, not a promise that every action is available through a self-service Settings control.

Updates and contact

Revisions will be shown on this page with an updated date. Company formation, changes to live services and the completion of the operational privacy decisions will require further updates.

For privacy questions, contact hi@tamaam.io. For a product issue, use Contact support so you receive a saved request reference.

Something you want to clarify?

Talk to the Tamaam team at hi@tamaam.io.

Read the terms of service