01
Your account is the boundary.
Cards, images, notes, and relationship context are treated as private user data tied to your account.
Security
Your network.
Yours alone.
Kumbuka protects the cards, context, and relationship memory you save, without turning your private network into advertising or training data.
Trust baseline
Private by product design.
- Contact sales
- Never
- Model training
- Never on private data
- Transport
- Encrypted
- User control
- Export and delete
02
We collect what the product needs.
Kumbuka uses contact, account, scan, device, and optional calendar data to provide the service.
03
You can leave with your data.
Export contacts, remove cards, delete images, or request account deletion through support.
Protected data
The sensitive parts of your network.
Scanned cards
Card photos, extracted text, logos, and structured fields from business cards.
Relationship context
Notes, tags, locations, follow-up history, and memory cues you add.
Account access
Sign-in identifiers, authentication events, device details, and support records.
Reliability logs
Diagnostics, crash signals, abuse prevention records, and operational logs.
Data flow
From scan to control.
- 01 / Capture
You scan or enter a card.
Kumbuka structures the information you provide so it can be searched, edited, exported, and remembered later.
- 02 / Sync
Data moves through encrypted connections.
Your library syncs across supported devices and service surfaces through secured network communication.
- 03 / Store
Private data stays within service infrastructure.
Card records, images, notes, and account data are protected with storage and access controls.
- 04 / Control
You can export or delete.
Kumbuka is designed so your network is not trapped inside the product.
Controls
Safeguards around everyday use.
Encrypted transport
Network communication uses encrypted connections between the app, website, and service infrastructure.
Protected storage
Cloud data and card files are stored in private infrastructure with access controls and operational limits.
Data portability
You can export contacts through product flows and request help when you need account-level assistance.
Deletion paths
You can delete cards and request account deletion, subject to legal, fraud, accounting, or dispute obligations.
01 / Private data
What we protect
Kumbuka is built around relationship memory, so the data you save can be personal and commercially sensitive. We treat scanned cards, card images, contact fields, notes, meeting context, relationship data, and support messages as private user data.
We do not sell contact data, share private cards for advertising, or train models on your private cards, notes, or relationship context.
02 / Access
Who can access it
Your account is the primary boundary for your Kumbuka library. Internal access is limited to authorized service needs such as support, security, abuse prevention, debugging, legal compliance, and operations.
You are responsible for keeping your device, sign-in provider, and account credentials secure. If you believe your account is compromised, contact us at support@jambo.team.
03 / Retention
Export, deletion, and retention
Kumbuka is designed to let you take your network with you. You can export contacts, delete individual records, and request account deletion.
Some records may be retained when required for legal compliance, accounting, fraud prevention, security investigations, support history, or dispute resolution. The full policy is described in our Privacy Policy.
04 / Limits
Security limits
No online service can guarantee absolute security. We use technical and organizational safeguards to reduce risk, but protection also depends on your device security, account settings, operating system, sign-in provider, and how you share exported contact data.
If you find a vulnerability or security issue, send enough detail for us to investigate to support@jambo.team.
Related
Policies and support
- Privacy
- Read policy
- Terms
- Read terms
- Support
- support@jambo.team
- Operator
- Jambo.team