[Storika](https://www.storika.ai/)Privacy policy

# Storika Privacy Policy

Effective Date: July 4, 2026

Last Updated: November 19, 2026

This Privacy Policy applies to the Storika platform operated by Storika, Inc. and is published at https://www.storika.ai/privacy. It covers the Storika brand application (app.storika.ai), the Storika creator application (app.storika.ai/creator), and the Storika marketing website (www.storika.ai), together with related APIs, subdomains, and services.

## 1\. Introduction

Storika, Inc. ("Storika," "we," "us," or "our") is an AI-powered creator-marketing technology provider that enables direct-to-consumer and enterprise brands to discover, evaluate, and collaborate with micro- and nano-influencers. Through proprietary semantic search, ontology-based video analysis, and machine-learning models, Storika analyzes creator profiles, content patterns, and audience signals to support creator discovery, brand and campaign setup, and roster enrollment (collectively, the "Service").

This Privacy Policy ("Policy") describes how we collect, use, disclose, and protect personal information of the brands and agencies that use our Service ("Clients"), the creators who connect their accounts to participate in campaigns ("Creators"), public social-media creators whose publicly available data we ingest for discovery, visitors to our websites, TikTok Shop sellers and end-customers whose information we process through partner integrations, and other individuals whose information we process. By accessing or using the Service, you acknowledge that you have read and understood this Policy.

Current product scope covers creator discovery, brand and campaign setup, and roster enrollment. Shipment tracking and post monitoring are retired, while creator-side and payout code is held; descriptions of legacy data processing do not promise those features today. Storika is committed to protecting personal information and complying with applicable data-protection laws, including the California Consumer Privacy Act as amended by the California Privacy Rights Act ("CCPA/CPRA") where applicable, the EU General Data Protection Regulation ("GDPR"), the UK GDPR and Data Protection Act 2018 ("UK GDPR"), and other applicable privacy laws, as well as the platform terms of the partners whose APIs we use, including TikTok and Meta.

## 2\. Scope and the Individuals we Process Data about

Storika processes four categories of individuals:

Registered Clients: Corporate administrators, marketing managers, and agency partners who create accounts to manage campaigns, issue briefs, and view analytics.

Registered Creators: Individuals who intentionally register and connect their social-media or payout accounts (for example, via OAuth authentication or Stripe Connect) and opt in to participate in campaigns.

Public Social-Media Creators: Creators who have not registered an account with Storika but whose publicly available profile data, public content, and public performance metrics are ingested, processed, and indexed by Storika's discovery and video-intelligence engines for brand-discovery purposes.

Partner Platform Sellers and End-Customers: Where Storika is authorized to operate through partner integrations such as the TikTok Shop Open API, we may process seller, shop, order, contact, fulfillment, campaign, and related end-customer information only as necessary to provide the authorized partner-app functionality, support seller requests, comply with platform requirements, and maintain security.

We also collect standard telemetry, cookies, and device metadata from visitors to our public websites, landing pages, and marketing pages.

## 3\. Information we Collect

"Personal Information" means information that identifies, relates to, or could reasonably be linked with a particular individual or household.

Information You Provide Directly

Clients: When a Client registers or transacts, we collect information such as name, business email address, company name, phone number, account credentials, and billing metadata. To facilitate onboarding and automatically set up and personalize your workspace, we may also collect publicly available information from your company's public website (such as company descriptions, logos, and public brand assets) associated with your email domain or registration. Client billing is handled through subscription and usage-based token charges processed by our payment processor; we do not store full payment-card or bank-account details on our own servers.

Creators: When a Creator registers and connects an account, legacy creator accounts may retain information previously collected for onboarding and payments, including name, social-media handle, contact information, and account-authentication data. Creator payment details, identity-verification (KYC), and tax information are collected and held directly by Stripe through Stripe Connect (Standard) and are not stored by Storika. For paid-campaign payouts, the Creator is the merchant of record; Storika does not hold or take custody of campaign funds. Current product scope does not include outreach sequences, contract execution, creator payouts, general campaign shipment tracking, post monitoring or campaign reporting.

Information We Collect From Connected Platforms

When a Creator authorizes a connection, or when we operate on behalf of a Client, we access information through partner application programming interfaces, including TikTok for Business, the TikTok Shop Open API, the Instagram/Meta Graph API, YouTube API Services, and other Google APIs where connected. We request only the minimum API scopes necessary to provide the Service and minimize sensitive scopes wherever possible. Information received may include profile data, content and creative assets, campaign and order interactions, shop or seller information, order and contact information where authorized, fulfillment or commerce-related metadata, and delivery or performance metrics. If you connect a YouTube or Google account, or if the Service uses YouTube API Services or other Google APIs with your authorization, Storika’s use of Google API data follows the Limited Use statement under "Google user data" below. Your use of YouTube API Services is also subject to the YouTube Terms of Service (https://www.youtube.com/t/terms), and Google’s processing of information is described in the Google Privacy Policy (https://policies.google.com/privacy). You may revoke Storika’s access to Google or YouTube data through Google’s security settings at https://security.google.com/settings/security/permissions where applicable.

Google user data

Google Analytics 4. When you connect Google Analytics 4, Storika reads the names and ids of the Google Analytics 4 properties the connected Google account can read, and the sessions, total users and key events for a date range, so the brand's team sees its site traffic next to its creator campaigns. Storika stores the Google account id and email address, the granted scopes and the encrypted tokens. It does not store the report totals. Disconnecting Google Analytics on its card in Settings deletes the tokens at once. You can also revoke Storika's access at any time at https://myaccount.google.com/permissions.

Google Ads. When you connect Google Ads, Storika reads the id, name, currency, manager-account flag and time zone of each Google Ads account the connected Google account can reach, and the cost, impressions, clicks and conversions for a date range, so the brand's team sees its ad results next to its creator campaigns. Storika stores the Google account id and email address, the granted scopes and the encrypted tokens. It does not store the report totals. Disconnecting Google Ads deletes the tokens, and Storika also revokes the grant at Google when no other Storika connection uses it.

Google Sheets. When an admin connects Google Sheets, Storika reads the cells of only the tabs the admin picks in Google's file picker: a creator list (handle, platform, followers, email and notes) or an inventory list. Storika uses them to add creators from the brand's list to a campaign, to read stock, and to export the roster and results. Storika stores the Google account id and email address, the granted scopes, the encrypted tokens and, for each picked tab its spreadsheet id, tab id, title and a hash of its cells, plus the creator rows the admin chose to import. Disconnecting Google Sheets deletes the tokens.

How Storika handles Google user data. Storika sends the report totals it reads only to the AI assistant that the brand's own user connected to Storika, and only at that user's request. Storika does not sell Google user data or use it for advertising. Storika does not use Google user data to train AI models; the model training described in Section 4 does not apply to it. Storika stores Google user data in its production database on Google Cloud in the United States (us-west1). Storika'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 (https://developers.google.com/terms/api-services-user-data-policy).

Publicly Available Creator Data

For brand-discovery purposes, Storika ingests publicly available creator profile data, public content, and public performance metrics from third-party social platforms, including through third-party data-ingestion tools such as Apify. This information is held in a discovery index that is logically segregated from registered-account data. Storika may apply semantic matching, ontology-based video analysis, machine-learning scoring, and other profiling to this public creator data for discovery and campaign-matching purposes. Public Social-Media Creators may request removal from the discovery index or object to profiling by contacting privacy@storika.ai.

Information We Collect Automatically

When you use our websites or Service, we automatically collect IP address, device and browser information, server logs (user agent, timestamps), product-usage events, error diagnostics, and identity/contact data via tracking partners. We use web-based registration forms, Google single sign-on, persistent and session cookies (including for authentication and CSRF protection), product-analytics SDKs (PostHog), and error-monitoring SDKs (Sentry/Bugsnag). Required cookies are essential to operation; performance and functionality cookies are loaded subject to consent where required. Storika may also use advertising technologies from Meta, TikTok and Google to measure and improve its own ads, only as described under "Advertising and measurement" below, and uses visitor-identification technology as described next. When you visit or log in to our website while advertising is allowed in your browser, cookies and similar technologies may be used by our visitor-identification partner, RB2B (Retention.com), and other online data partners or vendors to associate these activities with other personal information they or others have about you, including by association with your email. We (or service providers on our behalf) may then send communications and marketing to these email addresses. You may opt out of receiving this advertising by visiting https://app.retention.com/optout.

Cookieless visit counting: Before you answer the cookie banner on www.storika.ai, and after you decline, we count page views without cookies, based on our legitimate interest in measuring visits to our website. Nothing is stored on your device for this, no profile is created, and we do not fingerprint your device: our product-analytics provider, PostHog, derives a daily anonymous ID on its servers and does not store your IP address or a location for these page views. We keep these page-view events for no more than 24 months; counts aggregated with no event-level data may be kept longer. You can object at any time with the control below, which stops the count in this browser and also declines analytics cookies, by storing only your cookie choice; a browser that sends Global Privacy Control or Do Not Track is not counted.

Purchase and subscription analytics. When a workspace buys, renews, changes, cancels, refunds or disputes a paid plan, we record that event in our product analytics (PostHog) on the profile of the member who paid at checkout, so we can see which channels and product use lead to paid plans and renewals. We do this on the basis of our legitimate interest in running and improving our paid service. We keep these events for at most 13 months. You can object at any time by writing to privacy@storika.ai; we then stop recording these events for you and delete the ones we hold.

AI connector activity and account profile. When you use Storika through an AI app, we record each request your AI app sends to Storika: the tool it used, what the request asked for (for example your search text, campaign details, budgets and the creators named), how the request ended and why, and the AI app and its version when the app states them. We leave out passwords, access tokens and other credentials, payment data, one-time approval codes, and the text of messages and invites you send to creators, and we mask creators' email addresses and phone numbers. We group your requests into sessions, and we add your name, email address, workspace name, account type, plan, how you signed up and your sign-up date to your profile in our product analytics (PostHog). Storika team members see this activity, your search text included, in an internal channel on Slack, and an AI agent that runs on Anthropic's models reads it with read-only access, so we can support you and improve the product; your email address is masked in what they see. We do this on the basis of our legitimate interest in supporting our customers and improving our service. We keep these records for at most 13 months. You can object at any time by writing to privacy@storika.ai; we then stop recording this activity for you, stop showing it to the team, and delete your profile and its events in our product analytics.

Sign-up and workspace analytics. Our servers record account and workspace creation on your PostHog profile. This applies on the web and through AI apps. The records include sign-up method and workspace creation path. We use them to follow account cohorts into later use and payment and identify workspace creators. Our legitimate interest is measuring activation and attribution to improve the service. Recording continues whatever your analytics cookie choice. We keep these events for at most 13 months. You can object by writing to privacy@storika.ai. We then stop recording for you and delete your profile and its events.

Sign-up source cookies. When you open a Storika sign-up or sign-in link that carries a campaign tag (for example an ad link) or that an AI app opened, and you have accepted analytics, the app stores a first-party cookie whose name starts with \_\_Host-storika.signup-carry in your browser, one for each such visit. Each holds only that link's campaign tags (source, medium, campaign, term and content, or a mark for an AI app), the address of the site that sent you, the app page you landed on and the time you first arrived. It holds no email address, name or account number. It lasts up to seven days from that visit, or one hour when it holds only the AI-app mark. If you create a Storika account in that time, Storika saves the values of your earliest visit once on the new account to learn which campaigns bring new customers. Only Storika receives them. If you decline analytics, the app deletes these cookies. You can also delete them at any time by clearing this site's cookies and storage in your browser.

Analytics choice cookie. The app keeps your answer to the analytics question, accepted or declined, in a first-party cookie named \_\_Host-storika.analytics-choice for up to eight days, so open Storika tabs and the sign-up step follow a decline. It holds only that answer and is used for nothing else.

The model call record. To diagnose wrong, failed or slow model calls, our servers record API model calls in our product analytics (PostHog) on the signed-in user's profile with the workspace: the model and provider, tokens and cost, latency and status, and internal feature and trace ids. The brief embedding call sends no record. A scheduled search's calls are recorded on the profile of the user who created that search, with the campaign's workspace; without that user, no record is sent. The AI app's own conversation is never collected, and Python model calls are outside this record. For the calls our policy permits, the record also includes cleaned prompt and answer text, at most 32,768 UTF-8 bytes each. We leave out chat threads, comments on creators' posts, creator messages (including answers that draft them), and open-web excerpts; a call that cannot separate this content sends neither text. A safety read sends its prompt only. We mask email addresses, phone numbers, secrets, access tokens, credentials, payment data and approval references, and replace separately supplied creator ids and handles with placeholders without keeping the mapping. Names, handles or addresses within a bio or caption can remain, so the text can contain creators' personal data. Authorised staff engineers may read the text to diagnose a call; the analysis agent does not. We do this whatever your analytics cookie choice, on the basis of our legitimate interest in diagnosing calls for workspace members. Our analytics provider removes prompt and answer text after 30 days through its own deletion process, according to its documentation; this removal has not yet been verified on our project. We keep the other fields, which contain no creator data or text, for at most 13 months. This separate text copy can outlast the creator's profile retention period by up to 30 days. After a creator's erasure request, no new record includes that creator's data, and support deletes copies it can find; the 30-day limit is not a verified erasure. Until the remaining text is deleted or reaches its 30-day limit, no post, report or agent reply quotes that creator's handle. We send no record for an objector, a Storika team or QA account, an account of unknown kind, or a call with no resolved user. You can object by writing to privacy@storika.ai; we then stop recording for you and delete your profile and its events.

Browser errors and session replay. We send browser errors to PostHog, linked to the session replay, only after you accept analytics in the app and only once replay masks creator-profile and contact text on screen. Errors carry the error class, cleaned message and stack, release, route template, internal user and workspace ids, and session and replay ids. We leave out IP addresses, requests, breadcrumbs and network bodies, and mask email addresses, phone numbers, secrets and tokens. Pages that exclude analytics, including creator pages, send no errors. Consented Storika team and QA sessions are included and marked by account kind. We keep browser errors for at most 13 months. The app also records a session replay (session recording) only after you accept analytics in the app, masking every typed input and elements marked for masking. Other on-screen text, including creator-profile and contact text, is recorded as shown. We keep session recordings for 90 days. You can decline or withdraw analytics consent in the app's cookie banner at any time; this stops browser errors and session recording. These flows follow your analytics choice rather than the server-analytics objector list.

API log lines. To diagnose API failures, we send cleaned API warning and error log lines, including 4xx responses, to PostHog Logs. They carry log level, message, context, request and trace ids, a stack when present, and the call's person and workspace ids. We clean the already-redacted lines again, mask email addresses, phone numbers, secrets and tokens, and use a route template instead of the request path. We leave out request bodies, vendor response bodies and fetched addresses; a model-answer parse error carries only its class. Connector argument labels keep their existing exclusions, masks and size limits. A line that cannot be cleaned is not sent. We exclude calls attributed to objectors, Storika team or QA accounts, or accounts of unknown kind. A scheduled search uses its creator and workspace for this check and sends no line without a creator; other lines without a user carry no person. We do this whatever your analytics cookie choice, on the basis of our legitimate interest in diagnosing API failures. We keep these lines for 14 days. You can object by writing to privacy@storika.ai; we then stop recording these lines for you and delete the records we hold for you through the same support process as the other identified server analytics.

Discovery fan-out progress. Our servers record the start and finish of a creator-discovery run on the PostHog profile of the member whose run it is, with the workspace, the campaign, the run id, the operation name and the outcome. Our legitimate interest is operating that run without storing this progress in our database. Recording does not depend on the analytics cookie. We keep these events for at most 13 months. You can object at privacy@storika.ai. We then stop recording for you and delete your profile and its events.

Advertising and measurement. Storika advertises its own service on Meta (Facebook and Instagram), TikTok and Google (Google Ads). Where we place these platforms' advertising tags on our website, and only while advertising is allowed in your browser (see "Your advertising choices" below), our website shares data about your visit with them so that we can measure which of our ads bring visitors, sign-ups and first product connections, show our ads to people who have visited our website, and improve how our ads are delivered. Meta, TikTok and Google then receive this data and use it under their own terms and privacy policies (https://www.facebook.com/privacy/policy, https://www.tiktok.com/legal/privacy-policy, https://policies.google.com/privacy). Our Korean affiliate, which operates some of these advertising accounts, receives the same advertising reports. The same advertising choice governs the RB2B (Retention.com) visitor identification described above: our website loads it only while advertising is allowed in your browser.

What these tags share: the address of the page you visit and of the page before it, the time of the visit, your browser's network IP address, browser and device information (such as the browser type, language and screen size), the identifiers these platforms keep in cookies on storika.ai (Meta's \_fbp and \_fbc, TikTok's \_ttp and Google's \_gcl\_au), and the click identifier an ad link carries (fbclid, ttclid or gclid). If we also report a sign-up for Storika or your first product connection to the platform whose ad you clicked, and only while advertising is allowed, that report carries only the click identifier and a one-way hashed Storika account number, never your name. We never send your email address, raw or hashed, to an advertising platform.

How long it is kept: the platform cookies on storika.ai expire after at most 13 months (Meta's and Google's after 90 days, TikTok's after 13 months). If we keep a click identifier with your account for such a report, we keep it only as long as we need it to report your sign-up and first product connection, and never longer than the account. Each platform keeps the data it receives under its own terms. Before any platform's tag runs on our website, Storika accepts that platform's data processing terms for this measurement.

Where it goes: Meta, TikTok and Google process this data in the United States and in other countries where they or their service providers operate. Where the law requires it, these transfers rely on the Standard Contractual Clauses or another lawful transfer mechanism in each platform's data processing terms.

Your advertising choices: advertising and analytics are separate choices in our cookie banner, asked and stored separately. In the European Economic Area, the United Kingdom, Switzerland, South Korea, and any region we cannot identify, advertising stays off unless you allow it. In the United States, advertising may run once you have been shown the cookie banner, unless you turn it off. Wherever you are, advertising stays off in a browser that sends Global Privacy Control or Do Not Track. You can withdraw at any time with the control below, which every page footer links to as "Do Not Sell or Share My Personal Information", or in Cookie settings. Withdrawing stops our website from sending data to these platforms from then on; to delete data already shared, ask the platform, or write to privacy@storika.ai and we will pass the request on. Under some U.S. state privacy laws this sharing can count as a "sale" or "sharing" of personal information for cross-context behavioral advertising; this control is how you opt out of it.

Do Not Sell or Share My Personal Information

## 4\. How we Use your Information

We use Personal Information to:

Deliver and operate the Service, including creator discovery, brand-creator matching, campaign brief generation, workflow execution, TikTok Shop and other partner-platform workflows, seller support, and performance reporting;

Manage accounts, authenticate users, and provide customer support;

Process Client billing, including subscriptions and usage-based tokens, and remit Creator payouts through our payment processor;

Train, validate, and refine our proprietary AI/ML models for creator matching, content analysis, and campaign-performance prediction, using aggregated, anonymized, or de-identified data where feasible and excluding payment-card, banking, KYC, and tax data held by payment processors. Storika does not use TikTok Shop U.S. seller, order, contact, fulfillment, or end-customer data to train AI/ML models except where expressly permitted and only in aggregated, anonymized, or de-identified form;

Generate aggregated analytics and benchmark reports;

Send transactional communications and, for Client and agency users, direct marketing (with opt-out available);

Detect fraud, monitor security, and prevent abuse; and

Comply with legal, regulatory, tax, and accounting obligations.

## 5\. How we Share your Information

We do not sell your Personal Information for money, and we do not purchase personal data from data brokers. When advertising is allowed in your browser, our website may share visit data with Meta, TikTok and Google, and with our visitor-identification partner, as described in Section 3; some U.S. state laws treat this as a "sale" or "sharing" for cross-context behavioral advertising, and you can opt out of it at any time with the "Do Not Sell or Share My Personal Information" control. We share Personal Information only as follows:

Service Providers / Sub-Processors: We share data with vetted vendors who process it on our behalf under Data Processing Agreements, each receiving only the data necessary for its function. These include Google Cloud Platform (hosting and databases), Vercel (frontend hosting), PostHog (product analytics), Sentry/Bugsnag (error monitoring with PII scrubbing), Google Workspace (email and documents), Customer.io and Resend (transactional and marketing email), Apify (public-data ingestion), Slack (internal team messaging) and Anthropic (AI analysis of product use).

Payment Processor: Stripe processes Client billing and previously processed legacy Creator payouts through Stripe Connect (Standard) and holds related KYC, tax, and payment-instrument data. Storika does not charge a platform fee on Creator payouts and does not store card, bank, KYC, or tax data on Storika infrastructure. Current product scope does not include outreach sequences, contract execution, creator payouts, general campaign shipment tracking, post monitoring or campaign reporting.

Connected Platforms: We exchange data with partner platforms, such as TikTok, Meta, YouTube, and Google, as necessary to provide the Service and in accordance with their platform terms.

Advertising Platforms: where we place their tags, Meta, TikTok and Google may receive website visit data and, if we report them, sign-up and first product connection events, as described under "Advertising and measurement" in Section 3, only while advertising is allowed in your browser and never with your email address. Our visitor-identification partner, RB2B (Retention.com), receives website visit data on the same condition.

Between Clients and Creators: Information necessary to facilitate a campaign is shared between the participating Client and Creator.

Legal and Safety: We may disclose information to comply with law, respond to lawful requests, or protect the rights, property, or safety of Storika, our users, or others.

Business Transfers: In connection with a merger, acquisition, financing, or sale of assets, information may be transferred as part of that transaction.

## 6\. Your rights and choices

Subject to applicable law, you may have the right to request access to, correction of, deletion of, or portability of your Personal Information, and to opt out of certain processing. To exercise these rights, contact us at privacy@storika.ai. Public Social-Media Creators may also request removal from our discovery index, and any Creator may object to profiling or automated analysis for discovery and matching, by contacting privacy@storika.ai. We will honor verified requests within the timeframes required by applicable law and our contractual obligations.

Storika honors the Global Privacy Control (GPC) and Do Not Track signals: a browser that sends either is treated as opted out of advertising, wherever you are. Our cookie banner (Cookie settings in every page footer) and the "Do Not Sell or Share My Personal Information" control in Section 3 let you change your analytics and advertising choices at any time. Turning advertising off in our cookie banner or with the "Do Not Sell or Share My Personal Information" control stops our website from loading the visitor-identification technology described in this Policy. To opt out of the email-marketing tracking it may already have associated with you (provided by our partner, Retention.com / RB2B), please visit the Retention.com Opt-Out Page directly at https://app.retention.com/optout. Vetted Creators may disconnect their OAuth tokens at any time, which immediately ends ongoing collection from the connected account. For Google or YouTube connections, users may also revoke access through Google’s security settings at https://security.google.com/settings/security/permissions where applicable. Storika will also assist sellers, TikTok Shop, and other authorized partners in fulfilling access, correction, deletion, and other end-user data requests where required by law or contract. We do not discriminate against users for exercising their privacy rights.

## 7\. Data security

Storika maintains technical and organizational measures designed to protect Personal Information. Personally identifiable account data is stored in encrypted relational databases on Google Cloud Platform; behavioral and analytics data in BigQuery is stored separately and linked by tokenized identifiers rather than direct PII. Product analytics in PostHog work differently: as Section 3 describes, your profile there carries your name, email address and account details, and the product events we record are linked to that profile. All user data in operational and analytical databases, object storage, and backup snapshots is encrypted at rest using AES-256, and all client-to-server traffic is encrypted in transit using TLS 1.2 or higher. Access to production systems and personal data follows role-based, least-privilege controls with single sign-on and mandatory two-factor authentication; credentials, OAuth tokens, and API secrets are stored in a dedicated secrets manager. Production workloads are segregated from development and staging, production PII is not copied to non-production environments, and sensitive data stores are logically separated. Storika uses cloud logging, Google Cloud Security Command Center, IP allowlisting where appropriate, CI-based dependency scanning, code review for production deployments, and macOS endpoint controls such as FileVault, XProtect, Gatekeeper, automatic screen locking, and security updates. Suspected incidents may be reported to privacy@storika.ai; confirmed breaches affecting partner, seller, or end-customer data will be handled under our incident-response process, including notice to affected partners, sellers, regulators, and individuals where required by law or contract. No system is perfectly secure, and we cannot guarantee absolute security.

## 8\. Data retention

We retain Personal Information only as long as necessary to provide the Service or as required by tax, accounting, and legal record-retention rules (typically seven years for transactional records). After the applicable retention period, identifying PII is deleted or anonymized, and backups are purged on a rolling 90-day cycle. At the end of a partner or customer relationship, we delete or return collected customer data in our possession, subject to legal-hold and statutory-retention exceptions.

## 9\. Data storage and international transfers

Storika stores and processes TikTok Shop U.S. data only in Google Cloud Platform U.S. regions, including us-central1 and us-east1. Storika does not intentionally store or process TikTok Shop U.S. data outside the United States. Storika's other service data is also processed primarily in U.S.-hosted infrastructure. Because the Service is available globally, personal information of Clients and Creators located outside the United States may be transferred to and stored in the United States; where required, Storika uses applicable contractual safeguards, such as Standard Contractual Clauses or equivalent transfer mechanisms. Payment data is held by Stripe at Stripe's facilities and is not stored on Storika infrastructure.

## 10\. Children's privacy

The Service is intended for business users and creators who are at least 18 years of age. We do not direct the Service to, or knowingly collect Personal Information from, children under 18. If we learn that we have collected Personal Information from a child under 18 without appropriate consent, we will delete it.

## 11\. Changes to this Privacy Policy

We may update this Policy from time to time to reflect changes in our practices, technology, legal requirements, or other factors. We will post the updated Policy at https://www.storika.ai/privacy and revise the "Last Updated" date above. Material changes will be communicated as required by law.

## 12\. Contact us

If you have any questions, concerns, or requests regarding this Policy or our privacy practices, please contact us at:

Storika, Inc.

1259 El Camino Real, Unit #1321

Menlo Park, CA 94025

United States

Privacy and data-subject requests: privacy@storika.ai

General support: contact@storika.ai

Storika is not listed in app directories yet.

[Ask ChatGPT](https://chatgpt.com/?q=Help%20me%20set%20up%20Storika%20and%20prepare%20my%20first%20creator%20campaign.%0AStorika%20is%20not%20listed%20in%20app%20directories%20yet.%0AIn%20ChatGPT%2C%20turn%20on%20developer%20mode%20for%20your%20workspace%2C%20then%20add%20Storika%20as%20a%20custom%20MCP%20server.%0APaste%20https%3A%2F%2Fapi.storika.ai%2Fmcp%20as%20the%20server%20URL.%0AChatGPT%20opens%20a%20browser%20sign-in%20page.%20Sign%20in%20with%20the%20account%20you%20use%20for%20Storika%20and%20approve%20the%20connection.%0AAsk%20ChatGPT%20to%20call%20whoami%20to%20confirm%20the%20connection.%0AAsk%20for%20my%20brand%2C%20product%2C%20goal%2C%20market%2C%20budget%20and%20dates.%20Draft%20a%20campaign%20brief%20for%20my%20review.%20Before%20creating%20or%20changing%20anything%20or%20using%20paid%20tokens%2C%20explain%20the%20action%20and%20cost%20and%20wait%20for%20my%20explicit%20yes.%20Do%20not%20contact%20creators%20or%20send%20invites%20or%20messages.)[Ask Claude](https://claude.ai/new?q=Help%20me%20set%20up%20Storika%20and%20prepare%20my%20first%20creator%20campaign.%0AStorika%20is%20not%20listed%20in%20app%20directories%20yet.%0AIn%20Claude.ai%2C%20open%20connector%20settings%20and%20add%20Storika%20as%20a%20custom%20connector.%0APaste%20https%3A%2F%2Fapi.storika.ai%2Fmcp%20as%20the%20connector%20URL.%0AClaude%20opens%20a%20browser%20sign-in%20page.%20Sign%20in%20with%20the%20account%20you%20use%20for%20Storika%20and%20approve%20the%20connection.%0ABack%20in%20Claude%2C%20ask%20it%20to%20call%20whoami.%20It%20should%20return%20your%20connected%20Storika%20organization.%0AAsk%20for%20my%20brand%2C%20product%2C%20goal%2C%20market%2C%20budget%20and%20dates.%20Draft%20a%20campaign%20brief%20for%20my%20review.%20Before%20creating%20or%20changing%20anything%20or%20using%20paid%20tokens%2C%20explain%20the%20action%20and%20cost%20and%20wait%20for%20my%20explicit%20yes.%20Do%20not%20contact%20creators%20or%20send%20invites%20or%20messages.)[Ask Perplexity](https://www.perplexity.ai/search/new?q=Help%20me%20plan%20my%20first%20creator%20campaign%20with%20Storika.%0AStorika%20is%20not%20listed%20in%20app%20directories%20yet.%0AStorika%27s%20setup%20guide%20at%20https%3A%2F%2Fwww.storika.ai%2Fconnect%20documents%20ChatGPT%20and%20Claude%2C%20but%20has%20no%20Perplexity%20connection%20recipe.%20Guide%20me%20to%20that%20documented%20setup%20for%20the%20connection.%20Do%20not%20invent%20Perplexity%20setup%20steps%20or%20claim%20a%20connection%20here.%0AAsk%20for%20my%20brand%2C%20product%2C%20goal%2C%20market%2C%20budget%20and%20dates.%20Draft%20a%20campaign%20brief%20for%20my%20review.%20Before%20creating%20or%20changing%20anything%20or%20using%20paid%20tokens%2C%20explain%20the%20action%20and%20cost%20and%20wait%20for%20my%20explicit%20yes.%20Do%20not%20contact%20creators%20or%20send%20invites%20or%20messages.)
