Security at ApplyPilot
This page describes controls in the current prototype and its honest limitations.
Every profile, document, recommendation and application query is scoped to the authenticated user.
Uploads and extracted résumé text remain private and have no public download URLs.
File size, extension, declared type and file signature are checked before storage.
On the private OpenAI Sites deployment, the agent requires both Sites service access and a separate ApplyPilot integration secret, plus user consent, rate limits, idempotency and audit records.
Backups use AES-256-GCM before private storage or an optional dedicated Google Drive folder.
Users can revoke the agent, export records and permanently delete live account data.
Current limitation
The Grok adapter, encrypted backup schedule and Google Drive writer remain disabled until their separate server-only settings are configured. The two-boundary service claim applies to the private OpenAI Sites deployment; another host must provide an equivalent private gateway. This prototype does not yet submit to employers or job boards, process payments or claim production compliance certification. Commercial launch still requires independent penetration testing, malware scanning, an enforced retention schedule, incident-response procedures and jurisdiction-specific legal review.
Responsible reporting
If you suspect a security issue, stop using the affected workflow and contact the operator through the official support channel. Do not include passwords or sensitive documents in an initial report.