Legal
Privacy Policy
Tembeza reads the product you point it at — a code repository, a website, files or a description — and helps you take it to market. To do that we handle some personal information and a lot of your own material. This page explains what, why, who else sees it, and what you can do about it.
1. Who we are
The service is operated by [legal entity name and registered address] (“Tembeza”, “we”). Questions about this policy or your data: hello@tembeza.online.
2. What we collect
Your account.
- Your email address, and — if you sign in with GitHub or Google — your name, profile picture and that provider’s account identifier.
- Sign-in records: a one-time code (stored only in scrambled form and deleted within 24 hours), and a session record (the session token is stored only in scrambled form).
What you give us to work on.
- The sources you add: repository links, repositories you choose to share through GitHub, website links, uploaded files, and written descriptions.
- What we produce from them for you: briefs, positioning, an AI “agent” persona (including generated images), chat messages and draft posts.
From GitHub, when you connect it. Read-only access to the repositories you choose (contents, metadata and pull requests). We can’t change your code. You can remove access at any time in your GitHub settings.
Technical data. Your IP address and browser details in our hosting providers’ logs, and a scrambled form of your IP address used only to limit abuse of the sign-in form. [Confirm what the hosts log and for how long.]
We do not use advertising or analytics trackers on tembeza.online or in the app. [Re-check at launch.]
3. How we use it
- To run the service: read your sources, draft your brief and content, and show them to you.
- To sign you in and keep your account secure, and to prevent abuse and control cost.
- To send the emails the service needs (sign-in codes and important notices). We don’t send marketing email without asking you first.
- To improve reliability, using operational data such as errors and timings. [Confirm scope.]
We don’t sell your personal information, and we don’t use your material to advertise to you.
4. Who else processes it
We use other companies to run Tembeza. Where they handle your information, they do so to provide their service to us.
| Provider | What for | What they receive |
|---|---|---|
| Render | Hosts our API and database (United States, Oregon) | All account and project data we store |
| Cloudflare | DNS, website and app hosting, image storage, bot protection on the sign-in form | Web traffic; stored images; sign-in form checks |
| Resend | Sends sign-in emails | Your email address and the message |
| GitHub, Google | Sign-in, and (GitHub) repository access | What you authorise at sign-in |
AI model providers
To read your sources and write for you, we send excerpts of your sources and your inputs to AI model providers through their business APIs. Today these are:
| Provider | Used for |
|---|---|
| Moonshot AI (Kimi) | Reading your sources and drafting the brief |
| DeepSeek | Grounding and structuring steps of the brief |
| Anthropic (Claude) | Fallback reading, inference and agent writing |
| Google (Gemini) | Quality checks, agent writing and image generation |
| OpenAI | Fallback for quality checks |
[Founder decision before launch: two of these providers are based in China, and the first two handle the most repository content. Either keep them and say so plainly here, or route customer content only to providers you are comfortable naming to a customer who asks “where does my private code go?”. Also confirm each provider’s API terms on retention and training, and quote them here.] We do not use your material to train our own models.
5. Where your information goes
Our servers are in the United States. Our providers may process information in other countries, including those where AI model providers operate. Where the law requires it, we rely on standard contractual clauses or another lawful transfer mechanism. [Lawyer to confirm the mechanism.]
6. Cookies and local storage
- Session cookie — set when you sign in; strictly necessary to keep you signed in; lasts up to 90 days of use.
- Your browser’s storage — remembers your light/dark choice and holds the sources you have added while you sign in, so you don’t lose them.
No advertising or analytics cookies.
7. How long we keep it
- Account and project data: until you delete your account or ask us to delete it.
- Sign-in codes: deleted within 24 hours. Sessions: expire after 90 days without use.
- Backups and provider logs may keep copies for a short further period. [State the periods.]
8. Your rights
You can ask us to give you a copy of your information, correct it, delete it, or stop using it for a particular purpose, and you can withdraw consent you gave. Email hello@tembeza.online from the address on your account. There is no self-service delete button yet, so we handle these requests by hand, and we aim to reply within [30] days. You may also complain to your data protection authority [including Uganda’s Personal Data Protection Office, and your local authority if you are in the EU/UK].
[Lawyer: confirm the legal bases we rely on (contract, legitimate interests, consent) and the laws that apply — Uganda’s Data Protection and Privacy Act, and GDPR/UK GDPR/CCPA for users there.]
9. Security
We use HTTPS everywhere, store sign-in tokens and codes only in scrambled form, ask GitHub for read-only access, and separate each account’s data. No system is perfectly secure; if a breach affects you we will tell you as the law requires. [Confirm each statement is true at launch.]
10. Children
Tembeza is not for anyone under [18]. We don’t knowingly collect information from children.
11. Changes
If we change this policy in a way that matters, we’ll tell you before it takes effect.