Web Developer
Hello Appwrite Support,
I'm evaluating Appwrite Cloud to host a Patreon OAuth integration, including authentication callbacks, encrypted token storage, membership synchronization, webhooks, and scheduled token refreshes.
Before proceeding, I need clarification about how Appwrite Cloud handles sensitive OAuth callback URL parameters.
Patreon redirects users to an HTTPS GET callback containing code and state query parameters.
Could you please confirm:
Does Appwrite Cloud record the full callback URL, including query parameters, in any provider-controlled ingress, gateway, load-balancer, CDN, security, tracing, error, or infrastructure logs?
If these parameters are recorded, can their collection be disabled or redacted before storage?
Does disabling application/function logging also prevent collection by upstream infrastructure?
What are the retention periods and access controls for any logs that might contain these parameters?
Can Appwrite Cloud support the entire backend—OAuth callbacks, encrypted token storage, webhook processing, scheduled refreshes, and a persistent database—without requiring Cloudflare or another hosting provider?
Does the Free plan have a strict $0 overage limit, or can any usage or attack-related activity result in charges?
Please distinguish documented platform guarantees from application-level logging controls.
Thank you.