Privacy Policy

Last updated October 3, 2026

This policy explains what personal data GitPersona collects, why, who else handles it, and the choices you have. It covers the desktop app, the gitpersona CLI, this website, and the GitPersona server. GitPersona is run by Arpakhsad Joshtri Sugiatma Lenggu (known as Joshtri Lenggu), an individual based in Indonesia ("we"), who is responsible for this data.

In short

Your Git identities, SSH keys, tokens, and repository data stay on your device. We never receive them.
The app and the CLI have no analytics, telemetry, or crash reporting.
You only need an account for the Pro trial or to buy Pro. We then keep your email address, your plan, and a short record of each device you sign in on.
We don't sell your data, show ads, or send marketing email.

Data that stays on your device

Your profiles (name, email, and signing key reference), tracked repositories and their assignments, rules, SSH key and credential details, settings, and the activity log are saved in GitPersona's data folder on your computer. HTTPS tokens and your sign-in session are kept in your operating system's credential store (Windows Credential Manager, the macOS Keychain, or Secret Service on Linux). None of this is sent to us.

Requests to GitHub and GitLab

A few features talk directly to GitHub or GitLab, not to us. They handle these requests under their own privacy policies.

Token checks— when you add or change an HTTPS token for github.com or gitlab.com, and when the app starts if a token's expiry date isn't known yet, the app sends that token straight to the service that issued it, to confirm it works and find out when it expires.
Downloads and updates — installers and app updates are downloaded from GitHub, where our releases are published.
CLI update check— about once a day, the CLI asks GitHub's public API for the latest version number.

Data our server receives

Update and announcement checks — when the desktop app checks for updates, announcements, and feature settings, it sends the app version and release channel, and the update check also sends your operating system and processor type. These requests carry no account or device identifier.
Download clicks on this website — the platform, version, and button you clicked; the country our host works out from your IP address; and a salted hash of your IP address and browser identifier that changes every day and is used only to avoid counting the same download twice. Your IP address itself is not stored.
If you sign in— your email address; one-time sign-in codes, stored as hashes and deleted within an hour, together with a hash of your IP address to limit repeated attempts; your session, stored as a hash; your plan, paid-through date, and trial dates; and when you created your account and last signed in. For each device you sign in on, we also keep a one-way hash of the computer's machine ID (the ID itself never leaves your computer), the computer's name, its operating system, the GitPersona version, and when it was activated and last seen. The app sends these device details whenever it checks your plan: at startup, every 12 hours while it runs, and when you open Settings → Account.
If you buy Pro— to create the payment, we send DOKU your email address, the invoice number, and the amount. We keep the order (plan, price list, amount, invoice number, status, payment date, and which part of the app you started from) and the payment notifications DOKU sends us. You enter your payment details on DOKU's page; we never see your full card number.
If you open a support ticket — the category, subject, and messages you write; your app version, operating system, and release channel; a random support ID the app creates for you, stored as a hash, so only your app can read the replies; and a hash of your IP address to limit spam. If you are signed in, the ticket is also linked to your account, email address, and plan. A diagnostics report is attached only while Attach diagnostics is on; you can preview it or switch it off before sending. It lists your app, OS, and Git versions, your plan, how many profiles, repositories, rules, SSH keys, and credentials you have, and recent log lines, with email addresses masked, your home folder replaced by ~, and tokens removed.
If you email us — your email address and your message, so we can answer you.

How and why we use it

To provide what you ask for: sign-in, the trial, Pro, the device limit, purchases, and refunds. This is needed to carry out our agreement with you.
To keep the records that tax and accounting law requires.
To prevent abuse, such as repeated trials or too many sign-in attempts, and to count downloads anonymously. These are our legitimate interests in running the service.
To deliver updates and to answer your messages.

The only emails we send are sign-in codes and replies to messages you send us.

Service providers

We rely on these providers, each only for its part of the service:

Vercel — hosts our server.
MongoDB Atlas — stores the server data described above.
Resend — delivers sign-in code emails.
DOKU — processes payments.
GitHub — hosts our downloads and updates.

Some of these providers store or process data outside Indonesia. The providers that host this website and our server may also keep standard technical logs, such as IP addresses, for security and reliability.

This website

This website uses no analytics or advertising cookies. It saves your theme, language, and price-list choices in your browser's local storage so they're remembered next time, and records download clicks as described above.

Security

We store sign-in codes, sessions, and IP addresses only as salted hashes, sign plan tokens so they can't be forged, and connect to our server over HTTPS. No system is perfectly secure. If a breach affects your personal data, we will notify you as the law requires.

How long we keep it

Sign-in codes, and the IP hash stored with them, are deleted within an hour.
A session ends when you sign out, when the device is deactivated, or after 180 days without use.
Account, plan, and device data are kept while your account exists.
The hashed ID of a device that has used the trial is kept so the trial can't be repeated on that device.
Order records are kept for as long as accounting and tax law requires.
Download records are kept as anonymous download statistics.
Emails and support tickets are kept as long as we need them to help you, and deleted on request.

Your choices and rights

You can use GitPersona without an account. If you have one, you can sign out and deactivate devices yourself in Settings → Account.

Under Indonesia's Personal Data Protection Law (Law No. 27 of 2022, "UU PDP"), you can ask us to:

tell you what personal data we hold about you and give you a copy;
correct data that is wrong or incomplete;
delete your data, or stop or limit how we use it.

Email gitpersona@outlook.com from the address you sign in with, so we can confirm the request comes from you. There is no delete button in the app; we delete accounts on request. When we do, we keep the order records the law requires and the trial record described above.