A useful inquiry starts with context. Select a channel, link the relevant page and describe the question. About Emily Hartman.
Editorial inquiries
editor@fraudtoolatlas.comCorrections, source submissions and new-product suggestions.
- Include the page URL and exact passage.
- Link current product documentation, pricing and the relevant plan or version.
- Explain the user-protection workflow when suggesting coverage.
Partnerships and research
partnerships@fraudtoolatlas.comB2B SaaS research, educational resources and collaboration proposals.
- Describe the organization, audience and proposed work.
- Identify the product scope and participating teams.
- Keep commercial terms separate from evidence for a factual correction.
Privacy and data inquiries
privacy@fraudtoolatlas.comQuestions about this website and information you choose to send to the publication.
- Identify the interaction and approximate date.
- Use the site’s privacy notice for hosting and link context.
- Avoid credentials, payment details and unnecessary identity documents.
Promotional links and disclosures
affiliates@fraudtoolatlas.comQuestions about vendor links, promotional parameters and disclosure wording.
- Include the publication page and destination URL.
- Name the parameter or wording you want clarified.
- Send account credit and registration issues to the provider operating the offer.
Press and media
press@fraudtoolatlas.comQuestions about the atlas, its framework and the fraud-software category.
- Include your publication, subject and deadline.
- Link the passage or figure you plan to discuss.
- Identify the product and source date where they matter.
Make the request easy to review
Use a clear subject and include the product, source and date where relevant. The corrections process explains factual updates. A vendor’s account, API access, billing or bonus credit should be handled by that provider’s own support.