berkkarabacak.com

Privacy Policy

Last updated: 23 June 2026

This policy explains what the self‑hosted tools on berkkarabacak.com — including the Post‑Migration Health Checker, Cloud Site Reset, and Migration Scrubber — collect, why, and how the data is protected. These are personal, self‑hosted utilities operated by Berk Karabacak. They are not a commercial product and your data is never sold or used for advertising.

What we collect

Account identity (via SSO). When you sign in with Google or Atlassian we receive and store your email address, display name, and a stable account identifier from that provider. We do not store passwords — sign‑in is single‑sign‑on only.
Jira connection credentials. Any Jira API token you save is stored encrypted at rest and is used only to call the Atlassian/Jira APIs on your behalf to perform the action you requested.
Atlassian authorization data. If you authorize the app via Atlassian OAuth, we read the list of Atlassian sites your account can access (to populate the site picker) and your account id/email (to sign you in). We request only the scopes needed for the feature you use.
Operational data. Reports from the runs you trigger (e.g. which projects/issues were tested and the results) are saved on the server so you can review and download them.

How we use it

Solely to provide the tools' functionality — verifying a Jira Cloud migration, auditing permissions, and cleaning up migrated content. We do not sell, rent, or share your data with third parties, and we do not use it for advertising or profiling.

Where it lives & how it's protected

Data is held on a single private server operated by the owner. Jira API tokens are encrypted at rest, access requires your authenticated account, and connections between your browser and the server use HTTPS.

Atlassian data

We access your Atlassian/Jira data through official Atlassian APIs, only under the scopes you explicitly grant, and only while performing a task you initiated. We do not retain Jira content beyond the run reports you generate, and Atlassian account identifiers we store are handled in line with Atlassian's developer requirements.

Retention & your choices

Saved Jira connections and run history are kept until you remove them — you can clear history and delete connections from your account at any time.
You can request deletion of your account and all associated data by contacting us (below).

Changes

If this policy changes, the "Last updated" date above will change accordingly.

Contact

Questions or deletion requests: berkkarabacak@gmail.com.