Publisher
DevToolStack
Trust
Updated May 10, 2026Reviewed by OfferGuard AI research and review deskA clear summary of how OfferGuard AI handles uploaded content, browser-linked history, payments, support, and product limitations.
Publisher
DevToolStack
Support email
support@devtoolstack.in
Payment model
One-time credits with server-side verification
Operating region
India
OfferGuard AI is published by DevToolStack. Support, trust, and product questions should use the public contact path at /contact or the support email support@devtoolstack.in.
Publishing a clear contact route matters because a trustworthy product should not feel anonymous when payments, identity concerns, or public claims are involved.
The current version of the product uses a browser-linked profile to remember scan history and available credits. That means some history and entitlement behavior is tied to the current browser unless the user chooses a supported sign-in or account-linking flow.
This design keeps the first use lightweight, but it also means users should understand that switching devices or browsers may change what history is immediately available.
Paid credits are added only after the server confirms the relevant payment event. A client-side success screen alone does not grant paid credits, which reduces the risk of fake client callbacks or incomplete payment flows being treated as successful.
This is important because job seekers using the product to avoid scams should also be able to trust the payment and credit grant flow inside the product itself.
Uploaded files and pasted text are processed so the product can extract readable content, identify risk signals, and show related result history for the same browser-linked profile where applicable.
Users should only upload content they are allowed to share and should avoid including unrelated financial or personal material that is not necessary for the review.
OfferGuard AI is intended to reduce obvious hiring risk, not to act as legal advice, employer verification, or final proof of fraud or legitimacy. Users should still confirm company domains, recruiter identities, interview history, and payment safety independently.
If a user believes a scan is misleading, a payment credit did not arrive, or a trust page needs correction, the public support path is support@devtoolstack.in. Visible support routes and review ownership are part of how we make the product easier to audit.
FAQ
Paid credits are granted only after the server verifies the payment flow.
In the current product, history and entitlements are primarily browser-linked unless a supported sign-in or linking flow is used.
Use support@devtoolstack.in or the public contact page for payment, trust, and product issues.
Related guides
Read the current policy for uploaded content, history, and optional identity flows.
Review user responsibilities, credits, and intended use.
See how verdicts are framed and where manual verification still matters.
Use the public support path for questions and corrections.
Next step
These pages are designed to answer the search query directly and help users think clearly before they act. When you have the actual message, PDF, screenshot, or offer letter in hand, run the scanner and compare the result against the guidance above.
Why this page exists
We use public trust pages, visible review ownership, and related-topic links so users can verify the product itself, not just the suspicious offer they uploaded.
Publisher: DevToolStack
Support: support@devtoolstack.in
Operating region: India