Terms of Service

ApplyOptics is a product of AnchorForged. “We,” “us,” and “our” mean AnchorForged operating ApplyOptics. “You” means a person using the site, including a candidate trying the demo or hosted apply flow and an employer asking about a design-partner seat.

AnchorForged also offers Chiefly, a sibling product. Chiefly is separate from ApplyOptics. These terms do not govern Chiefly. Chiefly’s own App Store listing is the source of truth for that product. Using ApplyOptics does not create a Chiefly account, and using Chiefly does not create an ApplyOptics account.

If you later sign a written design-partner agreement or order with us, that writing controls where it conflicts with these public terms. These pages are not a data processing addendum and not a production service-level agreement.

We transcribe, not score! A candidate can upload a hard resume — two-column, table, scanned, Word, PDF, or a phone photo. A vision model transcribes fields and flags anything it is unsure about. The candidate confirms those fields before submit.

The military skills translator lists drafting examples for a job code and for additional duties you select, so you can paste civilian wording onto a resume and confirm it. You can describe an extra duty for that browser session. Wording suggestions are built in the browser from what you type. The page labels them “Your wording. Review before using.” and does not fill in numbers you left blank. You can ask ApplyOptics to review that wording. A suggestion is reviewed before it can become a reviewed translation, and your browser does not write that translation. The translator does not state an accuracy percentage. It is not hiring eligibility and not a Department of Defense endorsement.

We do not score candidates. We do not rank them. We do not filter them. We do not recommend a hire. ApplyOptics is not an automated employment decision tool, and a transcript is not an employment decision. The employer remains responsible for hiring decisions and for the applicant tracking system (ATS) they already run.

Transcription can be wrong. Low-confidence fields are highlighted because the reader was unsure. You should read and correct the fields before you treat them as accurate. A confidence flag is not a candidate score.

The page at /demo is a public demonstration on a sample posting. You can upload a resume, see a transcription, confirm uncertain fields, and submit. That submit stays in the demo. It does not post an application to Greenhouse, Lever, or any other ATS.

There is no live one-line overlay script for an employer careers page. Asking about a design-partner seat is a conversation, not a purchase of a production overlay or a live ATS network. A host may turn on a beside-form confirm panel at /beside. That panel lets a candidate confirm a transcript and copy it into a form beside it. It does not type into a third-party careers page. When it is off, the page says so. The public demo submit stays simulated.

The hosted page at /apply is the path that can write to an employer ATS, and only after the candidate confirms the fields. The live write path, when the host is configured with credentials, is Greenhouse Job Board. We do not send a score or a rank with that write.

Other connectors fail closed. If the required credentials or tenant access are missing, ApplyOptics does not invent a successful application. Workday, Taleo, and Rippling are not live write paths. A missing configuration is a failed write, not a silent success. The public demo never calls these connectors.

When a configured Greenhouse write succeeds, the application is the employer’s record in the employer’s ATS. That employer’s terms and privacy practices apply to data that reaches them. The same receipt lists fields that were not posted, including a location without coordinates, free-text education, and job questions this path does not collect, such as file questions other than the resume, EEOC, and demographic surveys. We do not invent coordinates or education IDs.

On a resume extract, we send the file to the configured vision provider and return a transcript for you to confirm. When both Gemini and Anthropic are configured, and cross-checking is not turned off, the file is sent to both, and fields they disagree on are flagged for you to confirm. We do not train ApplyOptics models on uploads.

A zero-data-retention arrangement with those providers is not in place. Each provider that receives the file may retain API inputs under its own terms. Details are in the Privacy Policy.

Waitlist and design-partner requests are different. If you leave your name, work email, and company, we keep those contact details so we can reply. Those fields are contact details for the conversation.

Public pricing, including the Spark early-access teaser, is indicative. A “fill” means a confirmed transcription or apply, not a hire. Numbers can change before a design partner is on a written plan. Nothing on the site is an offer that creates a paid subscription by itself.

You agree not to:

• Upload a resume or personal data you do not have the right to share for this purpose.
• Use ApplyOptics to score, rank, or automatically reject candidates.
• Probe, overload, or bypass rate limits, bot checks, or access controls.
• Misrepresent a simulated demo submit as a live application to an employer.
• Resell the site or present ApplyOptics as your own product.

You keep ownership of the resume you upload. You give us a limited permission to process it solely to provide the transcription, confirmation, and — only on a configured hosted apply — the ATS write you asked for.

ApplyOptics is an early product. The site, demo, and hosted apply flow are provided as available, without a warranty of uninterrupted operation, perfect transcription, or a particular hiring outcome. Accuracy checks we publish are about our own premise-check harness. They are not a customer service level.

To the fullest extent the law allows, AnchorForged is not liable for indirect, incidental, or consequential damages, or for hiring decisions made by an employer, arising out of use of the public site. Nothing here limits liability that cannot legally be limited.

We may update these terms as the product changes. The effective date at the top of this page will move when we do. Continued use of the site after the new date means you accept the updated terms. The current effective date is September 29, 2026.

Questions about these terms: [email protected].