Contact FastDrop

Tell us what happened.

Email privacy@fastdrop.dev for account, listing, billing, technical integration, or privacy questions. One public address keeps the request connected to the relevant account or product context without requiring a separate support portal. Do not send API keys, webhook secrets, passwords, card details, or private MCP credentials in email.

What to include

Account, billing, or access

Send from the email associated with the account when possible. Include the affected page, an order or transaction reference when relevant, and a description of the expected and observed result. Never include full payment-card data.

Listing or moderation

Include the FastDrop product URL or slug, the submission state you see, and the specific metadata or review decision you are asking about. A public product URL is more useful than a screenshot alone.

Developer integration

Name the interface, HTTP method, timestamp, status code, and JSON-RPC error code where one exists. Share a minimal redacted request and response, but replace bearer tokens and webhook signatures before sending.

Privacy or data rights

State the account or submission concerned and the action you are requesting. FastDrop may need enough context to verify that a request relates to you before acting on account or personal data.

Developer resources before you write

The Developer Portal explains anonymous reads, API keys, OAuth discovery, curl requests, and error shapes. The OpenAPI specification is the source for endpoint-specific request and response schemas, while the MCP manifest identifies the Streamable HTTP endpoint. Signed-in makers can manage credentials and webhooks at developer settings.

Response context

Requests are reviewed in the context of their category, available account evidence, and the information supplied. A billing question, moderation appeal, protocol report, and privacy request can require different checks, so a fixed response time or support SLA is not published. Clear reproduction steps and stable identifiers help distinguish a product issue from an account-specific one. Email is for support communication; it is not a place to send live secrets or an emergency channel.

Postal business and controller details

Gabriele Ferracuti

Via Svarchi

63824 Altidona (FM), Italy

VAT IT02023040443

These are the same controller details published in the Privacy Policy. Email is the practical first contact for routing a request with technical or account context.