Terms and Conditions

Terms for using RequestMaster as an Android HTTP client.

Last updated: 21/08/2026
By installing or using RequestMaster, you accept these terms. If you disagree, do not use the application.

1. Service

RequestMaster lets you build, send, and inspect HTTP requests from Android. Features may evolve through new releases.

2. Authorized use

Send requests only to APIs, servers, and services you own or are sufficiently authorized to access.

You must follow applicable law, destination service terms, usage limits, and relevant confidentiality obligations.

3. Credentials and content

You are responsible for protecting tokens, API keys, passwords, cookies, headers, and data included in requests.

Always verify the URL, method, and body before sending an operation that may create, modify, or delete information.

4. External services

Responses, availability, security, and data handling depend on the destination endpoint. CHC Ideas does not control those external services.

Using an API may incur charges, quotas, or blocks defined by its provider; review them before repeated testing.

5. Account, plans, and purchases

RequestMaster 0.1.0 works without an account, ads, subscriptions, or in-app purchases. If this changes, the terms and policy will be updated before the new processing applies.

6. Availability and compatibility

We do not guarantee compatibility with every endpoint, authentication scheme, certificate, format, or network configuration.

The app does not replace a security audit or guarantee that an API is secure, correct, or production-ready.

7. Intellectual property

RequestMaster, its code, design, and brand belong to their respective owners. Data, APIs, and responses remain owned by their applicable owners.

8. Prohibited conduct

You may not use the app for unauthorized access, bypassing controls, service abuse, malware distribution, rights infringement, or interference with third-party infrastructure.

9. Liability

To the extent permitted by law, CHC Ideas is not liable for losses arising from requests, credentials, data, endpoints, or decisions configured by the user. Keep backups and use test environments.

10. Changes and contact

The current version is published here. For questions, write to chcideas.support@gmail.com.