Privacy at tamaga.systems

Tamaga tries to collect less data, not more.

This notice explains the current data boundary for the interim tamaga.systems website and how to contact us about privacy.

Tamaga is currently operated through BlueMelon.

Privacy questions can be sent to talk@tamaga.systems.

The interim site is intentionally simple.

At this stage, the public website is designed to work without a visitor account, marketing profile, or behavioral advertising.

The site code does not intentionally load third-party behavioral analytics or advertising trackers. Contact and Snapshot requests route to email at talk@tamaga.systems.

The footer newsletter is optional. When you submit it, the email address is sent to a Tamaga-operated newsletter endpoint and forwarded to Plunk to start a confirmation email. The contact remains unsubscribed until you confirm through that email. A newsletter confirmation is not the same as an immediate subscription.

The website does not place a Plunk credential in the browser. Email open or click tracking is not described here as disabled; that setting depends on the configured newsletter project and must remain aligned with the actual service configuration.

If you contact us, we receive the information you choose to send.

An email may include your name, email address, role or organization, property or platform website, the content of your message, and attachments you choose to send.

We use that information to understand and respond to the inquiry, discuss possible work, answer research or media questions, and manage any working relationship that follows.

Do not send payment-card data, account passwords, API keys, identity documents, or unrelated sensitive guest information through ordinary email.

Technical request data

The infrastructure that serves the site may process basic technical request information to deliver pages, protect the service, diagnose errors, and prevent abuse. The exact production provider and its applicable wording are not yet selected, so this notice does not make a claim about specific infrastructure logs.

No behavioral analytics or advertising cookies.

The site should not load third-party behavioral analytics, advertising pixels, or marketing cookies. If privacy-first analytics are added later, the implementation and this notice must be reviewed together.

The fictional demo has a stricter data boundary.

Tamaga Hotel is a product demonstration, not a real accommodation service. The public demo is designed around synthetic scenarios and should not require or create real guest identity, payment information, billing profiles, identity documents, or hotel reservation data.

Do not enter real personal or payment data into the demonstration. The fictional property, room, policy, and representation data are demonstration content and not records about real travelers or real hotel operations.

We do not sell personal data to advertisers.

Information may be processed by service providers necessary to operate the website, email, hosting, security, or future project work. The actual provider list depends on the production deployment and must be documented before additional data-collection services are enabled.

Keep information only while it has a legitimate purpose.

Email inquiries may be retained while they are needed to respond, maintain relevant correspondence, manage a working relationship, keep appropriate business records, or meet legal obligations that apply. Different records may require different retention periods.

You can ask what information we hold about your inquiry.

Depending on the law that applies to you and to the processing, you may have rights to request access, correction, deletion, restriction, objection, or another applicable privacy right. To make a privacy request, write to talk@tamaga.systems.

Include enough information for us to understand the request, but do not send unnecessary identity documents in the first email. We may need to verify identity before acting on a request that affects personal data.

Privacy also depends on what we choose not to collect.

Tamaga aims to keep the public site static-first, limit third-party scripts, avoid client-side secrets, and separate product demonstrations from real guest data. No public website or email system can promise absolute security.

The notice should change when the data flow changes.

A privacy notice should describe the real system, not a hypothetical one. When Tamaga adds or changes a form provider, analytics, newsletter service, hosting architecture, or another material data flow, the page should be reviewed and updated.

Privacy questions

Email talk@tamaga.systems.