Trust
Security and vulnerability disclosure
Last updated: November 16, 2026
FunAI is operated by Funsol Technologies. People trust us with their accounts, their creative work and their payments, and we treat the security of that information as a core part of the product. This page describes how we protect the FunAI platform and how security researchers can report a vulnerability to us.
To report a security issue, email [email protected].
Security overview
Infrastructure and network
- All public FunAI services, including funai.art, api.funai.art, mcp.funai.art, developers.funai.art and docs.funai.art, are served over HTTPS. Traffic passes through Cloudflare, which provides TLS termination, DNS and network protection.
- Requests to our backend services pass through a central API gateway. The gateway authenticates requests to protected endpoints, applies security headers and cross-origin rules, and enforces rate limits per API key and per IP address.
- Internal services require service-to-service authentication and cannot be reached from the internet.
- Each backend service keeps its data in a separate database, which limits the impact of any single fault or compromise.
- Billing and credit write requests require an idempotency key, so a retried request is not processed twice.
Accounts and authentication
- Passwords are never stored in plain text. They are stored only as salted bcrypt hashes.
- Two-factor authentication is available on every account. We strongly recommend enabling it.
- Sessions use access tokens that expire after 15 minutes and refresh tokens that are tied to a server-side session. You can sign out of all devices at any time.
- Sign in with Google is supported for users who prefer not to manage a separate password.
API keys and integrations
- API keys are created in the developer portal. We store keys only as one-way hashes. After a key is created, we display only its last four characters, and a key can be revoked at any time.
- Applications that connect to FunAI through our MCP server receive an OAuth grant rather than a password or API key. Each grant is limited in scope, carries a spending cap you choose, and expires after 90 days.
Payments
Card payments are processed by Stripe. Card numbers are entered into Stripe's systems and never reach FunAI servers. We keep only the transaction records needed for billing, tax and accounting.
Data protection
- Generated and uploaded files are served from unguessable URLs. Download links expire after 24 hours. Deleting an item revokes its link.
- Deleted files are kept in a recycle bin for 30 days and then permanently removed.
- Data in transit between your device and FunAI is protected by TLS.
- Our Privacy Policy and Trust Center describe what we collect, how long we keep it and how to request deletion.
Staff access
- Staff access to administrative tools is granted by role and limited to what each role requires.
- Two-factor authentication is mandatory for every staff sign-in to administrative tools.
- Sensitive administrative actions, such as wallet adjustments, refunds and role changes, are authorized centrally and require the staff member to re-authenticate.
- Administrative actions are recorded in an audit log.
Content safety
We use automated content moderation to screen image, video, audio and other media generation requests before they are sent to an AI model and before any credits are reserved. A dedicated safeguard blocks generation requests that seek sexual content involving minors. We do not use your prompts, uploads or generated content to train or fine-tune AI models without your consent. Prompts and attached files are sent to the model provider that runs the model you select. Our Trust Center explains how those providers handle prompts and outputs under their business terms.
Availability, backups and monitoring
- Production databases are backed up daily to storage separate from the production servers. Backups are retained on a rotating schedule of daily, weekly and monthly copies covering approximately six months.
- We monitor platform health continuously. Component status, planned maintenance and incident updates are published on our status page.
Secure development and incident response
- We review our code for security issues and remediate findings according to severity.
- We maintain a documented incident response process with defined severity levels. Service-affecting incidents are communicated on our status page.
- If a security incident affects personal data, we notify affected customers without undue delay, and notify the relevant authorities, as required by applicable law and our agreements with customers.
Your role in keeping your account secure
- Use a unique password for FunAI and enable two-factor authentication.
- Keep API keys out of public code repositories, client-side code and shared documents. If a key may have been exposed, revoke it in the developer portal and create a new one.
- If you believe your account has been accessed without your permission, change your password immediately and contact [email protected].
Vulnerability disclosure policy
We value the work of security researchers and welcome reports of vulnerabilities in FunAI. This policy explains what is in scope, how to report an issue, what we ask of you, and what you can expect from us.
Scope
This policy covers internet-facing systems that FunAI owns and operates, including:
- funai.art and its subdomains, including api.funai.art, mcp.funai.art, developers.funai.art and docs.funai.art
- the FunAI web application, including the creative studio and video editor
- the FunAI API, the FunAI MCP server and the developer portal
Out of scope
The following are not covered by this policy:
- Systems operated by third parties, even where they are connected to FunAI or served under a FunAI domain. This includes our payment processor, email and analytics providers, our content delivery network, and the AI model providers we route requests to. Please report those issues to the relevant vendor.
- Findings from automated scanners without a working proof of concept.
- Missing security headers, cookie flags or other best-practice recommendations without a demonstrated security impact.
- SPF, DKIM or DMARC configuration.
- Self-XSS, logout cross-site request forgery, and clickjacking on pages without sensitive actions.
- Account or email enumeration through rate-limited forms, and missing rate limits on endpoints without a demonstrated impact.
- Denial-of-service attacks, volumetric testing and resource exhaustion.
- Social engineering, phishing and physical attacks against our staff, users, offices or vendors.
- Vulnerabilities that only affect outdated or unsupported browsers and operating systems.
- Vulnerabilities in third-party software that were publicly disclosed less than 30 days before your report.
Content safety and model behavior. Ways to bypass our content moderation or misuse AI models are important to us and may be reported to the same address. Please describe the technique and the prompts involved rather than generating prohibited content. Never attempt to generate sexual content involving minors under any circumstances.
How to report
Email [email protected] and include:
- a description of the vulnerability, its type and your assessment of its severity
- the affected URL, API endpoint, MCP tool or application screen
- step-by-step instructions to reproduce the issue, with a proof of concept where possible
- the potential impact, as you understand it
- any suggested remediation
- the email address or user ID of any test account you used
- any plans you have to publish your findings
- the name or handle you would like credited, if any
Please submit one vulnerability per report, unless several issues must be combined to demonstrate impact. Reports should be written in English. Do not include personal data belonging to other users. If you need to share sensitive technical details in encrypted form, say so in your first message and we will agree a suitable method with you.
Guidelines for researchers
When testing FunAI, you agree to:
- test only against accounts you own or test accounts you created for this purpose
- stop testing and report to us as soon as you have confirmed a vulnerability, and go no further than necessary to demonstrate it
- avoid accessing, modifying, deleting or retaining data that does not belong to you; if you encounter such data, stop, report it to us and delete any copy you hold
- avoid degrading the service for other users, including through high-volume automated testing
- avoid spending credits, balances or payment methods that are not yours, and use paid features only to the extent needed to demonstrate an issue
- keep the details of the vulnerability confidential until it has been resolved and we have agreed on the timing of any disclosure
- not make any demand for payment or other benefit in connection with a report
- comply with all applicable laws
Our commitments
When you report a vulnerability in line with this policy, we will:
- acknowledge your report within three business days
- investigate and validate the issue, and keep you informed of our progress
- prioritize remediation by severity, with the aim of resolving critical vulnerabilities within 30 days of confirmation
- let you know when the issue has been resolved
- work with you on the timing and content of any public disclosure
- credit you publicly for the discovery, if you wish
- not share your identity with third parties without your permission, unless required by law
FunAI does not currently offer monetary rewards for vulnerability reports.
Safe harbor
If you make a good-faith effort to comply with this policy during your security research, we will consider your research to be authorized. We will not initiate or support legal action against you, and we will not report you to law enforcement, for research conducted in accordance with this policy. To the extent your research conflicts with our Terms of Service, including its Acceptable Use section, we waive those restrictions for the limited purpose of research conducted under this policy.
If a third party initiates legal action against you in connection with research conducted in accordance with this policy, we will take reasonable steps to make it known that your research was authorized by us.
This safe harbor applies only to systems within the scope of this policy and does not extend to systems operated by third parties. It does not cover research that causes harm to FunAI, our users or others, accesses or retains personal data beyond what is necessary, or is accompanied by a demand for payment. FunAI decides in its reasonable judgment whether research was conducted in good faith. If you are unsure whether a planned activity is consistent with this policy, contact [email protected] before proceeding.
security.txt
Our security contact details are published in machine-readable form at /.well-known/security.txt, in line with RFC 9116.
Changes to this policy
We may update this policy from time to time. The version published on this page when you submit your report applies to that report.
Other contacts
- Privacy requests and personal data: see our Privacy Policy.
- Copyright notices: see our DMCA policy.
- Security questionnaires and procurement reviews: [email protected]
- Account and billing support: [email protected]