Introduction
ClaraOP is an operations platform for creators, talent managers and agencies. This Privacy Policy explains how ClaraOP ("ClaraOP", "we", "us" or "our") collects, uses, stores, shares and protects information when you use the ClaraOP website, application and related services.
It also explains how ClaraOP handles information received from Google APIs when you choose to connect a Gmail account.
For privacy questions or requests, contact: support@claraop.com
1. About ClaraOP
ClaraOP provides tools for creators, agencies and talent managers to manage brand opportunities, campaigns, deliverables, invoices, payouts and related operational workflows.
ClaraOP is currently operated under the ClaraOP name. If the legal entity operating ClaraOP changes, this Privacy Policy will be updated accordingly.
Depending on the circumstances and applicable law, ClaraOP may act as a controller of information you provide directly to the service or as a processor of information handled on behalf of an agency or other ClaraOP customer.
2. Information we collect
Account and profile information
When you create or use a ClaraOP account, we may collect information such as:
- your name;
- email address;
- account credentials;
- role and permissions;
- agency or creator membership;
- business information;
- tax-related information where required;
- profile and account settings.
Passwords are not stored in plain text.
Campaign and operational information
When you use ClaraOP, we may process information relating to campaigns and commercial activities, including:
- brand names;
- campaign values and currencies;
- deliverables;
- due dates;
- campaign status;
- communications relating to campaigns;
- invoice information;
- payout status;
- proof-of-delivery information;
- other information you enter into ClaraOP.
Financial and payout information
Where ClaraOP's payment or payout functionality is used, we may process information such as bank account details, payment instructions, invoice details and payout records.
Sensitive financial information stored by ClaraOP is protected using access controls and encryption at rest.
Google and Gmail information
Connecting Gmail to ClaraOP is optional.
If you choose to connect Gmail, ClaraOP requests read-only Gmail access using the Google Gmail API.
ClaraOP may access:
- Gmail message and thread identifiers;
- sender information;
- message subject;
- message date and time;
- message content required to determine whether an email relates to a potential brand opportunity or campaign; and
- structured information extracted from relevant messages.
ClaraOP does not request permission to send, modify or delete Gmail messages.
ClaraOP first uses filtering and search criteria to identify messages that may relate to brand opportunities. Message content may then be processed to determine whether the message is relevant and, where appropriate, extract campaign information.
Relevant information may include:
- brand name;
- campaign value;
- currency;
- deliverables;
- campaign type;
- due dates;
- other campaign-related information contained in the message.
Google authorization information
When you connect Gmail, ClaraOP securely stores the authorization credentials required to maintain that connection, including Google access or refresh tokens where applicable.
These credentials are encrypted at rest and are used only to provide the Gmail-connected functionality you authorized.
ClaraOP does not store its Google OAuth client secret in user or inbox database records.
3. How ClaraOP uses Gmail data
ClaraOP uses Gmail data only to provide user-facing functionality requested by the user.
Specifically, Gmail access is used to:
- identify potential brand-deal or campaign communications;
- classify relevant messages;
- extract campaign information;
- create or update structured campaign records;
- associate campaign records with their originating Gmail message or thread;
- avoid processing the same message repeatedly.
ClaraOP does not use Gmail data for advertising, behavioral profiling, credit scoring, lending or unrelated purposes.
4. Raw Gmail message content
ClaraOP may temporarily process the content of a relevant Gmail message in memory in order to classify the message and extract structured campaign information.
ClaraOP does not persist raw Gmail message bodies or Gmail snippets in its application database after this processing is completed.
The structured information required to provide the ClaraOP service may be retained, including:
- sender;
- subject;
- Gmail message ID;
- Gmail thread ID;
- message date;
- extracted campaign information.
This information may remain associated with the relevant campaign or operational record for as long as it is reasonably required to provide the service or until the applicable data is deleted.
5. Artificial intelligence processing
ClaraOP uses automated processing to classify potential brand-deal communications and extract structured campaign information.
For this functionality, relevant message content may pass through Emergent's AI processing infrastructure and be processed using Anthropic's Claude models.
The purpose of this processing is limited to providing the ClaraOP functionality requested by the user.
ClaraOP does not use, and does not permit Google Workspace API data to be used, to develop, improve or train generalized or non-personalized artificial intelligence or machine-learning models.
ClaraOP does not use Gmail content to train its own generalized AI models.
Emergent states that Customer Personal Data is not used to train, retrain, fine-tune or otherwise develop AI or machine-learning models and that its AI subprocessors are contractually prohibited from doing so.
Anthropic states that, by default, inputs and outputs from its commercial API products are not used to train Anthropic's models.
Under Anthropic's standard commercial API retention practices, API inputs and outputs may be retained on Anthropic's systems for up to 30 days, subject to exceptions relating to safety, legal requirements, contractual arrangements or other applicable policies.
ClaraOP does not represent that every third-party processor provides zero-data retention unless such an arrangement specifically applies.
6. Google API Services User Data Policy
ClaraOP's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
In particular:
- Google Workspace API data is used only to provide or improve user-facing ClaraOP functionality that is visible and relevant to the user.
- ClaraOP does not sell Google user data.
- ClaraOP does not transfer Google user data to advertising platforms, data brokers or information resellers.
- ClaraOP does not use Google user data for targeted advertising, personalized advertising, retargeting or interest-based advertising.
- ClaraOP does not use Google user data to determine creditworthiness or for lending purposes.
- ClaraOP does not use raw or derived Google Workspace API data to develop, improve or train generalized or non-personalized AI or machine-learning models.
- Google user data may be transferred to service providers only where necessary to provide the ClaraOP feature requested by the user, for security purposes, to comply with applicable law, or where otherwise permitted by Google's policies.
These restrictions apply to both raw Google data and information derived from that data.
7. Human access to Gmail-derived information
Access to Gmail-derived information by ClaraOP personnel is restricted.
ClaraOP does not permit routine human reading of Gmail message content.
Administrative or support access to Gmail-derived information is restricted to circumstances such as:
- support requested by the user;
- security or abuse investigations;
- compliance with applicable law or legal obligations; or
- other circumstances permitted under Google's Limited Use requirements.
Where administrative access is required, ClaraOP applies access controls and audit logging.
Administrative support sessions are time-limited, and Gmail-derived information is hidden by default unless an authorized reason for access is provided.
8. Service providers and subprocessors
ClaraOP uses third-party service providers to operate the service.
These may include:
Emergent
Provides application hosting, managed infrastructure, database services and AI-processing infrastructure used by ClaraOP.
Anthropic
Provides Claude models used for message classification and structured-data extraction.
Resend
Provides transactional email delivery. Transactional emails may contain ClaraOP campaign or invoice information required to send the communication but do not contain raw Gmail message bodies.
PostHog
May be used for analytics on ClaraOP's public, logged-out website pages. PostHog is not loaded on authenticated ClaraOP application pages and does not receive Gmail-derived content from those pages.
Provides Gmail and OAuth services when users choose to connect their Google account.
These providers receive information only where reasonably necessary to perform services on ClaraOP's behalf.
ClaraOP does not authorize its service providers to sell Gmail-derived information, use it for advertising, or use Google Workspace API data to train generalized AI models.
9. Analytics
ClaraOP may use analytics technologies on public, logged-out pages to understand website use and improve the public website.
These analytics may process information such as page interactions, browser or device information and similar usage information.
ClaraOP does not use public-site analytics to collect Gmail content or Gmail-derived information from authenticated ClaraOP pages.
10. Data retention
ClaraOP seeks to retain information only for as long as reasonably necessary to provide the service, comply with applicable obligations and protect the service.
Gmail message bodies
Raw Gmail message bodies and Gmail snippets are not persisted in ClaraOP's application database after classification and extraction.
Message content processed by external AI service providers may be subject to those providers' applicable retention practices.
Gmail connection credentials
Google authorization credentials are retained only while required to maintain an active Gmail connection.
When Gmail is disconnected, ClaraOP revokes the applicable Google authorization and removes the stored authorization credentials.
Gmail-derived records
Information such as message and thread IDs, sender, subject, dates and extracted campaign data may be retained where necessary to manage the associated campaign, maintain operational records or avoid duplicate processing.
When an account or applicable Gmail-derived record is deleted, ClaraOP removes the associated Gmail-specific identifiers and data unless retention is required for a lawful purpose.
Account and operational data
Account information is generally retained while the account remains active.
When an account is deleted, associated personal and Gmail-derived information is deleted as part of the account-deletion process, subject to limited information that ClaraOP may need to retain for legal, accounting, tax, fraud-prevention or security purposes.
Financial and legal records
Certain invoices, financial records or transaction records may need to be retained for accounting, tax or legal purposes.
Where such records are retained after account deletion, Gmail-specific message and thread links are removed where they are not required for the retained legal record.
Logs
Security, application and audit information may be retained for a reasonable period where required for troubleshooting, fraud prevention, security, compliance or operational purposes.
11. Disconnecting Gmail
You may disconnect Gmail from ClaraOP at any time through ClaraOP's Gmail integration controls.
When you disconnect Gmail:
- ClaraOP requests revocation of the Google authorization;
- stored access and refresh credentials associated with that connection are removed;
- ClaraOP stops making future Gmail requests using that connection.
You may also revoke ClaraOP's access independently through your Google Account settings.
Disconnecting Gmail does not necessarily delete structured campaign records that were previously created at your direction.
You may separately delete those records or delete your ClaraOP account.
12. Account deletion
ClaraOP provides account-deletion controls within the application.
When an individual account is deleted, ClaraOP removes the associated account and personal information in accordance with the user's role and the applicable account structure.
Where an agency is deleted by its authorized owner or administrator, ClaraOP removes applicable:
- Gmail connections;
- Google authorization credentials;
- Gmail-derived records;
- campaign source links;
- agency user access; and
- associated operational information that is not required to be retained.
Where an agency has multiple administrators, deleting an individual administrator account does not necessarily delete the entire agency.
Certain invoices or other records may be retained where required for legal, accounting or tax purposes.
13. Security
ClaraOP uses technical and organizational safeguards designed to protect information against unauthorized access, disclosure, alteration or destruction.
Measures include, where applicable:
- HTTPS encryption in transit;
- encryption of sensitive stored information;
- encrypted Google OAuth tokens;
- server-side storage of application credentials;
- role-based access controls;
- restricted administrative access;
- time-limited support sessions;
- audit logging for sensitive administrative actions;
- separation between public analytics and authenticated application activity;
- credential revocation and deletion controls.
No electronic service can guarantee absolute security.
14. International processing
ClaraOP and its service providers may process information in countries other than the country in which you live.
Where required by applicable law, we take reasonable measures to ensure that personal information is handled subject to appropriate contractual, privacy and security protections.
The location in which a particular service provider processes information may depend on that provider's infrastructure and contractual arrangements.
15. Your privacy rights
Depending on where you live, applicable privacy law may give you rights concerning your personal information.
These may include the right to:
- request access to personal information;
- request correction of inaccurate information;
- request deletion;
- object to or restrict certain processing;
- request portability where applicable;
- withdraw consent where processing is based on consent;
- lodge a complaint with an appropriate privacy or data-protection authority.
To make a privacy request, contact: support@claraop.com
We may need to verify your identity before completing certain requests.
16. Children
ClaraOP is intended for adults and business users and is not intended for children under 18.
We do not knowingly seek to collect personal information from children under 18 through ClaraOP.
If we become aware that an underage user has provided personal information in circumstances where they should not have done so, we may take steps to remove the account and associated information.
17. Sale of data and advertising
ClaraOP does not sell Gmail data or other Google Workspace API data.
ClaraOP does not use Gmail content for:
- targeted advertising;
- behavioral advertising;
- retargeting;
- advertising profiles;
- sale to data brokers;
- credit scoring;
- lending; or
- generalized AI-model training.
18. Changes to this Privacy Policy
We may update this Privacy Policy when ClaraOP's features, service providers, legal obligations or data-handling practices change.
The date at the top of this page will identify the most recent version.
Where required by law, we will provide additional notice of material changes.
If ClaraOP materially changes how Google user data is accessed, used, stored or shared, we will update this Policy and the relevant in-product disclosures accordingly.
19. Contact
For privacy questions, data requests or account-deletion enquiries, contact:
ClaraOP
Email: support@claraop.com
Website: https://claraop.com
