Legal
Privacy policy
Last updated 23 October 2026
This policy explains what KaribaCore collects when you use karibacore.com, why, and how long it is kept. KaribaCore, operated from Ireland, runs the service and decides how this information is used. You can reach us at [email protected].
What we collect
- Access requests. If you request access, the name, email address, GitHub username, workspace name and answers you enter, so we can review the request and reply. Your IP address is kept only as a keyed digest, to limit repeated requests.
- Your GitHub identity. When you sign in, GitHub gives us your user ID, username, display name and avatar address. We do not receive or store your GitHub password.
- Workspace records. Workspace names, members and their roles, and invitations, which include the GitHub username invited.
- Repository and deployment records. The repositories you import, branch names, commit identifiers, deployment history, and build and runtime output.
- Your code. We read the repositories you choose in order to build them, and we keep the built application images needed to run and roll back your releases.
- Configuration. Environment variables, stored encrypted, and the domains you add.
- Notification email address and preferences. If you add one, the address you verify for deployment and workspace updates, its verification status and your choices.
- Activity records. A record of actions taken in a workspace, such as deployments and access changes.
- Technical information. Your IP address is processed to limit request rates and protect the service.
We do not use analytics or advertising trackers, and the pilot does not collect payment details.
Why we use it
- To sign you in and keep your workspace separate from others
- To build, run and route your applications
- To show you what happened when something fails
- To keep the service secure and to answer support requests
Who else handles it
- GitHub provides sign-in and repository access.
- Microsoft (Microsoft Graph) sends transactional emails when you request access, receive an invitation email, verify an address or enable notifications. In-app notifications and email delivery records are retained for 30 days. Message payloads are encrypted while queued and removed after a final delivery result.
- Cloudflare carries traffic to the service and to hosted applications, and issues certificates for custom domains.
We do not sell your information.
How long we keep it
- Build output: 30 days
- Runtime output: 7 days
- Sign-in sessions: up to 8 hours, or until you sign out
- Access requests: until we decide on them, then 90 days
- Other records: while your account or workspace exists
- Encrypted database backups: 30 days, so deleted information leaves them within 30 days
If a workspace is suspended, its data is retained until it is reactivated or deleted.
Deleting a workspace
A workspace owner can delete it from Members, after typing its exact name. Its projects are deleted straight away and cannot be restored: their applications stop and their custom domains are released. For 7 days any owner can cancel, which keeps the workspace and its members, but not its projects.
After 7 days we permanently destroy its environment variables and the encrypted copy kept with each deployment, its build and runtime output, its notifications, pending invitations and the email addresses they were sent to, its member list and its GitHub connection, and we remove its application images and build caches. The workspace and project names are replaced. What remains is a minimal record: deployment history (commit identifiers, build results and the repository name each build used) and the activity history (which actions were taken, when, and by which account, including the domain names some of those actions name), so that the deletion itself can be accounted for.
Deleting your account
You can delete your account from My account. If you are the only owner of a workspace, delete that workspace or make another member an owner first. Deleting your account signs you out everywhere and removes your workspace memberships, notification settings and email address, your inbox, and the GitHub username, name and picture we stored. We keep your GitHub user ID with the deleted account, so past actions in workspace activity still point to one account (shown without your name) and the account cannot be recreated by signing in again.
Your choices
Owners and maintainers can download a copy of a workspace (settings, members and roles, projects, environment variable names, domains, deployment history and activity) from Members. Variable values are never included. You can also ask us for a copy of your information, for a correction, or for deletion, by emailing us. If you are in the European Economic Area or the United Kingdom, the General Data Protection Regulation gives you these rights and others, including the right to object to some processing and to complain to a supervisory authority. Our supervisory authority is the Data Protection Commission in Ireland.
Where it is processed
The service runs on infrastructure operated from Ireland. GitHub and Cloudflare process information in their own locations under their own terms.
Applications you host
If your application collects information from its own visitors, you are responsible for that information and for telling those visitors how you use it.
Changes
When this policy changes, we will update the date at the top of this page.
Contact
Questions about this page: [email protected].