Developer and API Terms
Published: 8 October 2026 · Operator: Frica LLC · Contact: [email protected]
Application registration
Developers must accurately register their application, authorized redirect URIs, permitted web origins, privacy policy and requested scopes. Frica may review and reject unsafe or misleading applications.
OAuth security
Public applications must use Authorization Code with PKCE. Confidential client secrets must remain on secure servers and must not be embedded in mobile apps or browser code. Protect access and refresh tokens, use HTTPS and validate authorization responses.
User data and permissions
Request the minimum necessary scopes, explain their use, respect consent and revocation, and avoid unauthorized sharing, resale or retention of user information. Your application must maintain its own appropriate privacy notice and user support.
Reliability and abuse
Do not bypass rate limits, probe systems without authorization, automate abusive requests or interfere with other developers. Report suspected compromise promptly to [email protected].
Enforcement and termination
Frica may suspend credentials, reject integrations or terminate developer access for security threats, legal requirements or material violations. Commercial API terms and service guarantees apply only where separately agreed in writing.