Privacy Policy

Last updated: 2 June 2026

Artiphik ("we", "our", "us") operates artiphik.com — an AI YouTube agent that plans, designs, writes, and helps you ship videos. This policy explains what data we collect, how we use it, how long we keep it, and the controls you have over it.

1. Who we are

Artiphik is a product built by Rahaman Bin Ujit. For privacy questions or data-deletion requests, contact rahaman@artiphik.com.

2. Data we collect

Account data. Email address, display name, hashed password or OAuth identifier, subscription plan. Stored when you sign up.

Generated content. Titles, thumbnail concepts, critiques, and images you create inside Artiphik, plus the prompts that produced them. Tied to your account so you can re-open past work.

Uploaded face and persona images. When you use features that place a saved persona into a thumbnail (the persona library), you upload one or more photos. We store those images so you can reuse the same person across generations. By uploading, you confirm you either are the person depicted or have explicit consent to use their image for this purpose. We do not use uploaded faces to train any models, and we do not share them with anyone outside the providers strictly required to render your generation.

Studio Chat conversations. When you use Studio Chat — the conversational interface that orchestrates titles, thumbnails, scripts, ideas, and other features — we store the messages you send and the responses we generate so you can re-open past conversations, branch off new requests, and continue work where you left off. Conversation history is tied to your account and remains available until you delete it. You can delete individual conversations at any time from the chat history sidebar.

Workspace and Projects. When you create a project, save items to it (titles, thumbnails, scripts, ideas, notes, research links), or use the publish checklist, we store that project data on your account. Projects are private to you by default and remain until you delete them.

Channel Audit and Video Autopsy results. When you run a Channel Audit or open a per-video Autopsy from your connected channel, we generate a scored analysis (grade, sub-scores, performance benchmarks, qualitative insights) and cache it on your account so you can re-open it without re-running. Cached audits and autopsies are refreshed against live YouTube data periodically.

Support tickets. If you open a support ticket from the in-app Help page, we store the subject, description, any screenshots or files you attach, and the reply thread between you and our team so we can resolve your issue. Tickets are tied to your account and visible to our support team. We retain tickets while your account is active and remove them on account deletion.

Referral data. If you sign up via a referral link, we record which referrer brought you so we can credit their account on a qualifying purchase. The referrer is told that a referral converted; they are not shown your name, email, or activity inside the product.

YouTube channel data (optional). If you connect your YouTube channel via Google OAuth, we access the following via YouTube API Services:

  • Channel ID, channel name, channel thumbnail
  • Video metadata for your uploads (video ID, title, thumbnail URL, published date, description)
  • Public performance metrics for your videos (views, watch time, retention, engagement) via the YouTube Analytics API
  • Caption text for your own videos, fetched only when you explicitly invoke a feature that needs it (e.g. script critique). See "Captions access" below.

We request OAuth scopes only for features you actually use. On initial connect we request the minimum read-only set: youtube.readonly and yt-analytics.readonly. We do not request write access to your channel, and we do not access revenue or monetization data.

Captions access (on-demand): youtube.force-ssl

  • Purpose: read caption tracks so the script-critique feature can grade a video's spoken script.
  • Endpoints called: captions.list and captions.download. These are the only endpoints we call with this scope.
  • Access type: read-only in practice. Although the scope name nominally permits writes, we do not upload, modify, or delete videos, ratings, comments, or captions. Caption read access is the only YouTube Data API endpoint Google exposes behind this scope, which is why it is required.
  • Limited to: videos on your own connected channel.
  • When requested: via a separate consent flow you opt into inside the app when you invoke a feature that needs captions — never at signup.
  • Revocation: the same way as any Google permission, via your Google security settings (link below).

Usage data. Basic request logs (endpoint, timestamp, error codes) used to operate the service and debug issues. No behavioural tracking or ad profiles.

3. How we use your data

  • To provide the features you invoke — generating titles, critiquing thumbnails, producing thumbnail ideas, rendering images, drafting scripts, brainstorming video ideas, and showing your analytics.
  • To power Studio Chat — the conversational interface that routes your natural-language requests to the relevant features and remembers context across messages so the conversation feels continuous.
  • To generate Channel Audit scores and per-video Autopsy analyses for your connected YouTube channel, so you can see which videos worked, which underperformed, and what to fix.
  • To save your work into Projects in the Workspace, so you can organize titles, thumbnails, scripts, ideas, and notes per video and pick up where you left off.
  • To match videos you publish on YouTube to content you generated in Artiphik, so we can show you which titles and thumbnails are performing.
  • To grade the spoken script of a video you ask us to critique, we fetch its captions via the YouTube Data API. Captions are used only to generate the requested critique and are not used for any other purpose.
  • To resolve support tickets you open through the in-app Help page, including reading the description and attachments you share with us and replying back through the same ticket.
  • To improve our internal retrieval system, we use publicly available thumbnails of high-performing videos (not your private data) as design references.
  • To display selected generations on our public Explore gallery. By default, generations made on the Free plan may appear in Explore so other creators can browse community output. You can flip a generation to private at any time from your library, and paid-plan generations are private by default.
  • To communicate with you about your account (billing, security, product updates, and feature launches). Every non-essential email includes a one-click unsubscribe link; billing and security notices are required for the service to function and cannot be unsubscribed from.

We do not sell your data, do not use your YouTube data (including captions) to train or fine-tune machine learning models, and do not share your YouTube data with advertisers.

4. YouTube API Services

Artiphik uses YouTube API Services. By connecting your channel, you also agree to the YouTube Terms of Service and the Google Privacy Policy.

You can revoke Artiphik's access to your YouTube channel at any time from the Google security settings page, or from inside Artiphik by clicking Disconnect on the Analytics page. Revocation stops any further syncs immediately.

5. Google API Services Limited Use

Artiphik's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Specifically:

  • We use Google user data only to provide and improve user-facing features that are prominent in the Artiphik UI (channel analytics, video matching, performance tracking).
  • We do not transfer Google user data to third parties except as necessary to provide or improve those features, to comply with applicable law, or as part of a merger, acquisition, or sale of assets with user notification.
  • We do not use Google user data for serving advertisements, including retargeting, personalised, or interest-based advertising.
  • We do not allow humans to read Google user data unless (a) you give us explicit consent for specific data, (b) it is necessary for security purposes such as investigating abuse, (c) it is required to comply with applicable law, or (d) the data is aggregated and anonymised and used for internal operations.
  • We do not use Google user data to develop, improve, or train generalised machine-learning or AI models.

6. Storage and retention

Data is encrypted in transit with TLS and at rest by our infrastructure providers. Our production infrastructure runs in the Asia-Pacific region.

In line with the YouTube API Services Developer Policies we refresh or delete YouTube-derived data at least every 30 days. Data we fetch via the YouTube API is either refreshed from the live API within this window or removed from our cache.

Captions fetched for script critique are processed at the time of the critique and are not persisted as their own record. Outputs you save are retained on your account so you can re-open past work; deleting an item from your library removes its stored output, and deleting your account removes all of it within 14 days.

Studio Chat conversations are retained on your account until you delete them. Each conversation is private to you and never appears in other users' histories. You can delete individual conversations from the chat history sidebar inside the app.

Workspace projects (titles, thumbnails, scripts, ideas, notes, and any items you saved into a project) are retained until you delete the project, the individual item, or your account.

Channel Audit and Video Autopsy results are cached on your account so re-opens are instant. Cached results are refreshed against the live YouTube API on a rolling basis so the analysis stays current with your channel.

Support tickets, including any attachments you share with us, are retained while your account is active so we can reference prior context if you reach out again. When you delete your account, your tickets and their attachments are removed within 14 days.

Uploaded face and persona images are retained while your account is active so you can reuse them across generations. You can delete an individual persona at any time from the persona library inside the app, which removes the image from our storage. When you delete your account, all uploaded face images are removed within 14 days.

When you disconnect your channel, we retain your historical performance data tied to your account so your past work stays intact, but we stop fetching new data and remove OAuth tokens immediately. When you delete your account, we remove all your data within 14 days, including any cached YouTube data.

7. Your rights and controls

  • Access / export. Email rahaman@artiphik.com and we'll send you a copy of the data we hold on your account within 14 days.
  • Correction. You can edit your profile inside the app, or email us for anything you can't change yourself.
  • Deletion. Disconnect your YouTube channel from the Analytics page, or request full account deletion at rahaman@artiphik.com. We process deletion requests within 14 days.
  • Revoke YouTube access. Use the Google permissions page. Our access ends the moment you revoke it.
  • Explore visibility. Toggle any generation to private from your library. Private generations never appear in Explore.
  • Delete face uploads. Remove individual personas from the persona library inside the app. Deletion removes the image from our storage immediately.
  • Delete chat conversations. Open the chat history sidebar inside Studio Chat and delete individual conversations. Deletion is immediate.
  • Delete projects and saved items. Open Workspace, click into the project, and delete the project or individual items. Deletion is immediate.

8. Categories of third-party service providers

To operate Artiphik we rely on the following categories of third-party service providers, each contractually bound to handle your data in line with this policy:

  • Cloud infrastructure and hosting providers — application hosting, authentication, database, and file storage.
  • AI model providers — third-party generative-AI APIs that produce titles, critiques, thumbnail concepts, and images from the prompts you submit. We contract with these providers under terms that restrict use of your inputs to delivering our service, including no use of your inputs to train their foundation models.
  • YouTube API Services (Data, Analytics, and Reporting APIs) — to fetch your channel data after you explicitly connect via Google OAuth. Governed by the Google Privacy Policy and YouTube Terms of Service.
  • Email and transactional communication providers — to send account notices, billing receipts, and customer support responses.
  • Payment processing. Dodo Payments handles subscription billing as our merchant of record, including tax handling and card processing. Card details are stored with Dodo, not with us.
  • Web analytics providers (Google Analytics 4, PostHog) — to understand how visitors and signed-in users navigate artiphik.com (pages viewed, referral sources, approximate location, device type, feature usage). Google processes its data under the Google Privacy Policy and PostHog processes its data under the PostHog Privacy Policy. IP addresses are anonymised and we do not pass personally identifying information to either provider. You can opt out of Google Analytics using the Google Analytics Opt-out Browser Add-on.
  • Advertising measurement (Meta Pixel & Conversions API) — to measure the performance of our ads on Instagram and Facebook, we use the Meta Pixel and the Conversions API to record when a visitor signs up. We share a hashed (irreversible) version of your email plus standard technical signals (IP address, browser type, ad-click identifiers) with Meta solely for de-duplicated conversion measurement and audience matching. Meta processes this data under the Meta Privacy Policy. You can manage ad personalisation in your Meta account settings.

Enterprise customers can request our current sub-processor list by emailing rahaman@artiphik.com.

9. Cookies and tracking technologies

Artiphik uses cookies and similar technologies for the following purposes:

  • Strictly necessary cookies. Required to operate the service — authenticating your session, remembering you while signed in, and persisting in-progress work between page loads. Without these, the app cannot function.
  • Analytics cookies. Used to understand how visitors and signed-in users navigate the product (pages viewed, referral sources, approximate location, device type, feature usage). We use these to improve the product and prioritize what to build next. They do not identify you to advertisers.

We do not use advertising cookies, retargeting pixels, or cross-site tracking. We do not sell cookie data to third parties. Most browsers let you control cookies through their settings; blocking strictly necessary cookies will break the service.

10. AI-generated content

Titles, critiques, thumbnail concepts, and images produced by Artiphik are generated by AI. Output may contain inaccuracies, biases, or unintended similarities to existing content. Treat it as a starting point and verify before publishing. Where platform policies require disclosure of AI-generated content (for example, YouTube's synthetic-content labelling rules), the obligation to disclose sits with you as the uploader.

11. Children

Artiphik is not intended for users under 13 and we do not knowingly collect data from children. If you believe a child under 13 has signed up, email us and we'll delete the account.

12. Changes to this policy

When we change this policy we update the "Last updated" date above and, for material changes, email every active user before the change takes effect.

13. Contact

Questions, deletion requests, or concerns — email rahaman@artiphik.com.