This page is written to reduce publication risk when comparing banks, fintechs, developer portals, and APIs using public information. It is a legal-risk-aware guide, not formal legal advice.
This is a practical, publication-oriented disclaimer you can place in a site footer, About page, or Terms section. It reduces risk, but it is not a guarantee of legal protection. Requires legal review before production use.
financeAI.tech is an independent research and analysis website based on public information. It is not affiliated with, endorsed by, sponsored by, or approved by any bank or company referenced.
Content is informational and is not financial, investment, legal, tax, accounting, or procurement advice. Users should verify details with official sources and their advisors.
We prioritize official bank sources (annual reports, investor materials, product pages, developer portals, regulatory filings). We use authoritative institutions and primary media as secondary sources when appropriate.
How to reduce “being wrong” risk when the underlying sources are dynamic.
Developer portals, product pages, and regulatory guidance can change quickly. Every important claim should show a source, a source date (if available), and a last-verified date.
If a bank, fintech, or user flags an error, publish a correction quickly and record what changed, when, and why. Prefer “correct then explain” over silent edits for high-impact items.
Comparisons should be framed as “publicly visible documentation signals” unless you have explicit, publishable official evidence. Flag gaps as “requires validation.”
How to keep comparisons useful without reproducing protected content.
We avoid uploading or reproducing proprietary client documentation, NDA materials, paywalled content, or internal bank documents. We summarize and link to public pages instead.
When quoting is necessary, use minimal excerpts with attribution. Prefer paraphrase. Avoid copying tables, full paragraphs, or large sections from bank sites or media.
For bank developer portals and documentation, link to the official portal and describe what is publicly visible. Do not scrape or mirror full documentation content.
A simple process to reduce IP risk and respond responsibly to rights-holder requests.
Send a notice with: (1) the URL on financeAI.tech, (2) the specific content you believe is infringing or incorrect, (3) the basis for your request (copyright/trademark/other), and (4) a contact email for follow-up.
legal@financeai.tech) and route notices to a tracked queue.
We aim to acknowledge notices promptly, review the claim, and either remove/correct content or explain why we believe it is permitted (with minimal necessary excerpting and attribution).
Immediate legal review is recommended if a page includes: logos, substantial copied text, paywalled material, performance/SLA claims, or statements that could be read as defamatory or as a bank endorsement.
Use brand and product names to identify products, not to imply endorsement.
Use trademarks (for example, CitiConnect®, CitiDirect, J.P. Morgan, CashPro) for identification only. Do not use logos unless you have explicit permission.
Do not imply partnership, certification, approval, or endorsement. Avoid phrasing that reads like a vendor listing or an official bank product page.
Legal review is recommended if you: (1) use a trademark in the site name, (2) use logos, (3) use brand fonts or look-and-feel too closely, or (4) use comparative language that could create confusion about affiliation.
Relevant if your goal is to look “very close” to another brand’s website.
Even if you do not use logos, a site design that closely mimics another brand’s look-and-feel can increase the risk of user confusion. Keep a visible non-affiliation disclaimer and avoid copying distinctive layouts, icon sets, or marketing language.
Use modern, clean UI patterns (typography, spacing, cards) without reproducing another company’s proprietary assets or distinctive trade dress. Use your own color system (for example Citi blue) and original copywriting.
Do not use third-party logos, icons, or brand imagery unless you have explicit permission or a license. If you need logos, implement a rights-checked asset pipeline and keep proof of license.
How to write comparisons that stay neutral and source-backed.
| Do | Instead of | Why |
|---|---|---|
| Say "public portal shows" or "publicly visible documentation indicates" | Say "supports" or "offers" (without qualification) | Public portals are not a complete product inventory; entitlements and region differences are common. |
| Use "appears" and label as analyst interpretation when needed | Make absolute claims from limited evidence | Reduces defamation and false advertising risk; encourages validation. |
| Use "requires validation" when evidence is incomplete | Fill gaps by assumption | Aligns with the platform's credibility goal and avoids misinformation. |
| Avoid "best/leading/superior" unless directly supported by sources | Marketing superlatives | Comparative claims often require stronger substantiation and legal review. |
Use this before production publication.
Confirm links work, the content is official, and source dates are captured. Prefer PDFs or official press releases for durable claims. Record last verified date.
Regulatory timelines, developer portal contents, and product pages can change. If the date matters, include it and add a "last verified" stamp.
Remove implied superiority. Replace with evidence-based descriptions of visibility, clarity, coverage, and limitations. Flag any negative comparative statements for legal review.
Avoid public claims about latency, uptime, throughput, error rates, or security unless the bank has publicly disclosed them. If included, cite exact sources and dates.
Ensure you are not copying large portions from sources. Use short excerpts only when necessary, and prefer paraphrase with links.
Use product names with correct trademark markings where practical. Avoid logos and confusing brand mimicry. Keep the non-affiliation disclaimer visible site-wide.