Legal publisher
DevToolStack
Trust
Updated May 30, 2026Reviewed by OfferGuard AI research and review deskTrust center
A clear summary of how OfferGuard AI handles uploaded content, browser-linked history, payments, support, and product limitations.
Publisher identity
Payment verification
Data handling and support
Support email
support@devtoolstack.in
Support target
Usually within 1 business day
Review owner
OfferGuard AI research and review desk
Proof and review
Signals, evidence, and ownership are visible on-page
Payments
Credit grants are tied to verified payment events
Paid credits are not granted purely from a client-side success state. The trust model is built around server-side verification so the payment flow is harder to fake.
- +Client-side success alone does not grant paid credits
- +Payment verification happens before the credit state changes
- +Users can challenge missing credits through the public support path
Support
Users get a public correction and support path
Trust pages are only useful if people can challenge them. The site exposes a public support route for payment issues, scan concerns, trust questions, and corrections.
- +Support email: support@devtoolstack.in
- +Support hours: Mon-Sat, 10:00-18:00 IST
- +Response target: Usually within 1 business day
Identity
The product exposes who is responsible for public claims
OfferGuard AI shows a visible legal publisher, a public review owner, and trust pages linked from the main navigation so users can audit the product before relying on it.
- +Legal publisher: DevToolStack
- +Founder or product owner: DevToolStack product team
- +Review owner: OfferGuard AI research and review desk
Case-style examples
Short examples of how risky patterns show up in real use
Payment support caseHandled through verification
Payment success screen but no credit yet
A user sees a successful checkout state but wants to confirm whether credits were actually granted. The trust model checks the verified payment event instead of relying only on the client screen.
Next step: Use the public support path if credits do not appear after verification completes.
Trust clarificationExpected behavior
Question about browser-linked history
A user changes browsers or devices and cannot immediately see earlier history. The Trust Center explains that some current history behavior is browser-linked unless a supported account path is used.
Next step: Read the history and account limitations before assuming data loss.
Trust-page correction requestPublic review path
User wants a public correction
If a trust statement, scan explanation, or payment outcome looks wrong, the product exposes a public route for corrections instead of hiding behind a tool-only interface.
Next step: Email support with the exact page, issue, and smallest useful context.
Publisher and contact path
OfferGuard AI is published by DevToolStack under the legal entity 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.
How history and browser-linked access work
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.
How payments and credits are protected
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.
What happens to uploaded content
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.
What the product does not claim
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.
- +Do not send money based only on a recruiter chat or offer PDF
- +Do not share Aadhaar, PAN, OTPs, or bank details too early
- +Do not rely on any automated result as final proof
- +Preserve suspicious messages and documents as evidence where needed
Support and issue resolution
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. The current support target is Usually within 1 business day. Visible support routes and review ownership are part of how we make the product easier to audit.
FAQ
Common questions
How do paid credits get added?
Paid credits are granted only after the server verifies the payment flow.
Is my history tied to the browser or the account?
In the current product, history and entitlements are primarily browser-linked unless a supported sign-in or linking flow is used.
How can I contact support?
Use support@devtoolstack.in or the public contact page for payment, trust, and product issues.
Related guides
Keep verifying with the right next page
Privacy policy
Read the current policy for uploaded content, history, and optional identity flows.
Terms of service
Review user responsibilities, credits, and intended use.
Methodology
See how verdicts are framed and where manual verification still matters.
Contact support
Use the public support path for questions and corrections.
Next step
Use the guide, then verify the exact evidence
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
Legal publisher: DevToolStack
Review owner: OfferGuard AI research and review desk
Support: support@devtoolstack.in
Support target: Usually within 1 business day
Operating region: India