FreeAI

FreeAI

Privacy Policy

Last updated: June 28, 2026

Information we process

FreeAI processes prompts, uploaded files, conversation context, technical request data, and basic usage signals needed to provide and protect the service. Do not submit passwords, payment details, medical records, legal secrets, or other sensitive information unless you are comfortable having it processed by an AI backend.

Conversation logs

FreeAI may store prompts, generated responses, model settings, attachment metadata, account identifiers, and anonymous browser identifiers so we can operate the service, debug failures, prevent abuse, provide support, and improve reliability. If you are signed in, logs may include your account email. If you are not signed in, logs use a random browser cookie instead.

We may hash technical signals such as IP address and browser user agent for abuse prevention and debugging. We do not use IP address as your main identity, and uploaded file bytes are not kept in chat logs.

AI backend processing

Prompts, attachments, and generated responses may be sent to AI model providers and supporting backend services so FreeAI can produce answers, analyze files, debug failures, prevent abuse, and improve service reliability.

Local storage

FreeAI may store interface preferences such as sidebar state in your browser local storage. Signed-in chat history is stored server-side for your account. You can clear local browser data through your browser settings.

Google ads and cookies

We use Google AdSense to show advertisements. Google and other third-party vendors may use cookies or similar technologies to serve ads based on your visits to this and other websites. Google's use of advertising cookies enables Google and its partners to serve personalized ads.

You can opt out of personalized advertising through Google Ads Settings at google.com/settings/ads. You can also learn about broader third-party ad choices at aboutads.info/choices.

Contact and deletion requests

For privacy, data deletion, or ad disclosure questions, contact [email protected]. Include enough detail for us to identify the relevant browser session, request, or account without sending unnecessary sensitive data.