Aptly stores your résumé, cover letters, job tracker, and any personal API keys in localStorage on your device. We do not run a database of your documents. Local scoring and document editing happen in your browser. When you choose an AI feature, the text needed for that request leaves your browser for processing, as described below.
With Aptly's built-in AI models, the relevant résumé, job posting, or answer text is sent to an Aptly Cloudflare Pages Function, which forwards it to the selected model provider (Groq, Gemini, or DeepSeek). The function returns the result to your browser. The current proxy code does not intentionally save your submitted text in a document database or include it in Aptly analytics. Cloudflare and model providers may process request data under their own terms and retention settings; we have not verified a universal no-retention or no-training guarantee for every provider.
If you supply your own API key for a supported provider, Aptly stores the key in your browser and sends the request directly from your browser to that provider. The provider still receives and processes the text under its own terms. Choose local scoring and editing if you do not want to send résumé text to an AI provider.
Provider rules differ by plan. In particular, Google's Gemini API terms allow content from unpaid services to be used to improve its products and reviewed by people; paid-service terms differ. We have not confirmed which terms apply to Aptly's current Gemini project. Groq describes its inference retention and data controls here. Do not use AI features with information you are not comfortable sending to the selected provider.
| Tool | What it collects | Requires your consent? |
|---|---|---|
| GoatCounter | Page views and named feature events, including optional feedback categories. The event names do not include résumé or job-posting text; detailed event data stays in your browser. | No — cookie-free, runs by default |
| Microsoft Clarity | Session replay and heatmaps (mouse movement, clicks, scroll). Aptly marks the app and print areas for masking to exclude their document text from recordings; surrounding page interactions may still appear. | Yes — only runs after you click Accept |
| Email (optional) | If you voluntarily submit your email (waitlist / save progress), we store it to contact you about Aptly. Never sold or shared. | Given by submitting the form |
On your first visit we ask whether to enable Clarity. If you reject or ignore the banner, Clarity does not load. GoatCounter page views and named feature events still run, and any optional AI request you make still follows the route described above. You can change your Clarity choice by clearing this site's browser storage, which re-shows the banner.
Analytics providers retain data under their own policies. Aptly's current Pages Function code does not log prompt or response bodies or save them to a document database. Cloudflare offers request and error logging controls, but the live account settings have not yet been verified. Model providers have their own processing and retention rules, which can differ by plan. Data stored in your browser's localStorage stays until you clear it yourself — Aptly has no way to delete it remotely.
Questions about this policy or a data request: email privacy@tryaptly.app.