Recipient privacy
Every delivery uses one To address. Recipient lists are never exposed through CC or BCC.
Create a campaign once, personalize it with recipient data, attach your CV, and let each company receive an independent Gmail message—never CC or BCC.
Build once, review every detail, and keep control until delivery starts.
Authorize sending without sharing your Google password.
Import recipients, personalize fields and attach your application documents.
Schedule delivery and follow every sent, failed or pending message.
Search role-based hiring emails published on official company pages.
Every delivery uses one To address. Recipient lists are never exposed through CC or BCC.
Edit drafts and change the schedule while the campaign is still waiting to send.
See what is pending, sent, or failed and keep credit usage visible.
Connect Gmail, prepare the campaign, and review it before anything is sent.
Your platform account and sending account stay separate. You can change the Gmail sender later.
0 of 4 complete
| Campaign | Status | Progress | Scheduled | Created |
|---|
Choose a CV from your library or upload a new file below. AI will extract your profile and specialization.
Analyzing skills, languages, experience, and target roles from your CV.
🟢 Step 1/3: Finding verified hiring contacts for your specialization...
Request access to search public company sources by city and sector.
Credits are reserved when a campaign is created and consumed only after a successful send.
| Date | Activity | Balance change | Reserved change | Balance after |
|---|
Used as the default when scheduling a new campaign.
Choose the language used by the platform interface. Your campaign content is never translated.
Review how the platform handles data and the rules that apply to campaigns.
Questions, delivery issues, or account help. Send a request and track its status from here.
This signs you out of the platform. It does not revoke Gmail until you disconnect it above.
Usage, support, and operational health without exposing private message content.
Privacy-safe landing page performance without raw IP addresses.
Anonymous visitor hashes are retained for 90 days. Raw IP addresses and full browser signatures are not stored.
Keys are encrypted and never returned to the browser. A provider and task must both be enabled before clients can use it.
Read-only server, database, worker, queue, and storage checks.
| Customer | Request | Status | Created |
|---|
| User | Status | Gmail sender | Credits | Campaigns | Joined |
|---|
| Action | Actor | Target | Details | Time |
|---|
Private email content, tokens, request bodies, and stack traces are never shown here.
| Code | Route | Request ID | User | Time |
|---|