DEVZIKKY PAY
Preparing your DEVZIKKY PAY experience
This page describes the main categories of information the application is designed to handle. It is a plain-language product overview, not legal advice or a substitute for any formal privacy notice required for a particular business or jurisdiction.
The application separates private transaction records from public aggregate statistics. It does not intentionally publish customer names, email addresses, notes or administrator credentials.
Where a transaction has been created, the backend may store the customer's name and email, reference, amount, original currency, transaction type, optional note, source, status and timestamps. These records are available only through authenticated administrative routes.
Paystack is the payment processor used by the existing integration. The existing integration supports server-side verification and was designed for secure payment initialization. Payment initialization is handled by the server-side Paystack integration. Do not enter or send card details in a note, email or support message.
Server logs include request IDs, route names, HTTP methods, response statuses, durations and sanitized error messages. Browser reports can include the page path, a resource path, error category and line/column numbers. The error-report endpoint is designed not to receive form bodies, cookies or payment credentials.
After a successful admin login, the server sets an HttpOnly, Secure, SameSite=Lax session cookie. The administrator key is sent only to the same-origin login endpoint and is not added to browser diagnostic report payloads. After a successful login, the form is cleared.
The statistics page is designed to show totals, currency groupings and payment references, not customer names, email addresses or private notes.
Transaction listings and CSV export require a valid administrator session. Do not share the admin key or leave an authenticated session open on a shared device.
The browser reporter caps the number of reports per page and strips query strings and common credential patterns. If the visitor is offline or the reporting endpoint is unavailable, a browser error may not reach Vercel logs.
The backend applies its configured transaction-retention policy during eligible requests. The current project configuration specifies a three-year retention period.
For privacy questions or corrections about this website, contact the developer using the public contact details on the portfolio.