Guapifi

Privacy notice

Updated October 14, 2026

Who this covers

This notice describes personal information the Guapifi charge-card application collects to run guapifi.com. It covers organization operators and cardholders. Charge-card records stay in the Postgres schema guap_charge.

Information the application collects

Account and organization records: organization name, operator email, a password hash, role, and active status. API keys are stored as hashes. Branding fields may include a program name, logo URL, and color.

Cardholder records: name, email, phone, date of birth, billing address, terms-acceptance time, and either a password hash or a Supabase auth user id when that sign-in is configured. Credit-builder signup also collects a Social Security number and sends it to Lithic for identity checks when Lithic credentials are set. The cardholder row does not store the Social Security number. If Lithic is not configured, the number is not sent and is not written to the database.

A Guapifi business application also collects the legal business name, phone, website, a short description of the business, an optional NAICS code, the employer identification number, and the control person and beneficial owners (name, email, phone, date of birth, address, and Social Security number or ITIN). When a Lithic sandbox key is set, Guapifi sends those government ids to Lithic for the business identity check. The application stores the last 4 digits only. Full employer identification numbers and Social Security numbers are not written to the database and are not written to audit rows.

Card and money records: issuer tokens, last4, brand, expiry, status, type, and freeze state. The application does not store a full card number or CVC. Ledger entries, authorizations, and transactions may include amounts, timestamps, and merchant details supplied by the issuer. Billing records may include a Stripe customer id, subscription state, deposit state, and statement amounts.

Device and log data: the application logger is configured to redact email, phone, date of birth, card number fields, and cookie headers. The hosting server may keep ordinary connection logs for the site.

Cookie choices: the first-party cookie guap_cookie_consent stores a version, a timestamp, and the category choices. Details are on the cookie policy.

Purposes

The application uses this information to:

  • create and authenticate operator and cardholder sessions;
  • issue and display cards through the configured issuer;
  • run membership billing and funding through Stripe when Stripe is configured;
  • keep the organization ledger, statements, and audit history;
  • verify webhooks and cron calls, and refuse those routes when the required secret is unset;
  • remember cookie choices;
  • prepare credit-furnisher payloads for Bloom when those credentials are set.

The application does not sell personal information. No marketing or analytics vendor is configured.

Processors

The application sends personal information to a processor only when that integration is configured:

  • Lithic, for card issuing and the card-number embed;
  • Stripe, for membership billing, checkout, and funding;
  • Supabase, for cardholder sign-in when Supabase credentials are set. Google sign-in is used only when Google OAuth credentials are also set, and it runs through Supabase;
  • Bloom, for credit furnishing when Bloom credentials are set;
  • Coinbase, for a foreign-exchange quote or trade when that engine is selected;
  • the hosting server that serves guapifi.com, which stores the application and its database.

This notice does not claim a security certification. The repository does not contain a SOC report, a PCI certification, or an insurance certificate.

Retention

This codebase does not run an automatic deletion job for personal information. Account, cardholder, ledger, audit, and webhook rows remain in guap_charge until the operator deletes them or honors a deletion request. Session cookies expire on the schedule in the cookie policy.

Access and deletion

You may ask the operator for access to, or deletion of, the personal information this application holds about you. Use the contact path in the operator block. The operator may keep records it must retain to complete a transaction, secure the service, or meet a legal duty. Deletion of a cardholder does not by itself close a record at Lithic, Stripe, or Bloom.

Children

The program is for people 18 and older. Credit-builder signup rejects a date of birth under 18. The service is not directed to children under 13, and the operator does not knowingly collect their personal information.

Security

Operator and cardholder session cookies are HttpOnly. Passwords stored by this application are hashed with scrypt. When Supabase sign-in is configured, Supabase stores that password. Card numbers render in the issuer’s frame. Logs are configured to redact the fields listed above. No method of transmission or storage is perfectly secure.

International visitors

Visitors outside the operator’s country can reach guapifi.com. Information is processed on the hosting server and by the processors named above when those integrations are configured. This notice does not identify a country of storage or a specific transfer agreement, because the repository does not state one.