Privacy & your workspace

Who is responsible

Nyembotech is the brand used by this website. The full legal name and address of the responsible operator, its privacy contact and any required representative or data protection officer are still awaiting owner confirmation. The company information page identifies those missing details.

Information the product uses

A project brief contains your name, email, company, market, selected service and project description. An account uses sign-in and identity information. A connected workspace holds proposals, customer decisions, project milestones, files you exchange, feedback, onboarding progress and support requests. Billing fields record operational status; this workspace does not collect payment card details.

Provide only information needed for your project. Do not put passwords, access tokens or unrelated sensitive personal information in a project brief or support message.

Why this information is used

The product uses these records to review inquiries, link the correct customer, prepare proposals, manage delivery, exchange files, record decisions and resolve support requests. Account verification and access controls help restrict customer records to the relevant workspace.

The final notice must identify the legal basis for each purpose, any legitimate interests, required versus optional fields, and how consent can be withdrawn where consent is used. These choices have not been finalized.

Service providers and international access

This website is hosted on OpenAI Sites using Cloudflare infrastructure. Portal sign-in uses ChatGPT identity. Project records are stored in Cloudflare D1 and uploaded files in private Cloudflare R2 storage. Local test data is separate from the live website. Automatic inquiry emails are currently disabled; any email, booking or billing integration will be identified here when enabled.

Serving Germany and Tanzania does not establish where data is stored. Hosting regions, processor terms, access from other countries and any transfer safeguards must be verified before launch. This page makes no data-residency assurance.

Retention and deletion

Retention periods for inquiries, accounts, proposals, projects, files, support records, security logs and backups have not yet been approved. The owner must define these periods, applicable legal recordkeeping requirements and a workable deletion or anonymization process. No automatic deletion schedule is claimed here.

Sign-in, preferences and app installation

Your browser stores authentication state needed for sign-in, your preferred language and your selected Light or Black theme. Installing the web app adds a shortcut to the same service; the installed app still requires a connection and the correct account to access customer or business records.

The service worker caches a generic offline page and a public logo. It does not cache workspace API responses, customer files or authenticated pages for offline use. Clearing browser data can remove preferences and sign-in state.

Operational records and diagnostics

Workspace actions create an operational history, including timestamps and the responsible account. Request and security metadata support access checks and abuse prevention. The live hosting and diagnostic configuration, and any additional analytics, must be reviewed and described before release.

The owner also sees aggregate counts of briefs, shared and accepted proposals, and completed projects. Optional website offer-view and discussion-click counts are disabled by default outside local testing. These counters store the date, language, offer category and event count, without customer content or a visitor identifier. The dashboard covers 30 days; aggregate rows older than 90 calendar days are removed when the next event is recorded. These figures count events rather than unique visitors.

Your data rights

Depending on the applicable law and circumstances, you may request access, correction, deletion, restrictions or portability, and raise objections to processing. You may also have rights concerning consent, automated decisions and complaints to a supervisory authority. The European Commission and Tanzania’s Personal Data Protection Commission provide the official guidance linked below.

A verified privacy contact and request-handling procedure must be added to the final notice. A general contact form is available while these owner details are being completed.

Official background sources