1. Accounts and inquiries
Registration involves your email and authentication data. Inquiries may include your name, contact details, company and message. Supabase Auth handles account access, email verification and password recovery.
Your password is submitted to the authentication service. Do not include passwords, access keys or other people's personal data in inquiries, catalogs or messages to the team.
2. Advertiser and publisher data
We process business and website details, advertising materials, catalogs, item prices and links, campaign settings and budgets, placement details and integration information. When you request an import, the server visits the supplied public website or processes your uploaded file.
An approved ad card may display the business name, ad copy, image, price and destination. Changes and delivery depend on review and pilot settings.
3. Context and advertising events
Partner apps supply structured context: category, need, country and optionally city, language, placement, budget and attribute constraints, request and session identifiers, and age, consent and sensitive-context signals. We record delivery decisions, card visibility, clicks, supported conversion events and accounting entries.
Session identifiers support frequency limits, event verification and deduplication. Hashing an identifier does not automatically make it anonymous. The decision API does not require a complete conversation. Partners must minimize context and exclude sensitive personal data.
The partner's main AI service and an advertiser's destination website process data under their own policies. inai.ad does not control their main responses or external websites.
4. Purposes and grounds
Processing supports requested features, inquiries, accounts, import and moderation, contextual selection, reporting, abuse prevention and applicable obligations. The relevant legal basis must apply to each processing activity; where the law requires consent, it must be obtained through the prescribed process.
We do not provide advertisers with account or inquiry data as a contact list. Technical logs may contain an IP address, timestamp, request path, device information, response status and error details; these are not assumed to be anonymous.
5. Providers and international infrastructure
Cloudflare provides hosting and network protection. Supabase provides authentication, database and server functions. Resend is used when the corresponding email channel is configured. Enabled Telegram notifications may share inquiry details with authorized team members. The browser loads Google Fonts and provides ordinary connection information to that provider.
Authorized team members and providers receive access necessary for their task. The current Supabase project is in ap-northeast-2, South Korea; the Resend domain uses eu-west-1, Ireland, for sending, while Resend states that customer data, message content and logs are stored in the United States. Cloudflare uses internationally distributed infrastructure. Applicable law determines transfer grounds and data location requirements; this policy does not certify storage in a particular country.
6. Account messages and newsletters
Email verification, recovery and updates about requested operations support your account. Product newsletters require separate, explicit consent and address verification, with unsubscribe available without signing in. Registration and inquiries do not subscribe you to marketing.
Marketing newsletters are not currently activated. When launched, messages must identify the sender, explain why you receive them and include an unsubscribe link. Open and click tracking are disabled in the current Resend configuration.
7. Browser storage
The browser stores sign-in state, language and form drafts. Infrastructure may use necessary cookies and security mechanisms. The Cookies and browser storage page explains management. New optional advertising or analytics tools require a separate assessment and prior consent where required.
8. Retention and safeguards
Data is kept while needed for accounts, inquiries, campaigns, event verification or applicable obligations. Logs, backups and accounting records may have separate retention under the configured infrastructure. We do not claim automatic deletion after a universal fixed number of days.
Safeguards include access controls, server-side secrets and secure connections. After account closure, some records may remain where required for accounting, security or disputes; the applicable basis and scope are considered separately.
9. Requests and rights
Email team@inai.ad to request information, access, correction or deletion, withdraw consent, or object where applicable law provides that right. Identify the account or inquiry involved. We may verify account ownership to protect your data, without asking for your password.
Requests are handled within applicable statutory periods. Withdrawing consent may affect features needing the relevant data. For a partner's main AI application, also contact its owner.
10. Changes
The revision date appears above. Material expansion of processing purposes or data categories requires updated information and renewed consent where required. Editing this text does not itself replace that consent.