Privacy
Your relationships are not advertising inventory.
Jamii needs context to be useful. This page explains what information the service handles, why it handles it and the choices you retain.
What Jamii stores
Account details, organisation membership, the business or personal-brand information you provide, imported contacts, monitoring topics, generated profiles, briefs, drafts and the activity needed to operate your workspace.
Limited-beta waitlist
If you request beta access, Jamii sends your name, email address and the business description you provide to the team so they can assess your request and contact you about availability. These details are not added to a public directory or used to send unrelated marketing.
How imported contact data is used
Contact data is used to organise your audience, build useful relationship context, create requested drafts and record relevant campaign activity. It remains scoped to your Jamii workspace and is not made public by Jamii.
Generated profiles and AI services
Jamii sends the information needed for a requested generation task to its configured AI providers. This may include business context or selected contact details. Jamii should only be given information you are entitled to use for that purpose.
Market and community monitoring
Jamii uses search services and publicly available sources to find relevant news and public conversations. It stores selected results and generated analysis inside your workspace. A suggested reply is a draft; you decide whether and where to post it.
Email delivery and measurement
When you deliberately send a campaign, an email delivery provider processes recipient addresses and message content. Delivery events such as sends, opens, clicks, bounces and unsubscribe activity may be recorded so the campaign can be operated and understood.
Connected social accounts
If an owner or admin connects a Facebook Page, Instagram account or LinkedIn page, Jamii stores that account's name, picture and identifier, and an access token encrypted at rest. The token is used only to publish posts your workspace has approved and to check the connection still works. Jamii does not read your messages, followers or other content. Disconnecting removes the token. You can also remove Jamii from your Facebook account settings, or ask Facebook to have Jamii delete this data; either request is honoured automatically, and a deletion gives you a confirmation code you can check at thisisjamii.com/data-deletion.
Access and separation
Workspace data is separated by organisation. Users must authenticate before accessing protected product routes, and server-side checks are used when reading or changing organisation data.
Your choices
You can edit or remove information in the product and choose whether to send a draft. For an access, correction, export or deletion request, email [email protected] from the address connected to your account.
Before launch
This plain-English explanation describes the current product behaviour. It is not a substitute for the final legal policy, retention schedule and processor list, which will be published before Jamii takes paid public customers.
Last updated 15 October 2026.