⚠️ Notice on current implementation status:
- Published posts (title, body, images, author display name) are actually stored in our server database (Firestore).
- We support three sign-in methods: (1) Firebase Anonymous authentication, (2) email/password sign-up, and (3) linking a Google account. When you sign up with email/password, Firebase sends a verification link email, and your password is encrypted and stored by Firebase Authentication — the company (AdEngine-X) cannot view it in plain text.
- The creator ad-revenue-share (payout) feature is currently under policy and operational review and is not available. Payout requests submitted in the past (including PayPal email and bank account details) are not deleted and remain stored on our servers (Firestore); our staff review and process them manually, in order. Credit purchases are processed directly by our payment processor (Toss Payments) — we never store your card number or other payment credentials on our servers. We only store the order ID, payment amount, number of credits purchased, and payment status.
1. Personal Information We Collect
Information AdEngine-X currently actually collects and processes includes:
- Account identifier (Firebase UID): used to link published posts to your account.
- Email address: stored by Firebase Authentication when you sign up or sign in with email/password or a Google account, used only for login verification and identity confirmation on the account settings screen (e.g., password changes).
- Nickname (optional): can be set on the account settings screen; once set, it can be shown as your author display name instead of your email address on published posts.
- Phone number (optional): can be freely entered as text on the account settings screen (not verified via SMS) and is stored on our server (Firestore) as reference information.
- Author display name, and the title, body, and attached images of published posts: stored on our server (Firestore) when a post is published.
- IP address: used only for temporary in-memory counting for spam and rate-limit prevention; never stored in a database.
The following fields, when entered on the payout request screen, are stored on our servers (Firestore) and used to review and process your request (manual transfer by our staff): PayPal email address, receiving bank account number and account holder name. This is not connected to any automated payment or transfer system — actual transfers are handled manually after our staff reviews the request.
3. Global Privacy Compliance (GDPR & CCPA)
Users may request deletion of their own published posts at any time (via the delete button in the post list), which removes the corresponding post data stored in Firestore. If you wish to have your account information — such as your email address, nickname, or phone number — deleted or disclosed, please contact us using the email address you registered with, and we will review and process your request. You may likewise request access to or deletion of the usage records described in Sections 5–7 below. Should real-name registration or payment features be added in the future, this policy will be updated accordingly.
4. Third-Party Advertising (Google) and Cookies
This site may use Google AdSense to display advertisements. Third-party vendors, including Google, may use cookies, web beacons, and IP addresses to serve ads based on a user's visits to this site and other websites, and to measure ad performance. Users can manage or opt out of personalized advertising via Google's ad settings, linked below. For information on how Google uses data collected from partner sites, see Google's partner sites data usage policy, also linked below.
5. Collection of Service Usage Records (Access & Usage Statistics)
AdEngine-X collects and analyzes the following usage records to improve service quality, respond to errors, prevent abuse, and manage per-feature operating costs.
What we collect:
- Access timestamps, session identifiers (randomly generated values), and visited page paths
- Actual active time (usage time measured only while the screen is visible and you are interacting with it)
- Classified referral information (e.g., search engine name, social network name, campaign name, referring domain — full URLs and raw search queries are never stored)
- Type of feature used, execution counts, success/failure, and processing time (e.g., daily-life tool runs, AI article/image generation counts, external public-data lookups)
- Estimated costs of AI and external API usage (for operating cost management)
- Browser language and device type (mobile/PC level only)
What we do NOT collect (prohibited from storage):
- Directly identifying information such as email address, name, or phone number (never included in analytics records)
- Full IP addresses (not stored, except for temporary in-memory processing for spam prevention)
- Full URLs of referring pages or URL query strings (including raw search queries)
- Login tokens and passwords
- Raw text of prompts entered into AI features, and raw search queries
- Copies of article or comment bodies
Separation of accounts and analytics records: our analytics storage does not store your account identifier (UID) directly; instead, we use a separate analytics identifier derived on the server via one-way encryption (HMAC). In admin screens, personally identifying information (such as email addresses) is masked by default.