Skip to content
Security & Privacy

You can't leak what we never receive.

GanttPulse is local-first by architecture, not by policy. Your projects don't pass through our servers because there are no servers of ours in the path.

The architecture is the proof

Most tools ask you to trust their security. With GanttPulse you can verify it: run the app, watch your network, and see that no project data leaves the machine. Proof you generate yourself beats any certificate we could wave at you.

Verify it yourself — five minutes

  1. 1

    Go offline. Turn Wi-Fi off (or unplug), open GanttPulse and work — planning, scheduling, dependencies and exports all run, and the license validates locally.

  2. 2

    Watch the network. Reconnect and observe the app in Windows Resource Monitor's Network tab (or add a firewall outbound-block rule for it). While you plan, there are no connections to outside hosts — loopback 127.0.0.1 traffic is just the app's UI talking to its own local engine on your machine.

  3. 3

    Use the AI. Now exactly one external connection appears — to the LLM provider you configured with your own key, identifiable by hostname. Point it at a local model and even that disappears.

  4. 4

    See anything else? Email [email protected] — that's a report we want.

Data stays local

Your projects live in a file on your machine or your own server. We never receive, store, or process them.

Bring-your-own-key AI

The assistant uses your API key and your chosen provider. We're never in the loop, and never see your prompts.

Runs fully offline

Plan, schedule, and export with no connection. Suitable for air-gapped and restricted environments.

Verifiable builds

Every build re-checks a 140-file self-integrity manifest at boot. SHA-256 checksums ship with every release, and Authenticode-signed builds land at launch.

No telemetry

No analytics, no phone-home, no usage tracking baked into the app. Nothing reports back to us.

Offline license check

Your license validates locally with public-key crypto — no seat server, no activation call to us.

What leaves your machine — the honest list

  • Nothing, by default. Planning, scheduling, dependencies and exports are entirely local.
  • Only when you use the AI: the context you send goes to the LLM provider you chose, with your key. You decide which provider or run a local model so nothing leaves at all.
  • Never to us. No telemetry, no analytics, no copy of your data on any GanttPulse server.

The list above is the whole story — the formal privacy policy publishes before launch.

Questions IT teams ask

Where exactly does my project data live?
In a database file on your own machine (or a server you control). There is no GanttPulse cloud holding a copy.
Is the data encrypted at rest?
Your project file sits on your disk and is protected by your operating system's disk encryption (BitLocker / FileVault). Because nothing is sent to us, there is no second copy to secure elsewhere.
What about the AI — doesn't that send data somewhere?
Yes, and we're upfront about it: when you use the AI assistant, the relevant context is sent to the LLM provider you configured, with your own key. You control which provider, and you can point it at a self-hosted model for zero external egress.
Can we run it in an air-gapped network?
Core planning, scheduling, dependencies and exports work with no internet at all. Only the AI assistant needs a reachable model endpoint (which can be on your own network).
What happens to our data if GanttPulse shuts down?
Nothing. The license validates offline with public-key cryptography — there is no activation server to lose. Your projects are database files on infrastructure you control, and everything exports to open formats (Excel, CSV, MS Project XML, JSON) at any time.

Built carefully, by one person you can email

GanttPulse is built independently by Ronen Aruch — no growth team, no investors who need your data to become the product. Questions land in the builder's inbox. The story →

  • 7,600+ automated tests
  • Date math verified across 9 timezones
  • Ed25519 offline licenses — no activation server
  • 140-file integrity manifest, re-checked at boot

Have a security questionnaire or need a deeper review?

[email protected]

We publish a machine-readable security.txt (RFC 9116).