Workspace access
Requests pass through the Philos server. Workspace membership and role govern access; a visible button is not the authority to change a record.
Security and data
Understand the boundaries. Keep control.
Clear access rules and inspectable records are part of operating a partner program. This page describes the product’s approach, without claiming a security certification.
Private credentials
Use secure settings for integration secrets and agent keys. Do not place them in program content, support email, or a public URL. Revoke agent access when it is no longer needed.
Payment authority
Merchant rewards, payment proposals, and payment evidence remain distinct. Review the exact recipient, amount, and effect before a consequential action.
Report a concern
Contact hello@getphilos.ai with a short description and safe reproduction steps. Please do not include passwords, signing secrets, complete payment details, or other users’ personal information in the first message.
If you suspect a compromised key, revoke it from Developer access. If you suspect a payment problem, preserve the record and provider references, stop repeating the command, and contact support.
Data and subprocessors
The privacy policy describes the data categories, service providers, and request process. AI-assisted drafts and analysis should be reviewed before use. AI observation services are not currently offered. Transaction attribution comes from referral links, codes and signed purchase events.
What this page does not promise
No certification, penetration-test result, or contractual uptime guarantee is implied here. Requirements for a security review, custom agreement, or data-processing terms should be established before activation.