Privacy Policy

Last updated: November 6, 2026 · Effective since: September 14, 2026

English / Español

This English version is provided for convenience. In case of any discrepancy, the Spanish version prevails. Read the Spanish version.

1. Who we are

This Privacy Policy governs the processing of personal data carried out by:

• Data controller: Alejandro Daniel Franco Zarza
• Tax ID (CUIT): 20-26025056-4
• Legal address: Chaco 965, Corrientes, Argentina
• Contact email: [email protected]
• Product: OneClickContent (OCC)
• Website: https://oneclickcontent.app

OCC operates under the personal responsibility of the individual named above. The owner reserves the right to transfer OCC's operations, assets and obligations to a legal entity that may be incorporated in the future. In that case, this policy will remain in force with the corresponding replacement of the Controller, and Users will be notified reasonably in advance.

Access model: brand owners, agencies and administration

The owner of each brand may authorize one or more agencies to operate that brand within OCC, with permissions limited to the tasks the owner enables and revocable at any time. Each authorized agency can only access data within those permissions: it cannot operate other brands or expand its own access. The platform administrator (the Controller named above) may access the data of any brand for technical support and operation of the service.

2. Data we collect

2.1. Data you give us directly

• Account data: name, email address, password (stored as an irreversible cryptographic hash).
• Billing data: where applicable, legal name, address and tax ID to invoice what was agreed directly with you. OCC does not charge automatically within the Platform: price, payment method and frequency are agreed separately with each client (see "Commercial terms" in the Terms of Service), and OCC does not store card or other payment method details.
• Content you upload: images, videos, texts, creative briefs, reference files and any other material you upload to the platform for processing.
• Communications: messages you send us by email, support or related channels.

2.2. Data we receive when you connect Meta (Facebook / Instagram)

When you authorize OCC to connect to your Meta account through Facebook Login for Business, we receive and store:

• Account identifiers: your Facebook user ID, the IDs of the Facebook Pages you manage, the IDs of the linked Instagram Business or Creator accounts, and the IDs of associated ad accounts.
• Access tokens: long-lived tokens issued by Meta that allow us to carry out authorized operations on your behalf. Sensitive credentials are stored with restrictive operating system permissions and, in production, encrypted at rest.
• Page and profile data: name, picture, bio, category, follower count and public data of the connected Pages and accounts.
• Metrics and Insights: reach, impressions, clicks, interactions, aggregated demographic data about your audience, and post and campaign metrics — always provided you have authorized the corresponding permissions.
• Ad campaign data: campaign structure, ad sets, ads, budgets, targeting, spend and performance, if you use the Marketing API features.
• Content published by OCC on your behalf: we record the posts, reels, stories, carousels and ads that are generated or published through the platform.

OAuth permissions requested from Meta

OCC requests the following permissions when you connect Meta. Each one is used exclusively for the stated purpose:

• pages_show_list — list your Facebook Pages so you can choose which one to connect.
• pages_read_engagement — read the posts, reactions and shares of what you published.
• pages_manage_posts — publish to your Page the content you approved.
• pages_read_user_content — only read the comments on your Page. OCC does not reply to, hide or delete comments.
• instagram_basic — identify your Instagram account and list its posts.
• instagram_content_publish — publish to Instagram the content you approved.
• instagram_manage_insights — view the metrics of each post.
• instagram_manage_comments — only read the comments on your posts. OCC does not reply to, hide or delete comments.
• read_insights — view your Page's results for the last 28 days.
• business_management — view your business assets and, only with your confirmation, grant partner access to the agency you choose, with the minimum tasks required.
• ads_read — view your campaigns, their spend and their results.
• ads_management — pause or resume campaigns and change their budget, always with your confirmation.

2.3. Email and email marketing data

When you connect a mailbox or manage campaigns from OCC, we may store and process:

• Sender identity: email address, display name, provider and identifier of the connected account.
• Connection credentials: Google or Microsoft OAuth tokens, or SMTP/API credentials provided by the account holder. They are stored encrypted and are never shown again in the browser.
• Permissions: Gmail campaigns request basic identity and sending. Gmail reading and replying inside OCC are postponed; no mailbox-reading permission is requested. We do not request Google Contacts, message deletion or label changes.
• Campaign contacts: email, name, lists, tags, source and date of consent, unsubscribes, bounces and complaints.
• Campaigns and results: subject, content, audience, schedule and metrics for sends, opens, clicks and unsubscribes. Opens may be measured with a minimal image and clicks with signed redirect links.
• Own account mail: when you enable an OCC address for your brand, incoming messages, sender, subject, text, attachments and original message are stored encrypted to view registration codes and notices. Only the owner and global administrator can access them. Contacts are not imported and these messages are not sent to AI models.

2.4. Data generated by OCC

• AI-generated content: text, copy, ideas, briefs and calendar production is assisted by the team's connected AI assistant, according to the agreed service and under the account and terms of its operator. The website currently does not include a self-service automatic text generator. Images are generated with Google Gemini, the only AI service OCC calls from its server.
• Usage logs: records of the operations you perform within the platform (what you generated, when and which account you used).
• Technical data: IP address, device type, browser, operating system, connection date and time, session identifiers.

2.5. TikTok

Only when you authorize the connection, TikTok provides your account identifier, display name, profile image, access credentials and refresh credentials. We store the identifier, account name and credentials to recognize the authorized destination. Credentials are encrypted in production and are not displayed in the browser.

We request user.info.basic to identify your account and video.publish to send the video or photos you reviewed and confirmed. We query the account's current privacy, comment, Duet, Stitch and maximum duration options. When you confirm a send, we share the video, text and selected options with TikTok; we retain the send identifier and status to report the result and avoid duplicates. Optional features requestvideo.list to read public videos and engagement counts, user.info.stats for profile totals, and video.upload to send media to your inbox to finish editing and publishing in TikTok. They require TikTok approval and separate account consent. We do not read private messages or audience demographics. Statistics are fetched when you use the feature; draft receipts retain the piece, reviewed caption and status to avoid resends. A video draft does not automatically transfer its caption: it is shown for copying in TikTok. We do not use this data to train AI.

TikTok approved Direct Post on October 16, 2026. Each release requires environment enablement, the account's publishing permission and confirmation of the exact piece. Review testing is conducted separately in Sandbox using authorized accounts and private publication. In the meantime, you can download approved material and post it through TikTok Studio. You can remove OCC's access from TikTok settings by following TikTok's instructions for removing connected applications. To delete only TikTok data while keeping your OCC account, email [email protected] from your account address and specify "TikTok only". See the deletion instructions for details. Support handles this request with identity verification and the response period in section 7. Removing permission does not delete copies stored in OCC or videos already posted on TikTok; those videos are managed through TikTok.

2.6. LinkedIn

We use the connection you authorize for the profile or Page features enabled in OCC: publishing, reading and managing content and its metrics. A brand's data is not shared with other brands or used for advertising or data sales. You may request deletion of LinkedIn data only, after identity and brand verification. This covers profile and Page connections, stored LinkedIn data and its copies while preserving your account, other networks and original material. We do not mark the request complete until older backups and local copies have also been verified. Restoring OCC requires a new authorization. This does not delete posts from LinkedIn itself.

3. What we use your data for

OCC does not sell your personal data to third parties. OCC does not use the content of your Pages, metrics or campaigns to train its own or third-party AI models without your explicit consent.

About AI providers: on the server side, OCC only uses Google Gemini, and only to generate images; for paid API usage, Google states that it does not use that data to improve its models. Text production is assisted by the team's connected AI assistant, according to the agreed service and under the account and terms of its operator. The website currently does not include a self-service automatic text generator.

External assistants (MCP): if you connect OCC to an external assistant, tool responses may include the social network data you request and are authorized to access, such as Meta account names and identifiers. Your chosen assistant provider receives these responses and applies its own terms and privacy policy. You can revoke access for your account's MCP integrations from Account → Private MCP access → Revoke. Connecting accounts or an assistant does not in itself authorize publishing or advertising spend.

4. Who we share your data with

• Infrastructure provider: hosting, database and storage on our own server hosted by DigitalOcean.
• Network and CDN provider: Cloudflare, through which traffic to oneclickcontent.app passes to act as a proxy, protect the site against attacks and cache public content.
• Account mail reception: Cloudflare receives messages for enabled own addresses and forwards them to OCC over HTTPS for encrypted storage. DigitalOcean hosts the inbox and its encrypted backups.
• AI provider: Google (Gemini), only to generate images and only with what is needed for that image. Text production is assisted by the team's connected AI assistant, according to the agreed service and under the account and terms of its operator.
• Meta platforms: Facebook, Instagram and related services, to the extent you have authorized the connection.
• Google Ads and YouTube: to the extent you have authorized the connection (see section 12).
• TikTok: identification of the authorized account and sending the video and options you confirmed, as described in section 2.5.
• Email providers chosen by each brand: each brand connects its own mailbox or account (Google Workspace/Gmail, Microsoft 365/Outlook, its SMTP server or, if configured, Resend or Amazon SES with its own credentials). They only receive what is needed to deliver the confirmed campaign.
• Public authorities: when a court order or binding legal requirement obliges us to.

5. International transfers

Some of our providers are located outside Argentina, mainly in the United States and the European Union. When this happens, we require them to apply protection standards equivalent to those set out in Argentina's Personal Data Protection Law 25,326 and, where applicable, the European Union's General Data Protection Regulation (GDPR).

6. How long we keep your data

• Account data and Meta tokens: while your OCC account is active and up to 30 days after you delete it or revoke the permissions in Meta.
• TikTok credentials and connection data: while you keep the connection in OCC and until your deletion request is handled. Revoking permission in TikTok cuts access on that platform; deletion of OCC copies must be requested separately (section 2.5).
• Google Ads and YouTube tokens: while the connection remains active. Revoking the permission from your Google account cuts access immediately; OCC disconnects and deletes stored Google data as described in section 12, within 7 calendar days of a deletion request.
• Email tokens and credentials: while the connection remains active. When you use "Disconnect and delete credentials", OCC deletes its local copies; you can also revoke the permission from Google or Microsoft.
• Contacts and campaigns: as long as the brand keeps them in OCC. Unsubscribes, bounces and complaints are kept as long as necessary to prevent new unauthorized sends.
• Historical Gmail inbox data: reading is postponed and no new replies are prepared. Any previously prepared reply remains encrypted for up to ten minutes; its content is then erased. The encrypted delivery receipt contains only message and thread identifiers and expires after 29 days. Disconnecting Google or requesting deletion removes both.
• Own account mail: messages are retained for up to 90 days; trash for up to 30 days within that period. Encrypted recovery backups may retain messages for seven additional days and are separate from normal inbox access. The owner can pause new mail; access records without message content are retained for 90 days.
• Uploaded and generated content: while your account is active. You can delete it at any time from the platform.
• Billing data: 10 years, as required by Argentine tax regulations.
• Technical logs: 12 months, unless needed to investigate a security incident.
• Support communications: 36 months from the last contact.

7. Your rights

You have the right to:

• Access the personal data we hold about you.
• Rectify inaccurate or incomplete data.
• Erase your data (right to be forgotten).
• Object to certain processing.
• Restrict processing.
• Port your data to another provider.
• Withdraw your consent at any time.
• File a complaint with Argentina's Agency for Access to Public Information (AAIP) if you believe we have violated your rights.

To exercise any of these rights, write to us at [email protected] or use our data deletion form. We reply within 10 business days.

8. Security

We apply reasonable technical and organizational measures to protect your data: encryption in transit (HTTPS/TLS), restrictive operating system permissions and encryption at rest of sensitive credentials —including additional AES-GCM encryption for email secrets—, role-based access control, audit logs and periodic backups. Even so, no system is 100% secure. If we detect a security breach affecting your personal data, we will notify you without undue delay and, where applicable, report it to the competent authorities.

9. Cookies and similar technologies

OCC uses the following cookies:

• occ_session — signed-in session (expires when the browser is closed)
• occ_brand — selected active brand (30 days)
• occ_consent — cookie consent (12 months)

You can set your browser to reject them, although some features might not work properly. We do not use third-party advertising cookies for retargeting.

10. Minors

OCC is not directed at people under 18. We do not knowingly collect data from minors. If we detect that a minor has created an account, we delete it.

11. Meta Platform — specific terms

When you connect your Meta account to OCC, the terms and policies of Meta Platforms, Inc. also apply to you, including Meta's Data Policy. OCC only accesses the permissions you explicitly authorize in the OAuth flow and uses them exclusively for the features of the service.

OCC may publish content on your behalf at scheduled times without manual intervention, according to the rules you configure (auto-publish). You can turn this feature off from your brand settings.

You can revoke OCC's access at any time from Facebook's business integrations settings.

Deletion of data received from Meta

• Deletion request from Meta (Data Deletion Request Callback): https://oneclickcontent.app/api/meta/data-deletion
• Deauthorization, when you remove the app from Facebook or Instagram (Deauthorize Callback): https://oneclickcontent.app/api/meta/deauthorize
• Instructions, manual request and request status: https://oneclickcontent.app/en/data-deletion (Spanish: https://oneclickcontent.app/data-deletion)

When Meta notifies us of a deletion request or a deauthorization, OCC deletes the credentials (access tokens) and Meta identifiers it stored for that account, and gives you a code to track the status on the instructions page. It does not automatically delete brands' content, plans or files: that is requested separately through the form. In the records we keep about those connections (what was authorized, by whom and when), the Meta identifier is replaced by a hash rather than kept in its original form, so that history stays intact. When the request comes from Meta, the request record does not store your original identifier either. If automatic deletion cannot be completed, the request goes to manual review and is resolved within 10 business days.

12. Google (Ads, YouTube, Business Profile and email) and Microsoft

When you connect Google Ads, YouTube, your Business Profile or your email (Gmail/Google Workspace or Microsoft 365) to OCC, we only access the permissions you explicitly authorize in each service's OAuth flow, and we use them exclusively for what is described here.

Google Ads

Read access: the list of ad accounts accessible with the Google identity you connected, their campaigns and the metrics for the last 30 days.

Linking with your agency: if during onboarding you confirm "Give access to my agency", OCC links your Google Ads account to the manager account (MCC) of the agency that manages you, using Google's own invitation-and-acceptance mechanism (no password is shared). While the onboarding link remains valid you can remove that access from the same screen, and at any time you can do it directly in your Google Ads account, under Access and security. The agency has no button in OCC to do it on your behalf, and disconnecting OCC (see below) does not automatically remove that native access.

Campaign changes (create, pause, rename, change budget or activate) are disabled by default. For a specific action to become available for your brand, three switches must be enabled at the same time: a general one, managed only by OCC's administration, and the agency's and your brand's, managed by your agency's administrator. Even then, each change is shown in a preview that an authorized operator must approve before it is sent to Google. Without those enablements and that approval, OCC does not change campaigns or generate spend.

YouTube

Basic read access to the channel (identity and basic statistics) and, only when you confirm it on the preparation screen, uploading the video you chose as private with public and unlisted options kept disabled in OCC until their enablement and the corresponding Google permissions are complete. No upload is automatic.

The additional video management permission allows changing the visibility and scheduling the release of an existing video, with a preview and explicit approval. Requesting or verifying that permission does not itself enable public release: the feature must also be enabled in OCC and each specific video must be approved.

Google Business Profile

The management permission allows reading authorized profiles, their locations, business hours and reviews, and preparing information changes, replies or local posts. Each change requires a preview and explicit approval. This connection is pending Business Profile API access for this project and is unavailable in the current production version.

Email (Gmail / Google Workspace and Microsoft 365)

OCC identifies the authorized mailbox and sends confirmed or scheduled messages. Gmail campaigns request only identity and sending. Gmail reading, searching and replying in the original thread inside OCC are postponed. Read and reply directly in Gmail. OCC does not request mailbox reading, message deletion, label changes or Google Contacts. Incoming mail does not subscribe its sender to campaigns.

The Gmail inbox is postponed in every OCC environment. Sending still requires Google approval for its separate permission. Mailbox messages are not sent to AI models or used for brand voice analysis, training, profiling or advertising. They are not sold or shared with third parties; human access is limited to authorized operators using the email feature and cases allowed by Google policy, with consent where required.

How we store this data, for how long and how to revoke it

Google Ads, YouTube, Business Profile and email tokens are stored encrypted at rest (see section 8). None of this data —including campaigns, metrics and YouTube channel data— is sold to third parties or used for advertising or to train artificial intelligence models, our own or third parties'.

Revoking the permission directly from your Google account permissions page cuts OCC's access immediately, without waiting for you to request anything here. In addition:

• Channels: “Disconnect Google and delete stored data” revokes OCC's access and erases associated stored Google tokens and data, including connection backups. Google may revoke other OCC services and brands using the same Google account and project.
• Agency Operations: disconnecting a client removes its access and queues native Google revocation and associated data deletion. This does not delete your videos, campaigns or the agency's independently granted native manager access.
• Deletion requests: use our data deletion form. We verify the requester's identity and delete associated Google data within 7 calendar days of the request. A pending retry is not reported as completed.

Google-derived cached data expires within 30 days unless refreshed. Authorization is periodically revalidated. YouTube data is excluded from brand voice analysis and is not sent to AI assistants. We keep only a minimal deletion receipt; during a revocation outage, an encrypted token is retained solely to retry revocation and erased upon completion.

Google API Limited Use

OCC's use of information received from Google APIs (Google Ads, YouTube, Business Profile and Gmail/Workspace), and its transfer to any other app, adheres to the Google API Services User Data Policy, including the Limited Use requirements.

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

13. Changes to this policy

We may update this policy. When we make substantial changes, we will notify you by email and/or through a visible notice on the platform at least 15 days in advance. The "Last updated" date above always reflects the current version.

14. Contact

For any question, complaint or exercise of rights related to this policy:

• Email: [email protected]
• Postal address: Chaco 965, Corrientes, Argentina