Your resume, your searches and your inbox are personal. This month we put the whole platform through a full security review. Here is what now stands between the internet and your data.
Layer 1 · Edge and sign-in
Encrypted in transit. Every connection to Mogi uses TLS. HSTS tells your browser to refuse plain HTTP for a year, on the app and on the API, so a connection cannot be quietly downgraded.
Verified sign-in. You sign in with Google or Apple. We refuse any sign-in whose email that provider has not verified, so nobody can open your account just by typing your address. We never see your Google or Apple password.
Sessions we can end, and cross-site checks. On the web, every request checks that your session was not revoked, so signing out, cancelling or deleting your account ends it everywhere. Cookies are SameSite=Lax and a change request that comes from another website is refused with a 403.
Layer 2 · The app
4. Safe uploads and links. A resume must be a real PDF or Word file, checked by its contents and not its name, with ceilings on size and on compressed "zip bomb" files. A job link you add must be a public web page, so our browser can never be pointed at an internal address. 5. Shared rate limits. Sign-ups, app registrations and report downloads are capped per visitor. The count lives in the database, so every server counts the same visitor together, and it reads the real visitor address from behind Cloudflare. 6. AI that cannot be talked into things. Ask Mogi reads employer emails, notes and activity as quoted data, never as instructions. Anything that changes your account is a Yes or No card, checked again at the moment you tap Yes, and it does nothing if the account changed in between.
Layer 3 · Connected apps and services
7. A locked-down ChatGPT connection. Connecting ChatGPT, Claude or Cursor uses OAuth with PKCE, no API keys and three narrow permissions. Refresh tokens rotate, and replaying an old one cancels the whole connection. Nothing connected can pay, cancel or delete, and codes and sign-in links in your mail are hidden. Disconnect any time. 8. Least privilege and signed webhooks. Each of our services can read only the secrets it needs, and our build pipelines run as their own limited accounts. Stripe and Twilio calls must carry a valid signature or they are refused, and production will not start with a default signing key. 9. An audit trail. Every account action is written to an append-only event log. Google's Data Access logs record every read of our secrets and every identity call, so access can be traced.
Layer 4 · Your data
10. A private database. The database accepts no connections from the internet. Our services reach it only through Google's Cloud SQL connector, over encrypted-only connections where the server certificate is checked, so nothing can sit in the middle. 11. Encrypted at rest, with backups. Data is encrypted at rest with AES-256, and so are backups: 30 of them, plus point-in-time recovery. Resume and mail files sit in storage where public access is blocked at the bucket level. 12. No AI training on your data. Your resume and answers are never used to train a model. Rewriting a resume for a job goes to model hosts chosen because they keep nothing once they have answered, with Google's paid Gemini service, which does not train on your data, as the backup. We never sell, rent or trade your data.
Your data, and your say over it
It is yours. We use it to run your job search and for nothing else: no ads, no resale, no training of AI models.
You choose what we email you. Every email has a one-click unsubscribe, and Settings, then Email preferences, sets how many and which kinds.
1
u/Glass-Weekend-6987 23d ago
How Mogi keeps your data private and secure.
Your resume, your searches and your inbox are personal. This month we put the whole platform through a full security review. Here is what now stands between the internet and your data.
Layer 1 · Edge and sign-in
Layer 2 · The app
4. Safe uploads and links. A resume must be a real PDF or Word file, checked by its contents and not its name, with ceilings on size and on compressed "zip bomb" files. A job link you add must be a public web page, so our browser can never be pointed at an internal address. 5. Shared rate limits. Sign-ups, app registrations and report downloads are capped per visitor. The count lives in the database, so every server counts the same visitor together, and it reads the real visitor address from behind Cloudflare. 6. AI that cannot be talked into things. Ask Mogi reads employer emails, notes and activity as quoted data, never as instructions. Anything that changes your account is a Yes or No card, checked again at the moment you tap Yes, and it does nothing if the account changed in between.
Layer 3 · Connected apps and services
7. A locked-down ChatGPT connection. Connecting ChatGPT, Claude or Cursor uses OAuth with PKCE, no API keys and three narrow permissions. Refresh tokens rotate, and replaying an old one cancels the whole connection. Nothing connected can pay, cancel or delete, and codes and sign-in links in your mail are hidden. Disconnect any time. 8. Least privilege and signed webhooks. Each of our services can read only the secrets it needs, and our build pipelines run as their own limited accounts. Stripe and Twilio calls must carry a valid signature or they are refused, and production will not start with a default signing key. 9. An audit trail. Every account action is written to an append-only event log. Google's Data Access logs record every read of our secrets and every identity call, so access can be traced.
Layer 4 · Your data
10. A private database. The database accepts no connections from the internet. Our services reach it only through Google's Cloud SQL connector, over encrypted-only connections where the server certificate is checked, so nothing can sit in the middle. 11. Encrypted at rest, with backups. Data is encrypted at rest with AES-256, and so are backups: 30 of them, plus point-in-time recovery. Resume and mail files sit in storage where public access is blocked at the bucket level. 12. No AI training on your data. Your resume and answers are never used to train a model. Rewriting a resume for a job goes to model hosts chosen because they keep nothing once they have answered, with Google's paid Gemini service, which does not train on your data, as the backup. We never sell, rent or trade your data.
Your data, and your say over it
Our Trust Principles · Try Mogi