Fahid Digital Ventures LLC · Five mailboxes, each with an owner
Contact
Pick the mailbox that matches what you need and you reach someone who can answer it. The form below routes by subject and tells you exactly where your message went.
If you have lost work right now, do not wait for us. Open GitAegis, switch to Doctor, and run Lost Work. Nothing on that path mutates your repository without taking a capsule first, and do not run git gc, git prune or git reflog expire while you wait.
Replies come from a person · No ticket-deflection bots · No phone queue, no live chat
Where to write
Each of these is read by someone who can act on it. Writing to the right one is the single biggest thing you can do to get a fast answer.
Product support
support@gitaegis.comInstallation, a Git that GitAegis will not accept, a repository behaving strangely, a crash, or a recovery that did not go the way you expected. Attach a support bundle if you can. It turns most of a diagnosis into a five-minute read.
Licensing and procurement
sales@gitaegis.comThere is nothing to buy today. The macOS edition is free and there is no checkout. Write here about volume licensing, purchase orders, or a vendor security questionnaire and you will get an answer in writing rather than a call.
Vulnerability reports
security@gitaegis.comReport a security issue here rather than through support and never in a public issue tracker. Include what you did, what you observed, and how to reproduce it. No published PGP key exists yet, so send plain text and leave out anything you would not want in an inbox.
Privacy and data
privacy@gitaegis.comQuestions about what the product records and what this site records. The free macOS edition links no HTTP client, so for most readers the honest answer is that there is nothing held about you to access, export or delete.
Press and media
press@gitaegis.comFact checks, interview requests, and permission questions about the brand assets. If a fact on this site is wrong, this is the fastest way to have it corrected.
Everything else
Anything that does not fit one of the five. The form below routes by subject and names the mailbox it reached.
What happens to your message
There is one queue. GitAegis is a free macOS release with no plans to sell, so there are no support tiers to route you into and no priority lane to buy.
| What you are writing about | Goes to | What happens first |
|---|---|---|
| Lost or damaged work | support@gitaegis.com | Read ahead of everything else in the queue. The first reply tells you what not to run while it is being looked at. |
| A bug, a crash, or a repository behaving strangely | support@gitaegis.com | Read against your support bundle and the Operation Journal entry you name. |
| A security vulnerability | security@gitaegis.com | Acknowledged, then worked privately. Never discussed in a public tracker while it is open. |
| Privacy, or a question about what is recorded | privacy@gitaegis.com | Answered in writing, naming what is held and what is not. |
| Licensing, procurement, or a vendor security questionnaire | sales@gitaegis.com | Answered in writing. There is no discovery call and no sales development team. |
| Press, a fact check, or brand assets | press@gitaegis.com | Answered in writing. A wrong fact on this site gets corrected first and replied to second. |
No first-response target is published here, because none would be honest yet: there is no support rota to measure and no agreement to hold it to. What is true is the ordering. Anything involving lost or damaged work is read before anything involving licensing.
A reply means a person reading your message and answering it. There is no automated receipt pretending to be one.
Send a message
Every field is required. The subject decides which mailbox owns it.
Before you use this form
Reporting a security vulnerability? Write to security@gitaegis.com directly rather than using this form, and never open a public issue for one while it is unfixed.
Data loss? Say so in the first line. It changes the order the message is read in, and the first reply will tell you what not to run in the meantime.
What to include when you report a bug
Paste this block into your message and fill it in. It removes an entire round trip.
GitAegis version:
macOS version and chip: e.g. 14.5, Apple Silicon
Git version: output of `git --version` (GitAegis requires 2.38.0 or newer)
Repository shape: rough size; submodules, worktrees, LFS, shallow clone?
Mode and operation: Home / Work / History / Review / Doctor, and what you ran
What you expected: one sentence
What happened: one sentence, plus the exact error text
Support bundle: attached / not attachedSupport bundles. A support bundle is generated inside GitAegis, in Doctor → Export. It is written to your own disk and every part of it is scanned for secrets before you see it. GitAegis does not transmit it. There is no background “send diagnostics” button, and no network client in the build that could be one.
It carries the GitAegis version, your operating system, the Git runtime that was resolved, the most recent Doctor report for each repository in your catalogue, and up to three recent session logs. It never carries your file contents, your commits, your credentials or a capsule’s payload.
Path redaction is a switch on that screen and it is off unless you turn it on, so check the paths before you attach it.
What we do not have
No phone queue. No live chat widget. No sales development team that will follow up on a page view, and no sequence you get enrolled in for reading this page.
If you write, a person reads it. If you do not write, nothing happens, which is the arrangement most engineers would pick if anyone asked.
Fahid Digital Ventures LLC is the entity behind GitAegis. Email reaches it faster than anything else.
Free edition · No account required
A recovery capsule before every risky Git operation.
You see the exact commands before they run, and the operation is refused if the capsule cannot be written.
Requires Git 2.38.0 or newer, already installed.
Every risky operation, in this order
- Previewthe exact commands, shown before anything runs
- Capsulerefs, index, staged and working changes, untracked files, operation state: written to disk first
- Executethe commands as shown, or not at all
- Journalplan, commands, capsule id, outcome