Privacy Policy

Rejectory tailors resumes and cover letters and tracks the applications they go into, built to keep your data in your hands. This policy explains what that means in practice, covering what we do and do not collect, and where your applications actually live.

The short version

Rejectory has no backend and no database of its own. Your applications, documents and profile are stored wherever you choose, in a folder on your device, your browser's local storage, or your own Google Drive. We never receive a copy, and there are no accounts to create with us. The only thing we collect is fully anonymous usage analytics, never your applications or anything you write in them.

What we collect

Your applications, documents and profile never leave the storage you choose, and are never sent to us, because we run no server or database that could receive them. The one thing we do collect is anonymous usage analytics, described below. It is aggregate and event-level, with nothing that identifies you or reveals what you wrote.

Where your data lives

You pick one of three places, and your data stays there:

• A local folder on your device, which only you and the apps you allow can read.
• Your browser (IndexedDB), kept on the device you are using.
• Your own Google Drive, in a folder you choose, owned by your Google account.

You can export everything as a backup file at any time, and move it between these places yourself.

Google Drive access

If you connect Google Drive, Rejectory requests the limited drive.file permission. This grants the app access only to a single Rejectory folder it creates for your data, and the files inside it. It cannot see, read or touch anything else in your Drive, and you can move that folder wherever you like.

Sign-in happens through Google. The access token Google returns is kept in this browser tab's session storage, cleared when you close the tab, so a reload does not ask you to reconnect. It expires within about an hour and is never sent to us (again, there is no server to send it to). You can revoke Rejectory's access at any time from your Google Account permissions page. When you connect Drive, Google's own Privacy Policy also applies.

Data stored on your device

Rejectory keeps a few small preferences in your browser's local storage, such as your chosen theme and which storage option you last used, so the app behaves consistently when you return. These stay on your device and are not sent anywhere.

Hosting and logs

The Rejectory website is served as static files by Google Firebase Hosting. Like any web host, it may keep standard technical logs (such as IP addresses and requested files) for security and reliability. These are handled by the hosting provider and are not used by us to profile or track you.

Anonymous analytics

To see how Rejectory is used and improve it, we collect anonymous usage analytics through Google Analytics for Firebase. This is event data such as the app loading, an application being added, or a status moving to "interview". It never includes your application content, company names, notes or documents, and it carries no name, email or account.

Analytics uses a random identifier, stored on your device, to count distinct devices and sessions, and IP addresses are anonymised. None of it can be tied back to you or to a specific application, and we use no advertising trackers.

Deleting your data

Because we hold no copy, you are always in control. Delete the local folder or its files, clear the app's data in your browser, or remove the Rejectory folder from your Google Drive and revoke its access. That is all it takes; there is nothing on our side to request deletion of.

Children

Rejectory is not directed at children under 16, and we do not knowingly collect their data.

Changes to this policy

We may update this policy as the app evolves. Material changes will be reflected here with a new date at the top.

Contact

Questions about privacy? Reach us at info@rejectory.com.