Clamora Privacy Policy
Last updated: October 22, 2026
This policy explains how Apphive, Inc. ("Apphive," "we," "us"), a Delaware (USA) corporation with its address at 2810 N Church St, PMB 97340, Wilmington, DE 19802, processes information in Clamora (clamora.app). Clamora is an AI-powered marketing service: it creates and publishes content, replies to comments with the customer's approval, measures results, and manages ad campaigns on the social media accounts that our customers connect.
Privacy contact: hello@clamora.app.
1. Who is the controller of each type of data
- Data about our customers and their users (whoever signs up for Clamora, their team, and their billing): the controller is Apphive, Inc.
- Data about a customer's accounts, followers, and audiences (comments, messages, metrics, ads): the controller is the customer. Apphive processes it on the customer's behalf, as a processor, under the Data Processing Agreement (DPA). If you commented on the page of a brand that uses Clamora and want to exercise your rights, you may contact that brand or us; we will assist the brand.
2. Information we process
a) Customer account
Name, email, company, encrypted password or Google sign-in, language, and billing data (payments are processed by Stripe; we do not store card numbers).
b) Brand DNA
What the customer provides to us or asks us to analyze: their website, logo, colors, tone, products, and the ideas they write.
c) Connected social media accounts
When the customer connects an account (Facebook, Instagram, TikTok, YouTube, LinkedIn, or X), the platform provides us with its identifier, name, username, profile picture, and the access tokens with the permissions the customer approved. Tokens are stored encrypted.
d) Content
Text, images, and videos that are created, scheduled, or published for the customer, and their status.
e) Comments and messages from other people
When someone comments on or replies to the customer's posts or ads, we receive the text, the author's public name or username and identifier, the date, and the post. This is used only to read, propose a reply that the customer approves, or moderate (for example, hide spam) that conversation.
f) Metrics and ads
Metrics for the customer's accounts, posts, and campaigns (reach, views, engagement, followers, spend, and results) and the configuration of their campaigns.
g) Public content for trends
Public content and its public metrics, obtained only through the official APIs and within their terms. It is used in aggregate to understand topics and formats. We do not build profiles of individuals.
h) Waitlist
Email (required), name, website, type (business, agency or platform), language and the campaign you came from (UTM). We use it to tell you about the launch and offer you the pilot. It is kept until you unsubscribe or for 24 months at most.
i) Website usage
Technical browsing data (IP, device, pages) for security and error logging (on our own server, without personal data) and, if you consent, analytics.
3. What we use it for
- Providing the service: creating, scheduling, and publishing content; reading, proposing replies to, and moderating comments; measuring results and comparing variants (experiments); creating and monitoring campaigns in the customer's ad accounts.
- Supporting the customer, collecting payment, and invoicing.
- Security, abuse prevention, and compliance with the law and with each platform's policies.
We do not sell or rent this information. We do not share it with advertisers or data brokers. We do not use it to target advertising to the people who comment. We do not use platform data to train artificial intelligence models.
4. Artificial intelligence
Clamora uses AI providers to draft text, propose replies, and generate images and videos. We send them only what is necessary for each task and use the options that exclude the data from training their models. Replies to comments are approved by the customer before they are published. Realistic AI-generated content is labeled when the platform requires it.
5. Who we share it with
- Providers that host or operate Clamora on our behalf (cloud, database, storage, backups, email, error analytics) and AI providers, subject to confidentiality obligations. The list is at clamora.app/subencargados.
- The social media platforms themselves, when publishing, replying, or managing ads on the customer's behalf.
- Authorities, when required by law.
6. How long we keep it
- Access tokens: for as long as the account remains connected. They are deleted when the account is disconnected or access is revoked.
- Comments and replies: up to 24 months. YouTube comments, up to 30 days from when we obtain them, unless refreshed from YouTube.
- Customer metrics: up to 36 months. Metrics obtained from YouTube, up to 30 days, unless refreshed.
- Public content for trends: up to 12 months, aggregated where possible.
- If access to an account is revoked (in Clamora or from the platform itself), we delete what was obtained with that access within a maximum of 7 days.
- Customer account: for as long as it is active. Upon termination, the customer may request an export within 30 days; after that, the data is deleted, except what the law requires us to retain (for example, invoices).
7. Your rights
You may request access to, rectification, erasure, or portability of your data, object to or request restriction of its processing, and withdraw your consent, by writing to hello@clamora.app. We respond within a maximum of 30 days. See also the data deletion instructions. Depending on where you live (for example, the EU or the United Kingdom, California, Mexico, Brazil, Colombia, or Peru), you may have additional rights, including the right to lodge a complaint with your data protection authority.
8. International transfers
Data is processed primarily in the USA. For data originating in the European Economic Area, the United Kingdom, or Switzerland, we use the European Commission's Standard Contractual Clauses. Apphive, Inc. is not certified under the EU-U.S. Data Privacy Framework.
9. Platform-specific terms
Meta (Facebook, Instagram, Meta Ads)
We access the Pages, Instagram professional accounts, and ad accounts that the customer connects, using Meta's official APIs and in accordance with the Meta Platform Terms. You can remove our app on Facebook under Settings → Apps and Websites; we receive the deletion request and delete the related data.
TikTok
We use TikTok's official APIs to publish to the accounts the customer connects and to read their information, in accordance with the TikTok Developer Terms of Service. Before publishing, the customer sees the destination account, chooses the video's privacy setting, and confirms.
YouTube and Google
Clamora uses YouTube API Services. By using features that interact with YouTube, you agree to the YouTube Terms of Service, and the Google Privacy Policy applies. You can revoke our access in Google's security settings. Clamora's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
We use LinkedIn's APIs to manage the Pages the customer connects, in accordance with the LinkedIn API Terms of Use.
X
We use the X API to publish and read replies on the accounts the customer connects, in accordance with the X Developer Agreement.
10. Cookies
The portal uses a strictly necessary session cookie. The public website uses Google Tag Manager and Google Analytics, Microsoft Clarity and the Meta Pixel to measure our own campaigns only if you accept them in the cookie notice. You can change your choice at any time from the «Cookies» link in the footer.
11. Security
Encrypted connections (TLS), encrypted tokens, role-based access, audit logs, and encrypted backups with a separate provider.
12. Minors
Clamora is a service for businesses and is not directed to individuals under 18 years of age.
13. Changes
We will update this page when our practices change and will show the date of the last update. If the change is material, we will notify customers by email.