Privacy Policy

This Privacy Policy describes how TrendSuite AI, LLC, a Delaware limited liability company, operating as “TrendSuite” (“we”, “our”, “us”), collects, uses, stores, and discloses personal data when you use the TrendSuite platform, website, and related services (collectively, the “Service”). TrendSuite is the data controller for personal data processed through the Service. This policy applies to all users worldwide and is supplemented by jurisdiction-specific disclosures where applicable (see Sections 4 and 7).

This policy does not apply to third-party websites or services that we may link to. We encourage you to review the privacy policies of those services separately.

Identifiers. Email address and display name, collected at account creation. If you sign in with Google, we receive your name and email from Google’s OAuth endpoint.

Brand profile data. The niche, target audience, tone of voice, content pillars, brand archetypes, and never-say rules you provide during onboarding and in subsequent profile edits. This is the primary input to content generation.

Social platform OAuth tokens. When you connect a social account, we store the OAuth access token and refresh token for that platform. These tokens are encrypted at the application layer using AES-256-GCM before being written to the database. We never store your social account passwords.

LinkedIn account access. If you connect a LinkedIn account, TrendSuite requests these LinkedIn permissions: openid, profile, email, w_member_social. These let us read your LinkedIn name and profile picture and your primary email address, and let us create posts on LinkedIn on your behalf when you publish or schedule LinkedIn content through TrendSuite. Where LinkedIn has approved Company Page access for TrendSuite, we instead request these LinkedIn permissions: r_basicprofile, w_member_social, w_organization_social, r_organization_social, r_organization_social_feed, rw_organization_admin. These let us read your basic profile, list the Company Pages you administer, read their post statistics, and post to the Company Page you choose. Without that approval, TrendSuite cannot access or post to a LinkedIn Company Page. Of the LinkedIn profile data made available to us, we store only your LinkedIn member ID and display name; we do not store your LinkedIn email address or profile picture. Your LinkedIn access token is encrypted at rest with AES-256-GCM, the same as every other social platform token described above, along with the scopes LinkedIn granted and the token’s expiry date.

Post performance from Facebook, Instagram and Threads. For posts TrendSuite published to an account you connected, we read each post’s own numbers from that platform: likes, comments or replies, shares, saves, reposts and quotes, and where the platform reports them, views and reach. We store these as totals per post, kept while your brand exists and deleted with it. We also read each connected account’s follower count once a day and keep those daily counts for 400 days. We do not read account-wide views or reach, and we do not receive or store who viewed or engaged with a post. We use these numbers to show your Performance screen and to suggest more of the ideas that worked best for your brand: when we generate new ideas with our AI provider, the ideas that earned the most engagement may guide the result, but the numbers themselves are not sent. We do not use this data for advertising and we do not sell it.

Photos from your website. If you tick the website photos box for your brand, we read up to 80 photos from the website address you give us and keep up to 30 of them, to use in your posts and videos. You confirm you own them or have the right to post them, and we record the version of our Terms and the time you did. We scan photos from your website to detect whether a human face appears, so we can exclude them. We don’t identify anyone, create face templates, or keep biometric data. Only a pass or fail result is kept. The check is made by Anthropic, our AI provider. You can turn website photos off in your brand’s video settings.

Usage data. In-product events such as features used, ideas generated, content plans created, and posts scheduled, linked to your account. Collected to understand how the product is used and to improve it.

Technical data. IP address, browser user agent, and device type. Collected by our hosting provider (Vercel) as part of normal server-side logging and retained according to Vercel’s log-retention policy. We also store your approximate location (country, region and city), derived from your IP address when you sign up and sign in, for security and support. We do not store the IP address itself with it.

People who interact with your accounts. When you connect a social account and use comments, the Inbox, contacts or automations, we process the platform identifier, username and messages of people who comment on or message your accounts. We do this on your behalf, as your processor; you are the controller of that data.

Prospects and subscribers. If you book a demo or subscribe to our newsletter, we keep the name, email, company and other details you give us, may use AI to help prioritise our follow-up, and send marketing only as described in Section 3.

Abuse prevention. At sign-up we store a one-way hash of the network you signed up from (never the IP address itself) and use your email address’s domain, to stop the free plan being claimed repeatedly by the same person (Terms of Service, Section 4B).

Support access. Authorised staff may view your account to resolve a support request. Each support session is view only, time-limited and logged: staff see your account as you do but cannot create, change, schedule, publish or delete anything, cannot send messages, change billing or your sign-in details, or export your data, and see only whether a social account is connected, never its name or details.

Payment data. We do not collect or store payment card data. All payment processing is handled directly by Stripe; we receive only non-sensitive billing metadata such as your subscription status and plan.

Running the product. Authentication, session management, content generation, scheduling, and all core features of the Service.

AI content generation. Brand profile data is included in prompts sent to our AI providers, Anthropic (text generation), OpenAI (narration voice and word timing for videos and, where enabled, image generation), Google (image generation, from a scene description written from your post), and ElevenLabs (narration from your video script, and music), to produce on-brand output. Under these providers’ paid API terms, your prompts and completions are not used to train their models. A provider may retain API data for a limited period for abuse monitoring before deletion, as described in that provider’s own policies.

Publishing to LinkedIn. When you connect LinkedIn and choose to publish or schedule a post, we send the post content you approve, text and any images, documents, or video you attach, to LinkedIn’s Posts API using your access token. The post is published to your own LinkedIn profile or, where LinkedIn has approved Company Page access for TrendSuite, to the Company Page you choose (see LinkedIn account access, above).

Fraud prevention. When you connect a social account, we keep a one-way, keyed hash of that account’s platform identifier, linked to your TrendSuite account. We use it only to limit how many TrendSuite accounts one social account can be connected to, which is how we keep the Free plan to one allotment per person. It cannot be used to identify or contact you on the platform, and we do not share it.

Billing. Subscription management, plan upgrades and downgrades, and payment processing via Stripe.

Communication. Welcome emails, account lifecycle emails, service announcements, and responses to your support requests. Lifecycle emails include product tips, onboarding reminders and updates about TrendSuite, which we send only to people who have created an account. You can opt out of them when you sign up, with the unsubscribe link in every one of them, or at any time in Settings, under Profile, Email preferences. Transactional emails (such as password resets) cannot be opted out of while your account is active.

Product analytics. We record in-product events (such as which features are used), linked to your account, to understand usage and prioritise the roadmap. These events are stored in our own database and are also processed by PostHog, our product-analytics provider (listed in the sub-processor table above). The part that runs in your browser loads only if you allow analytics cookies (Section 9). While you are signed in, we also keep the page of the app you last had open and when, in our own database only, so we can help you when you contact support and spot problems. We do not sell them, and we do not share them with advertising networks or data brokers.

Security monitoring. Error logs (via Sentry) and request logs (via Vercel) are used to detect and investigate security incidents, bugs, and abuse.

For users in the European Economic Area, United Kingdom, and Switzerland, we rely on the following legal bases:

• Contract performance (Article 6(1)(b)): processing necessary to operate the Service you have signed up for, including authentication, content generation, and scheduling.
• Legitimate interest (Article 6(1)(f)): security monitoring, fraud prevention, error tracking, product improvement through product analytics, and sending account holders product tips and onboarding emails about TrendSuite (the “soft opt-in” for existing customers under regulation 22 of the UK Privacy and Electronic Communications Regulations and Article 13(2) of the EU ePrivacy Directive). You can opt out of those emails when you sign up, through the unsubscribe link in each one, or in your account settings, and you may object to any of this processing (see Section 7).
• Consent (Article 6(1)(a)), where you give it for specific optional processing. Where we rely on consent, you can withdraw it at any time: for optional cookies and analytics with Cookie settings (also in the site footer and your account menu), and for anything else by contacting us.
• Legal obligation (Article 6(1)(c)), complying with applicable law, including responding to valid legal process.

We use the following third-party sub-processors to operate the Service. Each receives only the minimum data required for its specific function. Some sub-processors (for example, the website-analyzer, stock-photo, and social-publishing providers) are engaged only when the corresponding feature is enabled. We enter into Data Processing Agreements with each sub-processor that handles personal data of EEA/UK users.

We will notify users of material changes to this list at least 30 days in advance where required by applicable law.

Account data. Retained for the lifetime of your account. On account deletion, we initiate deletion within 30 days, subject to any legal hold obligations.

Server logs. Request and error logs are handled by our hosting and monitoring providers (Vercel and Sentry) and retained according to their respective retention policies.

Content & generation history. The ideas, content plans, and their generation inputs you create are retained for the life of your account so they remain available to you, and are deleted when your account is deleted, subject to the account-data schedule above.

Records of AI and stock pictures. For each AI-generated image, and each stock photo the Service chooses for you, we keep a short record: the model or stock photo used, the scene description (up to 500 characters), the results of our checks, and how it was labelled. We keep it to show how a picture was made and labelled if that is ever questioned. It never includes the picture itself, and it is deleted after 180 days.

Photos from your website. The photos we keep from your website, with their source address, size, a short description and the pass or fail result of the face check, are refreshed every 30 days: photos your site no longer shows are deleted at the next refresh. All of them are deleted when your brand is deleted.

Uploaded photos, videos, and voice recordings. We do not keep a library of your files. A file you upload is held only until every post that uses it has published or been cancelled, and is then deleted. A post that fails keeps its files for 7 days so you can retry it. An upload that is never scheduled is deleted after 7 days. A voiceover recording stays with the video plan it was recorded for, so the video can be previewed and rendered again, and is deleted 7 days after nothing uses it. Copies already published to a social platform are held by that platform under its own terms. The brand media library was retired on 1 October 2026 and the files in it were deleted.

Social platform connections. The account identifier, display handle, granted scopes, token expiry, and encrypted access token for a connected social platform, including LinkedIn, are retained for as long as that connection stays active. Disconnecting a platform deletes its access token, handle and connection details immediately; otherwise this data follows the account-data schedule above. The fraud-prevention hash described in Section 3 is kept while the connection is active and for 12 months after it was last connected or disconnected, then deleted. It is not removed when you delete your TrendSuite account, and is deleted at the end of that period. We rely on our legitimate interest in preventing fraud (GDPR Art. 6(1)(f)); you may object, and we will review any objection individually.

Comments, messages and automation history from Facebook and Instagram. For a comment on your own posts we keep its identifier, the post it is on, the commenter’s platform identifier and username, when it was made, and your reply. We do not store the comment’s words: they are read from Facebook or Instagram when you view them, and words stored by earlier versions of the Service are deleted with the comment. Comments are deleted 90 days after they were made. Records of your automations’ runs, which include the comment or message that started each run, are deleted after 90 days. Direct message conversations an automation took part in are kept while your brand exists. On a plan that includes the Inbox you can delete a conversation there at any time; on any plan you can ask us to delete one (see Section 7). Contacts your automations created are kept until you delete them.

Records of emails we send you. For each email we send, we keep the address it went to, its subject, what kind of email it was, when it was sent, and whether our email provider accepted it. We do not keep the email itself. These records are deleted after 90 days, and with your account.

Record of changes to your account. When something in your account is created, changed or deleted (a brand, plan, post, connection, setting or subscription), we keep a short record: what it was, which fields changed, when, and whether you, our staff or the app made the change. It never holds your connection keys or your full posts. We use it to help you when you contact support. Each record is deleted after 90 days.

Billing records. Transaction records are retained for 7 years as required by applicable tax and accounting laws, regardless of account deletion.

Depending on your jurisdiction, you have some or all of the following rights regarding the personal data we hold about you:

• Access (GDPR Art. 15; CCPA): Request a copy of the personal data we hold about you.
• Correction (GDPR Art. 16): Request that we correct inaccurate or incomplete data.
• Deletion (GDPR Art. 17; CCPA): Request erasure of your personal data, subject to legal retention obligations and the limited fraud-prevention records described in Section 6.
• Export / Portability (GDPR Art. 20): Receive your data in a structured, commonly used, machine-readable format.
• Restriction (GDPR Art. 18): Ask us to restrict processing of your data under certain circumstances.
• Objection (GDPR Art. 21): Object to processing based on legitimate interest, including profiling.
• Opt-out of sale (CCPA): We do not sell personal data. If this changes, we will provide a clear opt-out mechanism.
• Lodge a complaint: You have the right to lodge a complaint with your local supervisory authority (e.g., your national Data Protection Authority in the EU).

LinkedIn access. You can end TrendSuite’s access to your LinkedIn account at any time. Disconnecting LinkedIn from your Accounts page also asks LinkedIn to revoke the stored access token; if LinkedIn does not confirm that revocation, the connection is still removed from your TrendSuite account. You can also review and revoke TrendSuite’s access directly from LinkedIn, under Settings & Privacy, then Data privacy, then Other applications.

To exercise any right, email privacy@trendsuite.ai. We will respond within 30 days (or the shorter period required by applicable law). For complex or high-volume requests, we may extend this period by a further 60 days with notice.

TrendSuite operates primarily from the United States. When we transfer personal data of EEA or UK users to sub-processors outside the EEA/UK, we rely on Standard Contractual Clauses (SCCs) approved by the European Commission, supplemental technical and organisational measures where required, and the UK Addendum to the EU SCCs for UK transfers.

All sub-processors listed in Section 5 that are based outside the EEA operate under SCCs or an equivalent transfer mechanism. Several of our US-based providers (including OpenAI, Anthropic, and Stripe) are also self-certified under the EU-US Data Privacy Framework and its UK extension. Copies of the applicable transfer mechanisms are available on request.

Nothing optional loads until you choose. The first time you visit, a banner asks you to accept all, reject all, or choose by category. Until you choose, and if you reject, only the strictly necessary items below are used.

Strictly necessary (always on)

• Sign-in session: Supabase Auth cookies (sb-…-auth-token) keep you logged in; they last 7 days from your last visit and are removed when you sign out.
• Your cookie choice: ts_consent records what you chose in the banner, for 180 days.
• Workspace and preferences: active_brand_id (the brand you are working in), ts_tz (your time zone, so dates are right) and sidebar_collapsed (sidebar layout), each up to 1 year; a brand-switch notice cookie lasting 60 seconds; and, in your browser’s storage, your theme, display currency, unsaved onboarding drafts, in-progress posts and dismissed notices.
• Security steps: Short-lived cookies set only during a specific step: resetting your password (15 minutes), connecting a social account (OAuth state and verifier cookies, up to 30 minutes), and staff-only admin and support session cookies.

Optional (only if you allow them)

• Analytics: PostHog product analytics (a ph_…_posthog cookie and browser storage, up to 1 year), and Sentry session replay of a session in which an error occurs (browser session storage).
• Marketing attribution: ts_ref (90 days) credits the affiliate whose link brought you here if you later subscribe; ts_utm_first (90 days) and ts_utm_last (30 days) record the campaign, referring site and ad click identifier (gclid, fbclid, msclkid) you arrived with. If you create an account, what they hold at that moment is saved with your account so we know how you found us. They are not used for advertising and are not shared with ad networks.

Changing your mind. You can change your choice at any time with Cookie settings (also in the site footer and your account menu). Withdrawing consent stops the optional tools and deletes their cookies. If your browser sends a Global Privacy Control signal, we treat it as Reject all.

Error monitoring. We use Sentry to capture errors so we can fix them. Error reports are always on: they store nothing on your device and we remove cookies from them. Session replay runs only if you allow analytics; it records a session in which an error occurs (never a random sample of ordinary sessions), and is configured to mask text you type and block media, so we do not capture the content of your inputs.

Third-party requests. Some pages load resources from providers that receive your IP address: Cloudflare Turnstile on sign-up, sign-in, password-reset and demo-booking forms (bot protection), and Stripe at checkout. Your brand’s typeface is different: it comes from Google Fonts, but TrendSuite’s servers fetch it and pass it to your browser, so Google does not receive your IP address.

We do not use advertising cookies, third-party ad-tracking pixels, or cross-site advertising trackers. We do not use Google Analytics or any other cloud analytics service that transfers browsing data to advertising platforms.

The Service is for adults: you must be 18 or over to use it (Terms of Service, Section 2), and it is not directed to anyone under 18. We do not knowingly collect personal data from anyone under 18. If we learn that someone under 18 has created an account, we promptly delete the account and associated data. If you believe someone under 18 has provided us with personal data, please contact privacy@trendsuite.ai.

We implement technical and organisational measures to protect your personal data. A detailed description of these measures, including encryption standards, access control architecture, and our responsible disclosure programme, is available on the Security Overview page.

In the event of a personal data breach that is likely to result in a risk to the rights and freedoms of natural persons, we will notify the relevant supervisory authority within 72 hours of becoming aware of it, as required by GDPR Article 33. Where the breach is likely to result in a high risk to individuals, we will also notify affected users directly without undue delay.

We will update the “Last updated” date at the top of this page when we make material changes. For significant changes that affect your rights or how we use your data, we will notify you by email at least 14 days before the changes take effect. Continued use of the Service after the effective date constitutes acceptance of the updated policy.

Data controller. TrendSuite AI, LLC, a Delaware limited liability company, operator of the TrendSuite Service. Postal address for legal and privacy notices: 801 Travis Street, Suite 2101, PMB 2028, Houston, TX 77002. GDPR Articles 13 and 14 require us to give you the controller’s identity and contact details, so this address and the contact routes below are provided regardless of our corporate status.

Privacy questions and rights requests: privacy@trendsuite.ai

Data Processing Agreement requests: dpa@trendsuite.ai

EU/EEA representative: To be appointed before general availability in the European Union.

Data Protection Officer: To be appointed before EU general availability. Applicable to processing at scale of special-category data or systematic monitoring, as required by GDPR Article 37.