Privacy Policy

This Privacy Policy explains how we collect, use, share, and protect personal data when you use Rondo, our content automation platform, and the related websites and services (together, the “Service”).

Your use of the Service is also governed by our Terms of Service.

1. Who this policy covers

Rondo helps businesses (“brands”) plan, draft, approve, schedule, and publish content across channels such as company blogs, newsletters, and social media. This policy applies to two groups of people:

• Operators: the people at a brand who sign in to Rondo to configure it, review drafts, and approve what gets published.
• End-users: people whose data reaches Rondo because an operator has connected a third-party account (for example a LinkedIn page, an X or Meta account, a blog/CMS, an email service, or website analytics). This can include newsletter subscribers, people who comment on a brand’s posts, and website visitors counted in aggregate analytics.

We only collect end-user data that the Service needs in order to function and to help operators measure and improve their content. We do not buy personal data, and we do not use it to build advertising profiles.

2. Personal data we collect

2.1 Operator account & authentication

• Account details: your email address and, optionally, your name.
• Passwordless sign-in: Rondo’s default login is a “magic link”. When you request access we send a one-time login link to your email; the underlying one-time token is stored only as a hash and expires after 10 minutes. We also record your last login time.
• Google sign-in: if you choose to sign in with Google, Google tells us your email address, your name, and whether the address is verified. We request no other Google scope for sign-in, and we do not receive your Google password. Signing in with Google does not give Rondo access to your Gmail, Drive, or Calendar.
• Signup source: when you create an account after following a tagged link, we record the channel, medium and campaign from that link and the domain of the website that referred you, so we know which channels bring customers. Recorded once, when the account is created.
• Session cookie: after you sign in, we set a secure, HttpOnly session cookie (a signed token) that keeps you logged in for up to 7 days, refreshed as you keep using the app. See Section 6.

2.2 Brand configuration you provide

To run your content operation, operators enter configuration such as: brand name and details, your website address, “voice” documents and the answers you give in the guided voice setup, product notes, content topics and pillars, editorial focus periods, lists of content sources (e.g. RSS feeds), competitor domains, publishing destinations, channel settings, goals, and scheduling preferences. This may incidentally contain personal data if you choose to include it.

2.3 Connected accounts & credentials

When an operator connects a third-party service, we store the credentials and identifiers needed to operate that connection on the brand’s behalf. Sensitive credentials are encrypted at rest. These can include:

• Social accounts: OAuth access and refresh tokens, plus the page/organization or account identifier, for LinkedIn (company pages and personal profiles), X, Facebook Pages, and Instagram. Used to publish the posts you approve and to read engagement on posts Rondo published.
• Blog / CMS: API keys, endpoints, or OAuth tokens for your content management system: Shopify, WordPress, Payload, or a generic webhook endpoint you supply.
• Website & email analytics: credentials for website analytics (Plausible, or Google Analytics via OAuth or a service account) and for your email service (Resend), used to read aggregate performance figures back into Rondo.
• Telegram: a chat ID, if you use Telegram to receive status notifications about your content cycle.

You can disconnect any connected account from within the app at any time, which removes the stored credentials from our systems.

2.4 Content and engagement data

• Ingested content: articles and items fetched from the public sources you configure (titles, links, excerpts, timestamps) plus relevance scores Rondo generates.
• Drafts & approvals: the post drafts Rondo produces, your edits, and your approve/reject/schedule decisions.
• Social engagement: for posts Rondo published, we may store the author name/identifier, text, and link of comments so an operator can triage and draft replies. This is third-party personal data that reaches us on your instructions.
• Newsletter subscribers: where a brand composes newsletters through the Service, we may store the subscriber’s email address and name to enable sending.
• Aggregate metrics: post-level metrics (impressions, likes, comments, shares, clicks), website page metrics, and email event counts. Email metrics are stored as counts and do not include the recipient’s email address.
• Contact form: if you contact us or a brand through a form, the name, email, and message you submit.

2.5 Technical, log & usage data

Like most online services, our hosting and infrastructure providers process limited technical data needed to run and secure the Service, such as IP address, request metadata, and error logs. Specifically:

• Error monitoring (Sentry): when something goes wrong, we send a diagnostic report that includes the error, the request path, and (so that we can tell whose problem it is) your user identifier, email, and the brand and plan in context.
• Usage and cost telemetry: we record which AI actions ran, for which brand, and what they cost us, so that credits can be billed accurately and our published credit prices stay calibrated to real cost.
• Audit records: we log significant actions taken in the Service (for example a draft being approved, a brand being paused) so that “what happened here?” is answerable.

2.6 Rondo’s own newsletter

If you sign up for Rondo product updates on our website, we email you a link to confirm. Until you click it we store nothing about you, and the link expires after 48 hours. When you confirm, we add your address to our email provider (Resend) and keep a record of your consent: your address, when you asked and confirmed, the page you signed up on, and which version of the signup wording you saw. We use your address only to send product updates, about once a month. Every email has an unsubscribe link, and you can ask us to delete your address and consent record at [email protected]. This is separate from newsletters a brand sends through Rondo, which Section 3 covers.

3. Controller vs. processor

It matters who decides how data is used:

• For operator accounts and the operation of the Service itself (your login, account, billing, security, and product improvement), TechTulp is the controller.
• For end-user data that flows in through a brand’s connected accounts and content (e.g. newsletter subscribers, commenters, analytics), the brand is the controller and TechTulp acts as a processor handling that data on the brand’s instructions. Brands using the Service for this purpose should have their own privacy notice and, where required, a data processing agreement with us. We can provide a DPA on request at [email protected].

4. How and why we use data

We use personal data for the purposes below. Under the EU/UK General Data Protection Regulation (GDPR) we rely on the legal bases shown.

5. AI processing

Rondo uses third-party large language models to score content, discover topics, draft posts and replies, run the guided voice setup, generate suggestions, compose image prompts, and produce performance insights. To do this, relevant inputs are sent to our AI provider, Anthropic (Claude), and image generation prompts are sent to Replicate. Some features (topic discovery, SEO research, source suggestions) additionally run live web searches through Anthropic’s search tool, which sends the search query to that provider.

Inputs sent for AI processing can include your brand voice documents and setup answers, your website content and product notes, ingested public content, draft text, and the text of social comments you choose to act on. Please do not paste sensitive personal data about third parties into the Service unless necessary, as Rondo does not automatically redact it before AI processing.

We use these providers under their business/commercial terms. We do not permit your content to be used to train their public models under these terms, and we instruct providers to process data only to deliver the feature. No automated decision-making with legal or similarly significant effect on an individual takes place in the Service: AI-generated drafts are always reviewed and approved by a human operator before anything is published — the Service does not publish unattended.

6. Cookies & sessions

Rondo uses a minimal set of cookies and similar technologies. We do not use advertising or cross-site tracking cookies.

The strictly necessary items are required for the Service to work and cannot be switched off through the app. Where a brand embeds analytics on its own public website, that brand is responsible for any cookie notice or consent banner required on its site.

7. Sharing & sub-processors

We do not sell personal data. We share it only with service providers (“sub-processors”) that help us run the Service, with the third-party accounts you connect, and where required by law. This is our current list.

7.1 Infrastructure & operations

7.2 AI providers

7.3 Publishing & measurement platforms you connect

These receive data only because you connected the account and approved the content. They act as independent controllers for what happens on their own platforms, under their own terms and privacy policies.

The login form in the Rondo app and the newsletter signup form on our website are protected by Cloudflare Turnstile, which distinguishes people from automated traffic without using your data for advertising or cross-site tracking; Cloudflare’s handling of the data it collects for this is described in the Cloudflare Turnstile Privacy Addendum.

We may also share data in connection with a corporate transaction (e.g. merger or asset sale) or to comply with the law, enforce our terms, or protect rights and safety. If we add or replace a sub-processor that handles personal data we process on your behalf, we will update this list; customers under a DPA can ask to be notified of changes at [email protected].

8. International transfers

Some of our providers are located outside the European Economic Area (EEA), including in the United States, as noted in the tables above. Where personal data is transferred outside the EEA, we rely on appropriate safeguards such as the European Commission’s Standard Contractual Clauses, or transfers to providers certified under a recognized adequacy framework such as the EU–US Data Privacy Framework. We do not knowingly direct the Service to, or onboard customers in, countries subject to comprehensive trade sanctions. You can request more detail about a specific transfer, including a copy of the relevant safeguards, at [email protected].

9. Data retention

We keep personal data only as long as needed for the purposes above, then delete or de-identify it. These are the periods we actually operate to; a monthly automated sweep enforces them.

Two honest caveats. Application logs (at our hosting and error-monitoring providers) age out with those providers’ own log retention windows rather than on request; after an erasure the identifiers in them no longer resolve to a person. Database backups are snapshots taken for disaster recovery, so erased data can remain in a backup after it is gone from our live systems. Our backups expire automatically: scheduled snapshots are kept for at most 89 days, and our continuous point-in-time recovery archive holds roughly the last four weeks of changes. Erased data is therefore gone from every backup within 89 days at the latest. We erase from live systems and let backups expire on that schedule, and we never selectively restore data that somebody has asked us to delete.

10. Security

We apply technical and organizational measures appropriate to the risk, including encryption of data in transit, encryption of sensitive credentials and OAuth tokens at rest, access controls, passwordless authentication, bot protection on the login form, and brand-level isolation so one customer’s data cannot be queried from another’s session. No method of transmission or storage is completely secure, but we work to protect your data and to address incidents promptly. If a personal data breach is likely to result in a risk to your rights, we will notify the relevant supervisory authority and affected individuals as required by law, and we will inform affected customers without undue delay so they can meet their own notification duties.

11. Your rights

Depending on where you live, you have rights over your personal data. Under the GDPR these include the rights to access, rectify, erase, restrict, and object to processing, the right to data portability, and the right to withdraw consent at any time (without affecting prior processing). You also have the right to lodge a complaint with a supervisory authority (see Section 15).

To exercise any right, email [email protected]. We will respond within the timeframes required by law, normally within one month of receiving your request. We may need to verify your identity first. If your data is handled on a brand’s behalf (we are a processor), we will refer your request to that brand or assist them in responding, and we will tell you that we have done so.

Operators can also delete most data themselves from within the app (individual items, a whole brand, or the account) without needing to contact us.

California residents

If you are a California resident, you have rights under the CCPA/CPRA to know what personal information we collect and how we use it, to request access and deletion, and to opt out of any “sale” or “sharing” of personal information. We do not sell or share personal information as those terms are defined under California law, and we do not use it for cross-context behavioral advertising. You will not be discriminated against for exercising your rights. To make a request, contact [email protected].

12. Payments & subscriptions

Paid subscriptions are billed per brand. Payments are handled by our payment processor, Stripe, which acts as an independent controller for the payment data it collects. We process limited billing data: your name, billing contact details, VAT details where applicable, the plan and billing period for each brand, credit balances and usage, and transaction and invoice records. Full card details are handled directly by Stripe and are never stored on our systems; we hold only a Stripe customer reference and the last-four/brand metadata Stripe returns.

Where you hold several brands, they sit under a single Stripe customer record so they can be billed together. Archiving a brand cancels its subscription. See the Terms of Service for the commercial terms, and Pricing for the current price list.

13. Children

The Service is intended for businesses and is not directed at children. We do not knowingly collect personal data from children under 16. If you believe a child has provided us personal data, contact us and we will delete it.

14. Changes to this policy

We may update this policy from time to time. When we make material changes, we will update the “Last updated” date and version above and, where appropriate, notify you by email or in the app. Your continued use of the Service after an update means you accept the revised policy.

15. Contact & complaints

For any privacy question or request, contact us at [email protected]. For help using the product, [email protected] is the faster route.

If you are in the EU/EEA and believe we have not handled your data properly, you may lodge a complaint with your local data protection authority. In the Netherlands this is the Autoriteit Persoonsgegevens (autoriteitpersoonsgegevens.nl). We would, however, appreciate the chance to address your concern first.