POVV

Subprocessors

Last updated September 11, 2026 · POVV Kacper Gardocki — sole proprietorship (JDG), Poland · NIP 9151840843

This document is under review by external counsel. It is published so you can see the full supply chain before you send us a repository — not as a compliance claim.

POVV is the data controller. The providers below process data for the purposes listed. They act as processors when processing on our instructions, and may also act as controllers for their own account, legal or regulatory obligations. If we add a provider, we update this page and the Privacy Policy together.

ProcessorPurposeWhat it receivesLocation
AnthropicLanguage-model inference (the technical audit agent)Source-code excerpts and repository metadata submitted for analysisUnited States
xAILanguage-model inference (the adversarial business agent)Source-code excerpts and repository metadata submitted for analysisUnited States
SupabasePrimary database, authentication, storageAccount identity, audit runs, sealed verdicts, encrypted GitHub tokensEuropean Union
GitHubSource of the repositories you ask us to auditRepository reads performed with the access you grant usUnited States
StripePayments, subscriptions, invoicingBilling identity, payment method (held by Stripe, never by us), transaction historyUnited States / European Union
Striptu — FREELANCE Kamil JabłońskiStripe-to-inFakt invoice automationBilling identity, contact and tax details, account and transaction references, line items, amounts, currency, tax and payment statusRegistered in Poland; published terms allow transfers outside the EEA
inFakt Sp. z o.o.Invoice creation, customer invoice emails, KSeF submission and accounting recordsCustomer billing identity, contact and tax details, invoice items and amounts, payment references and accounting recordsRegistered in Poland; published terms allow transfers outside the EEA
VercelApplication hosting and serverless computeAll request traffic in transit, application logsUnited States / European Union
CloudflareDNS, TLS termination, WAF and bot protection at the edgeRequest metadata (IP address, user agent, path) in transitGlobal edge network
UpstashRedis — rate limiting, spend caps, ephemeral audit progressIP-derived rate-limit counters, short-lived run progress messagesEuropean Union
PostHogProduct analytics (currently not enabled in production)Pseudonymous usage events, subject to your cookie choiceEuropean Union

Billing connection

The Striptu connection from Stripe to our existing inFakt account is configured for invoice creation, customer invoice emails and submission to KSeF. Its scope is billing and invoice records; it does not include repository snapshots, GitHub access tokens or verdict contents. See Striptu’s privacy policy and published data-processing agreement, and inFakt’s privacy policy and terms with data-processing provisions.

inFakt’s published data-processing terms permit data in documents entered into its application to be used to train its own AI solutions. Our source-code training statement below concerns repository audits, not financial documents held by accounting providers.

Your code and model training

Source code you submit is sent to Anthropic and xAI for inference, because that is what produces the audit. We do not sell it, publish it, or train any model on it. Both providers are engaged on their commercial API terms, under which content submitted through the API is not used to train their models — a contractual position we rely on, not something we can verify inside their infrastructure.

Separately, POVV uses its own outputs — the verdicts, findings and synthesis the engine generates — in anonymized or aggregated form to improve its services, including a specialist audit model trained on our own hardware. Private-repository verdicts carry hash anchors and never verbatim source, so private code cannot enter that corpus; public-repository verdicts may contain short verified quotes from code that was already public. The full statement is in the Privacy Policy.

Transfers outside the EEA

Several processors are established in the United States. Those transfers rely on the European Commission’s Standard Contractual Clauses and each provider’s own transfer framework commitments. the President of the Personal Data Protection Office (UODO), Warsaw, Poland is our supervisory authority.

Questions

Email [email protected]. Business customers who need a signed data processing agreement should ask — we will provide one.

Subprocessors — POVV · POVV