- 2.1 Information You Provide Directly:
- 2.1.1 Clients:Â When a Client registers for an account, we collect Personal Information such as the Clientâs name, email address, company name, phone number, and billing information. Billing information is processed through a third-party payment processor, [Name of Processor, e.g., Stripe], and we do not store full credit card details on our servers. When a Client creates a campaign, we collect information about the brand, campaign objectives, and target audience, which may include Personal Information.
- 2.1.2 Creators:Â Creators are not required to create an account to interact with messages sent via the App. However, when a Creator responds to a message sent by a Client through the App, we collect any Personal Information the Creator provides in their response, which may include, but is not limited to, their name, social media handle, contact information, and any other information they voluntarily disclose.
- 2.2 Information from Meta Platforms:
- 2.2.1 Clients:Â To facilitate the sending of messages, we utilize the Meta Application Programming Interfaces (APIs), including, but not limited to, the Messenger API and Instagram Graph API. We access only the minimum necessary Personal Information from the Clientâs connected Meta account to enable message sending to Creators. This may include the Clientâs Meta page ID, access tokens necessary for API authorization, and information about the authorized user associated with the Clientâs account who is sending messages. We do not access or store the Clientâs complete social media contact list or data unrelated to the provision of the Appâs messaging functionality. Our use of information received from Meta APIs will adhere to Metaâs Platform Terms and Developer Policies, including any applicable limitations on use.
- 2.2.2 Creators:Â When a Client sends a message to a Creator via the App, we receive information from Meta related to message delivery and interaction, such as delivery confirmation, open status, and link click-throughs. We may also receive the Creatorâs public profile information (e.g., username, profile picture) as provided by the Meta API in the context of the specific message interaction. We do not collect or store Creator data beyond what is necessary for facilitating the message exchange initiated by the Client.
- 2.3 Automatically Collected Information:
- 2.3.1 Usage Data:Â We automatically collect information about how Clients interact with the App. This includes, but is not limited to, the Clientâs Internet Protocol (IP) address, browser type, operating system, pages visited within the App, features utilized, and timestamps of access. This data is used for analytical purposes, troubleshooting, App improvement, and to maintain the security of the App.
- 2.3.2 Cookies and Similar Technologies:Â We employ cookies and similar technologies (e.g., web beacons) to track Client activity within the App, store preferences, and enhance security. Clients can manage cookie preferences through their browser settings. For detailed information on our use of cookies, please refer to our Cookie Policy [Link to Cookie Policy - REQUIRED if you use cookies].
- 2.4 Information Not Collected:
- Storika does not request, collect, process, or store Sensitive Personal Information. âSensitive Personal Informationâ includes, but is not limited to, social security numbers, information related to racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic data, biometric data, data concerning health, or data concerning a natural personâs sex life or sexual orientation.
- 2.5 Information from YouTube API Services:
- Storika uses YouTube API Services to provide influencer marketing data. By using our Service, you acknowledge and agree that you are also bound by the **Google Privacy Policy **(https://www.google.com/policies/privacy). Through the YouTube API, we collect and store âAuthorized Dataâ (if you connect your account) and âPublic Dataâ (e.g., channel statistics, video metadata, view counts) directly from your device or account, which may involve the use of cookies or similar technologies to authenticate your access.
- 3.1 To Provide and Operate the Service:Â To enable Clients to send messages to Creators, manage their campaigns, and track message performance. This includes utilizing the Meta APIs to facilitate message delivery and retrieval of necessary interaction data.
- 3.2 To Communicate with Clients:Â To send transactional communications (e.g., account registration confirmations, billing notifications, password reset emails), respond to Client inquiries, and provide customer support.
- 3.3 To Improve the App:Â To analyze usage data, identify trends, diagnose technical issues, develop new features, and enhance the overall user experience of the App.
- 3.4 To Comply with Legal Obligations:Â To comply with applicable laws, regulations, legal processes (e.g., subpoenas, court orders), and lawful requests from government authorities.
- 3.5 For Security Purposes:Â To protect the App, our Clients, and Creators from fraudulent activity, unauthorized access, misuse, and other potential security threats.
- 3.6 With Your Consent:Â For any other purpose disclosed to you at the time we collect your Personal Information, provided we have obtained your explicit consent, where required by applicable law.
- **3.7 To Provide YouTube Analytics and Creator Discovery: **We use API Data retrieved from YouTube API Services to: (i) track campaign performance, verify content uploads (e.g., checking for required hashtags); (ii) identify and recommend potential YouTube creators that match our Clientâs campaign criteria (e.g., creating candidate shortlists based on subscriber count, engagement metrics, or content keywords); and (iii)Â generate analytics reports for our Clients. We do not use this data for surveillance or any unauthorized purposes.
- 4.1 With Meta:Â We share information with Meta as necessary to provide the core messaging functionality of the App through the Meta APIs. This sharing is strictly governed by Metaâs Platform Terms and Developer Policies, and we only share the minimum information required for API operation.
- 4.2 With Service Providers:Â We engage third-party service providers to assist with various aspects of our operations, including payment processing (e.g., Stripe), data hosting, analytics, and customer support. These service providers are contractually bound to protect your Personal Information and are authorized to use it only for the specific purposes for which we have engaged them and in accordance with this Privacy Policy and applicable data protection laws. A list of our current sub-processors is available upon request.
- 4.3 Between Clients and Creators:Â When a Client sends a message to a Creator via the App, the Creatorâs response, including any Personal Information provided by the Creator, is shared with the Client. This is inherent to the functionality of the App.
- 4.4 For Legal Reasons:Â We may disclose Personal Information if we are required to do so by law, legal process (e.g., a subpoena or court order), or in response to a valid request from a government or law enforcement authority. We may also disclose Personal Information if we believe it is necessary to protect our rights, property, or safety, or the rights, property, or safety of others, or to investigate suspected fraud or violations of our Terms of Service.
- 4.5 In Connection with a Business Transfer:Â In the event of a merger, acquisition, reorganization, sale of all or a portion of our assets, or bankruptcy proceeding, your Personal Information may be transferred to a successor or acquiring entity. We will provide notice on our App and/or via email of any such transfer and any choices you may have regarding your Personal Information.
- **4.6 With YouTube/Google: **Our use and transfer of information received from Google APIs to any other app will adhere to Google API Services User Data Policy, including the Limited Use requirements. We may share aggregated YouTube campaign performance data with our Clients (External Parties) to demonstrate campaign results. We do not sell YouTube API Data to third parties.
- 5.1 Access:Â You have the right to request access to the Personal Information we hold about you and to receive a copy of that information.
- 5.2 Rectification:Â You have the right to request that we correct any inaccurate or incomplete Personal Information we hold about you.
- 5.3 Erasure (âRight to be Forgottenâ):Â You have the right to request the deletion of your Personal Information, subject to certain exceptions permitted by law (e.g., legal obligations to retain data).
- 5.4 Restriction of Processing:Â You have the right to request that we restrict the processing of your Personal Information under certain circumstances, such as when you contest the accuracy of the data or object to the processing.
- 5.5 Objection to Processing:Â You have the right to object to the processing of your Personal Information under certain circumstances, including processing based on legitimate interests or for direct marketing purposes.
- 5.6 Data Portability:Â You have the right to receive a copy of your Personal Information in a structured, commonly used, and machine-readable format and to transmit that data to another controller, where technically feasible.
- 5.7 Withdrawal of Consent:Â Where we process your Personal Information based on your consent, you have the right to withdraw your consent at any time. The withdrawal of consent will not affect the lawfulness of processing based on consent before its withdrawal.
- **5.8 Revocation of YouTube Access: **You can revoke Storikaâs access to your YouTube data at any time via the **Google Security Settings **page. (https://security.google.com/settings/security/permissions)Â
- Formal Legal Tone:Â Uses more precise legal terminology (e.g., âPersonal Informationâ instead of âpersonal information,â âincluding, but not limited to,â âwithout limitation,â âsubject to applicable lawâ).
- Definitions:Â Defines âPersonal Informationâ clearly.
- Specificity:Â Provides more detail about the types of data collected, how itâs used, and how itâs shared, especially regarding Meta APIs.
- Data Processing Addendum (DPA) Mention (Implicit): Although not explicitly called a DPA, the sections on Meta API usage and service providers implicitly cover many of the requirements of a DPA. You should still have a separate DPA with Clients. This privacy policy references the need for contractual obligations with service providers.
- Sub-processor List:Â States that a list of sub-processors is available upon request (best practice).
- Cookie Policy Reference:Â Strongly recommends a separate Cookie Policy and links to it.
- Legal Basis (Implicit):Â The âHow We Use Your Informationâ section implicitly outlines the legal bases for processing (contract performance, legitimate interest, legal obligation, consent).
- Data Subject Rights:Â Expands on data subject rights with more legally precise language.
- International Data Transfers:Â Provides more detail on safeguards for international data transfers.
- Retention Period: Specifies a concrete retention period for message data (90 days). You must choose a period that is justifiable and complies with Metaâs policies.
- Security Measures:Â While still general, the description of security measures is more robust.
- California Specific Rights: The rights for California Residents have been streamlined and included in section 5.