Terms & Disclaimer
Terms & Disclaimer — Last updated: July 2026.
This document combines Terms of Use and a strict Disclaimer into one agreement for Numbro. It explains acceptable use, limits on relying on phone-number results, bans on defamation and scraping, and report/objection rules. By using the site you expressly agree. If you disagree, stop using the services immediately.
Read this together with the regional Privacy & Cookie Policy. A regional addendum at the end names related statutes (PDPL / GDPR / CCPA).
1. Brief definitions
- Platform: Numbro web services.
- User: any visitor using lookup, reports, or objections.
- Content: text, results, labels, reports, and materials shown on the platform.
2. Acceptance and eligibility
You represent that you are old enough under your local law to use the services and that you will use them only for lawful purposes. If you act for an organization, you represent you are authorized to bind it.
3. Nature of the service
Numbro is an informational / community platform for phone-related scam alerts and user reports/objections. It is not an official investigative authority, telecom regulator, police substitute, bank, or court, and it does not provide personalized legal advice.
4. Strict accuracy disclaimer (AS IS)
Services and results are provided AS IS and AS AVAILABLE without warranties of accuracy, completeness, freshness, merchantability, fitness for a particular purpose, or non-infringement.
- We do not guarantee that a lookup result is a definitive identity determination.
- You alone are responsible for decisions based on results.
- To the maximum extent permitted by law, we are not liable for direct or consequential damages arising from use or inability to use the services.
- If information about you is inaccurate, use the objection/correction flow.
5. Acceptable and prohibited use
Personal lawful use is allowed. Prohibited: stalking, harassment, extortion, privacy invasion, defamation, knowingly false reports, impersonation, spam, attacks, or resource abuse. Violations may lead to bans and reports to authorities.
6. Reports and objections
You are solely responsible for the legality and truthfulness of submissions. You grant a non-exclusive license needed to operate and moderate the service. We may hide, delete, or reject content. OTP checks reduce abuse; they do not certify the substantive truth of a report.
7. No scraping
Without prior written permission: no crawlers, bulk harvesting, derivative redistribution databases, commercial resale of outputs, or bypassing rate limits/security controls.
8. Ads and third-party links
Google AdSense and outbound links may appear. We are not responsible for third-party content or your dealings with them.
9. Intellectual property
Brand, UI, software, and original text are protected. No copying or commercial reuse without written permission.
10. Suspension
We may restrict or terminate access immediately for violations, security threats, or necessary maintenance, without compensation where permitted by law.
11. Changes
We may update these terms. Continued use after an update constitutes acceptance of the current version.
12. Contact
13. Expanded disclaimer notes
The platform does not provide judicial verification of every report. Human or automated review layers may be incomplete. Any reliance on a result, name, or label remains your risk. Marketing wording in the UI is never a warranty of accuracy.
If a user harms others through misuse, that user bears responsibility. We may remove content and cooperate with valid legal requests. Content remaining online is not an endorsement of its truth.
14. Indemnity (where permitted)
To the extent permitted by your law, you agree to indemnify the platform against reasonable claims arising from your breach, your submissions, or unlawful misuse — without overriding mandatory consumer protections.
15. Severability; no waiver
If one clause is unenforceable, the rest remains. Failure to enforce a right once is not a waiver.
16. Language
Translations may exist. We aim for substantive consistency across locales for the same cluster.
17. Practical examples
- Allowed: checking a number after a suspicious call; filing a good-faith report.
- Allowed: filing an objection if your number appears with incorrect information.
- Forbidden: using results to shame or threaten someone online.
- Forbidden: bulk scraping to build a competing database.
- Forbidden: spam-reporting to abuse moderation queues.
18. Security controls
Rate limits, App Check, and reCAPTCHA may protect the service. Bypassing them is an independent breach.
19. Financial harm and OTP caution
Common phone scams involve bank impersonation, urgent transfers, or OTP harvesting. Numbro may increase caution through alerts but does not replace official bank channels and does not guarantee that absence of a report means a number is safe. Any financial loss from your decision remains outside platform warranties under the AS-IS clause.
The same applies to medical, legal, or real-estate advice that may appear indirectly in user comments or reports; the platform is not a professional accreditation body. Use independent specialized sources before major decisions.
20. Republishing public results
Seeing a result on the platform is not permission to republish it to shame or threaten someone. Lawful personal review is allowed; weaponizing the platform for public humiliation is not.
Taking screenshots of results about others and posting them with insulting captions is also prohibited. If you must share a result with a competent official body, use their channels and minimize data.
21. Future accounts and APIs
If user accounts or APIs are offered later, they may have additional terms and can be suspended for abuse or automated extraction. Until separate API terms exist, this document remains the general conduct reference.
Any API key or access token issued to you is personal and non-transferable. You are responsible for secrecy. Public leakage is a breach and may cause immediate revocation.
22. Availability
Service may be interrupted for maintenance, vendor outages, attacks, or force majeure. We do not guarantee absolute uptime. Report/objection handling may be delayed during incidents.
We may change UI layout or retire a feature for security or product reasons without that alone constituting a breach, while seeking to keep core lookup/reporting reasonably available.
23. Conflicts of text
If a short UI blurb conflicts with these Terms, the Terms control. If the Privacy Policy conflicts on pure personal-data processing issues, the Privacy Policy controls for that issue, while anti-abuse rules remain in force.
Section headings are for convenience only. “Including” means examples without limitation unless stated otherwise.
24. Number-owner complaints — correct path
If your number appears with information you believe is wrong: (1) use objection/contact with a clear statement, (2) do not threaten staff, (3) do not file retaliatory false reports. We handle serious requests operationally under our rules. This path aims to reduce unnecessary disputes through structured correction — without blocking independent legal rights where they apply.
We may request additional verification and may reject incomplete or clearly abusive automated requests. Clarity and good faith speed processing.
25. Reverse engineering and unauthorized testing
You may not extract internal scoring logic, bypass protections, or run unauthorized production penetration tests. Unauthorized testing may result in bans.
The ban also covers UI tampering to skip verification, forged request headers, or large-scale proxy rotation to hide abuse.
26. Entire agreement
These Terms, the regional Privacy Policy, and any additional notices shown for a specific flow form the agreement on this subject and supersede prior informal understandings, without overriding non-waivable mandatory rights.
27. Survival
After you stop using the service or access is banned, clauses that by nature should survive remain in effect: disclaimers, liability limits, IP, anti-scraping, indemnity where applicable, and interpretation rules.
28. Practical safety guidance
- Never share OTP codes with callers even if a lookup label looks familiar.
- Do not rely on a single result for a major financial decision.
- Report scams through official channels in addition to the platform if you wish.
- Read your region’s Privacy Policy for statute names and rights.
This guidance does not expand platform warranties; it reduces practical user harm in telecom-fraud contexts.
29. Third-party embeds
Besides Google ads, pages may include embeds or outbound links. Those elements follow third-party policies. Third-party outages or misleading third-party content do not expand our liability beyond mandatory law.
30. Good-faith interpretation
These Terms should be interpreted to protect users from abuse and the platform from abusive claims, without circumventing the express AS-IS, anti-scraping, and anti-defamation clauses.
Shared operational depth section (part of the base template)
This section exists so users are not left with ultra-short legal blurbs. Numbro is a public web platform visited from many countries. We therefore use a shared operational template covering collection, use, cookies, ads, and security, plus a regional addendum that names statutes and abbreviations. That pattern is common among large global platforms: shared principles first, then regional compliance layers.
Lookup is an informational caution tool, not a license to accuse someone. Filing a report is a good-faith allegation pathway. Filing an objection requests review of content that may concern you. Each path has privacy and liability consequences, so Privacy and Terms must be read together.
Functional cookies differ from advertising cookies. Ads may fund a free service; they do not mean we sell your personal data as a product. Google Ads Settings, partner-site disclosures, aboutads.info, and YourOnlineChoices are provided as external controls even if an in-page consent dialog is not currently enabled.
When exercising a data right, clearly state your region/URL, the right requested, and verifiable contact details. Vague or abusive requests slow processing for everyone. We aim to respond within a reasonable operational window subject to legal requirements.
Choosing the correct cluster matters. Opening the GCC page while you need GDPR text is the wrong fit. The hub is designed around clusters with explicit statute names in titles and addenda (PDPL, GDPR, UK GDPR, ePrivacy, CCPA, CPRA).
Human or automated moderation is not a court judgment. Processing delays during peak load or attacks are operationally expected. Limited security-log retention helps protect the platform and other users from repeat abuse, balanced against practical data-minimization.
GCC Addendum — PDPL linkage
Privacy disclosures for this cluster follow the GCC Privacy Policy anchored to Saudi PDPL (SDAIA context). These Terms do not waive non-waivable mandatory rights, but confirm results are informational and prohibit defamation, false reports, and scraping.
Shared operational depth section (part of the base template)
This section exists so users are not left with ultra-short legal blurbs. Numbro is a public web platform visited from many countries. We therefore use a shared operational template covering collection, use, cookies, ads, and security, plus a regional addendum that names statutes and abbreviations. That pattern is common among large global platforms: shared principles first, then regional compliance layers.
Lookup is an informational caution tool, not a license to accuse someone. Filing a report is a good-faith allegation pathway. Filing an objection requests review of content that may concern you. Each path has privacy and liability consequences, so Privacy and Terms must be read together.
Functional cookies differ from advertising cookies. Ads may fund a free service; they do not mean we sell your personal data as a product. Google Ads Settings, partner-site disclosures, aboutads.info, and YourOnlineChoices are provided as external controls even if an in-page consent dialog is not currently enabled.
When exercising a data right, clearly state your region/URL, the right requested, and verifiable contact details. Vague or abusive requests slow processing for everyone. We aim to respond within a reasonable operational window subject to legal requirements.
Choosing the correct cluster matters. Opening the GCC page while you need GDPR text is the wrong fit. The hub is designed around clusters with explicit statute names in titles and addenda (PDPL, GDPR, UK GDPR, ePrivacy, CCPA, CPRA).
Human or automated moderation is not a court judgment. Processing delays during peak load or attacks are operationally expected. Limited security-log retention helps protect the platform and other users from repeat abuse, balanced against practical data-minimization.
19. Financial harm and OTP caution
Common phone scams involve bank impersonation, urgent transfers, or OTP harvesting. Numbro may increase caution through alerts but does not replace official bank channels and does not guarantee that absence of a report means a number is safe. Any financial loss from your decision remains outside platform warranties under the AS-IS clause.
The same applies to medical, legal, or real-estate advice that may appear indirectly in user comments or reports; the platform is not a professional accreditation body. Use independent specialized sources before major decisions.
20. Republishing public results
Seeing a result on the platform is not permission to republish it to shame or threaten someone. Lawful personal review is allowed; weaponizing the platform for public humiliation is not.
Taking screenshots of results about others and posting them with insulting captions is also prohibited. If you must share a result with a competent official body, use their channels and minimize data.
21. Future accounts and APIs
If user accounts or APIs are offered later, they may have additional terms and can be suspended for abuse or automated extraction. Until separate API terms exist, this document remains the general conduct reference.
Any API key or access token issued to you is personal and non-transferable. You are responsible for secrecy. Public leakage is a breach and may cause immediate revocation.
22. Availability
Service may be interrupted for maintenance, vendor outages, attacks, or force majeure. We do not guarantee absolute uptime. Report/objection handling may be delayed during incidents.
We may change UI layout or retire a feature for security or product reasons without that alone constituting a breach, while seeking to keep core lookup/reporting reasonably available.
23. Conflicts of text
If a short UI blurb conflicts with these Terms, the Terms control. If the Privacy Policy conflicts on pure personal-data processing issues, the Privacy Policy controls for that issue, while anti-abuse rules remain in force.
Section headings are for convenience only. “Including” means examples without limitation unless stated otherwise.
24. Number-owner complaints — correct path
If your number appears with information you believe is wrong: (1) use objection/contact with a clear statement, (2) do not threaten staff, (3) do not file retaliatory false reports. We handle serious requests operationally under our rules. This path aims to reduce unnecessary disputes through structured correction — without blocking independent legal rights where they apply.
We may request additional verification and may reject incomplete or clearly abusive automated requests. Clarity and good faith speed processing.
25. Reverse engineering and unauthorized testing
You may not extract internal scoring logic, bypass protections, or run unauthorized production penetration tests. Unauthorized testing may result in bans.
The ban also covers UI tampering to skip verification, forged request headers, or large-scale proxy rotation to hide abuse.
26. Entire agreement
These Terms, the regional Privacy Policy, and any additional notices shown for a specific flow form the agreement on this subject and supersede prior informal understandings, without overriding non-waivable mandatory rights.
27. Survival
After you stop using the service or access is banned, clauses that by nature should survive remain in effect: disclaimers, liability limits, IP, anti-scraping, indemnity where applicable, and interpretation rules.
28. Practical safety guidance
- Never share OTP codes with callers even if a lookup label looks familiar.
- Do not rely on a single result for a major financial decision.
- Report scams through official channels in addition to the platform if you wish.
- Read your region’s Privacy Policy for statute names and rights.
This guidance does not expand platform warranties; it reduces practical user harm in telecom-fraud contexts.
29. Third-party embeds
Besides Google ads, pages may include embeds or outbound links. Those elements follow third-party policies. Third-party outages or misleading third-party content do not expand our liability beyond mandatory law.
30. Good-faith interpretation
These Terms should be interpreted to protect users from abuse and the platform from abusive claims, without circumventing the express AS-IS, anti-scraping, and anti-defamation clauses.