Privacy Policy

This Privacy Policy outlines how Codelucent Technologies, LLC (“Paystack”) processes, tokenizes, isolates, and protects sensitive corporate data, programmatic variables, end-user financial identifiers, and transactional telematics when you interact with our money-movement endpoints or deploy our Model Context Protocol (MCP) packages. This policy applies strictly to our software infrastructure layers and does not govern the independent internal consumer databases maintained by you (“Company”) or the banking perimeter handled directly by Moov.

To orchestrate programmatic money movement across federal banking rails, our system processes specific categories of information via secure API payload vectors:

Corporate Identity & KYB Markers: Legal business names, employer identification numbers (EIN), physical corporate drop-zones, and verified structural registration documentation.

Beneficial Owner & KYC Markers: Legal names, birthdates, social security numbers (SSN) or passports, and physical addresses of directors and high-equity corporate officers.

End-User Account Routing Parameters: Bank account routing numbers, checking/savings account values tokenized via Plaid processor keys, and payment card primary account numbers (PAN).

Telemetry & Agentic Intelligence Logs: System transaction trails, unique auditId logs, automated agent reasoning metadata hashes, network IP pathways, and structural verification logs tied to our Strategy B safety frameworks.

We do not sell, rent, monetize, or distribute financial identity data to third-party ad networks or data brokers. All processing sequences are strictly limited to the execution of primary utility features:

• Passing compliant token arrays to Moov Financial, Inc. to facilitate financial network interactions.
• Validating bank routing accuracy and verifying consumer accounts via Plaid integration keys to proactively prevent fraud.
• Executing the SafetySwitch Strategy B verification algorithm, which analyzes programmatic reasoning logs to ensure an autonomous agent is not executing duplicate or malicious payout commands.
• Generating audit logs, processing transaction exception files, and maintaining compliant ledger-state archives required under SOC 2 and NACHA governance parameters.

Because our software is engineered to operate alongside Model Context Protocol architectures, we enforce absolute data isolation protocols. Our custom MCP tools use strict tokenization boundaries. The raw banking credentials or core account strings of Company, tenants, or lenders are never exposed directly to the LLM (Large Language Model) context window or the agentic reasoning environment. All internal processes use secure, randomized processor_token strings and tracking references (auditId). This ensures that even if an autonomous software agent experiences a reasoning failure or hallucination, the structural privacy and core routing integrity of the underlying banking accounts remain mathematically secure.

Financial identity markers processed through our nodes are shared exclusively with our natively embedded banking platform partner, Moov Financial, Inc., to facilitate lawful execution of the transactions. Moov processes and secures this data in strict compliance with federal bank-secrecy standards, PCI-DSS Level 1 specifications, and the regulatory oversight of their respective sponsor banks. We may disclose data when legally compelled to do so by active federal subpoenas, law enforcement investigations, or direct NACHA network governance audits.

Paystack strictly adheres to core principles of data minimization. Raw credit/debit card tracking data (PAN) or direct checking-account numbers are never written to our permanent database hard drives; they are handled entirely via secure, encrypted transit pipes directly to Moov’s compliant vault architecture. System transaction metadata, audit trails, and auditId reasoning hashes are stored inside AES-256 encrypted server arrays to fulfill legal retention periods mandated under federal financial-compliance rules.

Paystack reserves the right to adjust this Privacy Policy and the underlying Terms of Service programmatically to align with new NACHA network guidelines, shifting FinCEN compliance parameters, or federal transaction-enforcement guidelines. Changes are announced via direct system webhooks and developer-portal updates. Continued utilization of our active API routing keys following a policy update constitutes your operational acceptance of the revised infrastructure framework.

If you have questions about this Privacy Policy or our data practices, contact us at:

Codelucent Technologies, LLC
117 S Lexington St Ste 100
Harrisonville, MO 64701
Email: support@codelucent.com