git checkout -b feature/privacy

Commit Code.
Not Your Inbox.

The average developer's email is scraped 14 times per week from public `git log` history. Use a TempoMail Developer Alias to verify GitHub, test CI/CD pipelines, and keep your primary inbox free of recruiter spam.

Generate Alias
git config user.email "..."
bash — tempomail-cli
git clone https://github.com/privacy/secure-repo.git
Cloning into 'secure-repo'...
remote: Enumerating objects: 42, done.
git config --global user.email
"dev_88x2@tempomailusa.com"
git push origin main
Writing objects: 100% (3/3), 283 bytes | 283.00 KiB/s, done.
Total 3 (delta 0), reused 0 (delta 0)
_
Verification Code
882-910
1.2M+
Verified Commits
200ms
Code Delivery
TLS 1.3
Encryption
Zero
Logs Retained

Your `git log` is Public Record

Every open source contribution you make attaches your personal email to the commit metadata. This data is permanent, searchable, and scraped by bots.

The "Scraper" Economy

Recruitment agencies run scripts specifically targeting contributors of popular repositories (React, Vue, TensorFlow). They harvest `Author: email` fields to build cold-outreach lists.

Identity Triangulation

By linking your GitHub commit email to leaked databases from other services, malicious actors can build a full profile of your identity, physical location, and employer.

Engineered for GitHub's Filters

Phase 1

Domain Reputation

GitHub blocks generic temp mails. We rotate premium domains that are "pre-warmed" to pass GitHub's signup heuristics, ensuring your account isn't flagged as spam immediately.

Phase 2

Socket Delivery

Verification codes (OTPs) have short TTLs. Our architecture uses WebSockets to push the email payload from our MTA to your browser in < 200ms. No refreshing needed.

Phase 3

Metadata Scrubbing

Before the email hits your screen, we strip invisible tracking pixels and sanitise headers, ensuring the sender cannot fingerprint your device or location.

QA & TESTING

Test Authentication Flows

Developers often need to test "Invite Member", "SSO Login", or "Password Reset" flows for their own applications or GitHub Apps. Using your personal Gmail for this is messy.

  • Generate 10+ unique emails in seconds.
  • Validate "Magic Link" delivery instantly.
  • Isolate test accounts from production data.
testing_log.txt
# Validating Signup Flow
[INFO] Created user: qa_test_01@tempomailusa.com
[INFO] Verification email received.
[SUCCESS] Account verified. Token exchanged.
# Cleaning up
[DELETE] Inbox purged from memory.

Configuration Protocol

1

Generate Secure Alias

Navigate to the homepage. A secure email string is generated instantly in RAM.

> Allocating clean node... Done.
2

Configure Git Global

Set this email in your global config to sign all future commits with it.

$ git config --global user.email "alias@tempomailusa.com"
3

Verify & Commit

Enter the verification code from GitHub. You are now ready to push code anonymously.

-----BEGIN RECOVERY KEY-----
7x99-alpha-dev-secure-8821-gh
-----END RECOVERY KEY-----
Persistence

The "Session Recovery" Feature

Most temp mail services destroy your inbox when you close the tab. This is dangerous for GitHub accounts, as you might hit a "Suspicious Login" check next week.

TempoMailUSA provides a cryptographic Recovery Key. Save it locally. It allows you to resurrect the exact same email address later to receive 2FA codes or password resets.

Privacy Grade Comparison

Feature TempoMailUSA Standard Temp Mail GitHub No-Reply
Inbox Access Instant (Read/Write) Slow / Ad-filled No Inbox (Write Only)
Signup Verification Clean IP Often Blocked Impossible
Session Recovery Yes (Key) No N/A

Pro Tip: SSH Key Isolation

Creating a private GitHub account with a temp email is step one. However, if you use the same SSH key as your main account, GitHub can link the two identities.

# Generate a fresh key for the temp account
$ ssh-keygen -t ed25519 -C "alias@tempomailusa.com" -f ~/.ssh/id_temp_gh

Enterprise-Grade Security

TLS 1.3 Encryption

All traffic between GitHub's mail servers and our gateway is encrypted. We force TLS upgrades to prevent man-in-the-middle attacks on your verification codes.

RAM-Only Storage

We do not write emails to hard disks. Data exists in volatile memory only for the duration of your session. Once the server reboots or session ends, it is scrubbed.

Technical FAQ

Do you offer an API for automated testing?
No. To maintain the integrity of our IP reputation and prevent abuse, we do not provide API access. Our service is strictly for manual, interactive use via the web interface.
Does this work with GitHub Student Pack?
Generally, no. GitHub Student Packs require valid .edu email addresses. Our service provides general-purpose domains (.com, .net) suitable for standard account creation, but not academic verification.
Can I use this for GPG Key signing?
Yes. You can generate a GPG key associated with the TempoMail alias to verify your commits on GitHub. This adds a "Verified" badge to your commits while keeping your identity private.

Developer Feedback

"I manage 50+ test accounts for our org's SSO integration. TempoMail is the only service that reliably delivers the GitHub magic link every single time."

DE
DevOps Engineer

"Finally stopped the spam from recruiters scraping my git log. My public profile is clean, and my inbox is quiet."

FS
Full Stack Dev

"The recovery key feature is brilliant. I needed to verify a device login on an old alt account and it worked perfectly."

OS
OS Maintainer

Distributed Edge Nodes

Routing email traffic away from blacklisted data centers.

Critical Advisory

Do Not Use for Repo Ownership

While TempoMail is secure, disposable emails should not be the sole owner of mission-critical production repositories. If you lose your Recovery Key, you lose access. Use this tool for testing, contribution, and secondary accounts only.

Ready to Commit?

Join 12,000+ developers protecting their privacy with TempoMailUSA.

Initialize Secure Inbox

NO CREDIT CARD • NO API KEY • INSTANT