Privacy Policy
Effective October 9, 2026
1. Scope
This Privacy Policy explains how Tribal Verify handles information when people and organizations use TribalVerify.com, requester accounts, Nation staff tools, verification workflows, private document sharing, support, billing, and related services. Separate written agreements with a participating Tribal Nation or enterprise customer may impose stricter requirements. When they do, the stricter controlling agreement governs that relationship.
2. The Tribal Nation remains the citizenship authority
Tribal Verify does not determine who is a citizen or member of a Tribal Nation. A participating Nation remains the authority over its citizenship law, source records, matching rules, staff decisions, approved disclosures, retention requirements, and verification result. Tribal Verify provides the controlled workflow around that authority.
3. Information we may collect
Depending on the use case, Tribal Verify may process legal name, date of birth, a Nation-issued citizenship or member identifier, limited card metadata, citizen authorization, requester organization and user information, Nation staff-account information, billing and payout records, verification results, audit history, support communications, private document-sharing records, device/session information, security logs, and standard server/network records.
4. Sources of information
Information may come from requester organizations, the person being verified, authorized Tribal Nation systems and staff, payment and email providers, account-authentication systems, and technical logs generated when the service is used.
5. How we use information
We use information to authenticate users, obtain and document authorization, route verification requests, apply Nation-approved matching rules, support Nation staff review, deliver results, prevent fraud and misuse, maintain audit records, generate Nation-branded documents, operate requester billing and Nation revenue sharing, provide support, secure the service, comply with contractual obligations, and maintain business records.
6. Minimum disclosure
Tribal Verify is not designed to expose or replicate a Tribal citizenship roll. Requesters receive only the Nation-approved verification result and limited transaction information needed for the authorized purpose. Tribal Verify does not provide requesters with bulk access to Nation records.
7. Data minimization and retention
Full date of birth and full Nation-issued member numbers are treated as sensitive lookup fields. Tribal Verify supports Nation-controlled retention periods. The current default is 30 days unless a participating Nation requires another period. After the configured period, Tribal Verify is designed to remove the stored full date of birth and full member number while preserving the minimum verification and audit record required for accountability. The last four characters of a member number may remain when the Nation permits that limited reference.
8. Verification validity
A verification reflects the Nation-authoritative result at a point in time. The current default document-validity period is 90 days unless the participating Nation configures another period. Public QR validation is designed to confirm the existence and status of a verification record without displaying the citizen's name, date of birth, full member number, or requester organization.
9. Private business-document and presentation sharing
Tribal Verify may allow an authorized platform administrator to share protected business documents or presentations with a named email recipient. The service may record the recipient email, access token hash, claim time, expiration, view count, last-viewed time, revocation status, and browser-bound session information. Protected viewers may use recipient watermarking and interaction deterrents such as disabled printing, saving, copying, dragging, and context menus.
10. Service providers and subprocessors
Tribal Verify uses service providers for application hosting, authentication, database and private storage, payments and payouts, transactional email, source-code/continuous-integration services, DNS/domain services, and related infrastructure. Providers receive only the information reasonably needed to perform their service. Participating Nations may impose additional subprocessor, location, security, audit, and deletion requirements by agreement.
11. Sale, advertising, and public profiles
Tribal Verify does not sell Tribal citizenship information, publish Tribal citizenship rolls, create public citizen profiles, or use Tribal citizenship information for behavioral advertising. Tribal Verify is not a public enrollment search engine.
12. Security
Tribal Verify uses controls that include encrypted network connections, role-based access, two-factor authentication for Nation operations, server-side authorization, audit logging, protected private storage, no-store controls on sensitive routes, and restricted privileged credentials. Real Nation data is not enabled until the Nation-approved integration and security process is complete.
13. Children
Tribal Verify requester and Nation staff accounts are intended for authorized business and governmental users, not children. A verification involving a minor, if a participating Nation and requester lawfully support that use case, must follow the applicable Nation agreement, authorization requirements, and law.
14. Government and legal requests
Tribal Verify evaluates legal demands for information and seeks to disclose only what is lawfully required. Requests affecting a participating Nation's data may also be subject to that Nation's law, agreement, notice requirements, or sovereign interests. Nothing in this Policy waives any Tribal Nation's sovereign immunity or authority.
15. Privacy questions and requests
Citizens, requester users, Nation representatives, and other authorized persons may contact Tribal Verify about access, correction, deletion, retention, account, or privacy concerns. Some records may be controlled by the participating Nation or may need to be retained for fraud prevention, security, accounting, legal hold, or contractual reasons.
16. Changes
We may update this Policy as the service, legal requirements, Nation agreements, or data practices change. Material changes will be posted with a revised effective date and may be communicated through account or contractual channels when appropriate.
Contact Tribal Verify about privacy