- AGDor Pay may store the email address, name, avatar URL, and identity identifiers returned by the configured OAuth provider.
- Session records are stored to keep the authenticated area available and secure.
privacy policy
Privacy Policy
This page describes how AGDor Pay handles account data, project settings, payment records, and technical logs in the current early-access stage.
- The service stores project configuration, webhook endpoints, wallet labels, payment route metadata, and related operational settings entered by the account owner.
- Sensitive credentials are stored with the protection methods available in the current deployment configuration.
- Invoice records, transaction matches, webhook events, provider request logs, and audit records may be stored for service operation, troubleshooting, and abuse prevention.
- AGDor Pay uses these records to keep payment confirmation, retry logic, and dashboard visibility working correctly.
- AGDor Pay does not describe itself as the holder of client balances inside the platform.
- The configured merchant wallet remains the final payment destination controlled by the project owner.
- Session cookies and technical safeguards may be used to protect authentication, CSRF validation, and account access.
- Operational logs may contain technical metadata required for debugging and service protection.
- This policy may be updated as the product grows, adds more routes, or changes the supported infrastructure.