Privacy statement

How we process personal data, the rights you have and how to reach us. Transparent, GDPR-compliant and aligned with the Google API Services User Data Policy.

Version: 15 October 2026

1. About this statement

Social Media Tools (Dutch Chamber of Commerce no. 78527465; trading as Senly; "we", "us") provides a SaaS platform that allows marketing professionals — including agencies, social media managers, content creators, in-house marketers and freelancers — to manage their client relationships, content, scheduling, appointments, email communication, marketing and reporting. In this statement we explain which personal data we process, why, for how long, with whom we share it and which rights you have.

We act as a processor within the meaning of the GDPR. The marketing agency that uses the portal is the controller for the personal data of its own end clients. We are happy to conclude a data processing agreement (DPA) with each agency on request.

For data we collect directly from you as an agency (account, payments, support) we act as controller.

2. Which data do we process?

CategoryExamplesPurpose
Account dataName, email address, password hash, role, language, avatarAuthentication, access control, personalisation
Company dataCompany name, logo, colours, domain, contact personWhite-label portal and invoicing
End client dataCompany name, contact person, email, notes, subscription stageCRM functionality within the portal
ContentDesigns (Canva/Metricool), captions, files, posts, calendarsContent and scheduling management
Payment dataStripe customer ID, subscription status, billing address, currency (EUR/USD)Subscription billing via Stripe
OAuth tokensEncrypted access and refresh tokens from Google, Microsoft, LinkedIn, Facebook, etc.Authorised API calls on behalf of the connected user
Email dataConnected Gmail/Outlook/IMAP accounts, emails sent and received within the portal, signaturesEmail functionality in the portal
Calendar dataConnected Google/Outlook calendars, available time slots, bookings via the public booking pageAppointment management and calendars
Insights dataStatistics from Google Analytics, Search Console and Business Profile as connected by the userDashboard widgets and AI summaries
Log dataIP address, timestamp, action, user agentSecurity, debugging and audit log
Session dataJWT token, language cookie (portal_locale)Staying signed in, remembering language preference
Marketing trackingCookieless tracker (anonymised), UTM parameters, signup quiz answersInsight into which campaigns generate leads
Social session cookiesAuth cookies from LinkedIn, Facebook, TikTok, Instagram — only when you explicitly click "Connect" via the Senly ConnectorRunning automation features on behalf of your agency
Conversation dataTranscript, title, time and participant addresses of conversations from a recording service the agency connects (Fireflies, tl;dv); recordings and notes you provide yourself for a report; the meeting reportPreparing a meeting report, tasks and follow-up
Client communicationSender, recipients, subject, time and a short text snippet (up to 280 characters) of email from clients and open leads in connected mailboxes; messages in the client portalReply tasks, CRM touchpoints, draft replies
Lead proposalsAddress, name, subject and a short snippet of a business enquiry from a sender who is not yet a client, lead or contactLetting the agency decide whether to create a new lead
Client portalName and email address of users at the end client, password hash, sign-ins, pages viewed, downloads, approvals and messages, session with IP address and browser detailsAccess to the client portal, approvals and insight for the agency
Billing details of buyersCompany name, address, postcode, city, country, billing email address and optionally Chamber of Commerce and VAT number, entered when accepting a quotePreparing the first invoice
Calendar appointments with clients and leadsTitle, time, location or meeting link and guests (name, email) of appointments in a connected calendar to which a client or lead is invitedPreparation, report and follow-up of the meeting
Team absenceAbsence period of a team member and which tasks, clients, leads and appointments were temporarily handed over to a colleagueHanding work over and returning it afterwards

3. Google API Services and the Google API Services User Data Policy

When you connect your Google account through Senly, the use of your Google data is governed by the Google API Services User Data Policy, including the Limited Use requirements. Below we explain exactly which Google services Senly accesses and what we do — and do not do — with your data.

3.1 Which Google scopes does Senly request?

  • userinfo.email — to display which Google account you are connected with.
  • drive — to fetch and display your client folders (designs, files) within the client profile. Senly only writes when you explicitly perform an upload from the portal.
  • analytics.readonly — read-only access to Google Analytics 4 reports for the property you select, to display them as dashboard widgets.
  • webmasters.readonly — read-only access to Search Console statistics (clicks, impressions, positions, queries) for the site you select.
  • business.manage — reading your own Google Business Profile statistics (search impressions, phone clicks, direction requests). Senly only changes your Business Profile when you publish an update or reply to a review from the planner yourself.
  • gmail.send / gmail.modify (only if you connect Gmail) — to send and read emails from within the portal on behalf of the connected account.
  • calendar (only if you connect Google Calendar) — to display available time slots on your public booking page and add bookings to your calendar.

3.2 What do we do with your Google data?

We use your Google data solely to deliver the Senly functionality you request:

  • Statistics (Analytics, Search Console, Business Profile) are shown as charts and numbers in your dashboard widgets. We do not merge Google data with other users, and we do not combine data across tenants.
  • Drive files are shown in the client profile. We never copy them to our own storage without your explicit instruction.
  • Emails (Gmail) are shown in the portal email feature for the user who connected the account.
  • Calendar data (Google Calendar) is used to read "busy" times and add confirmed bookings to your calendar.

3.3 What do we NOT do with your Google data?

  • We never use Google data for advertising or marketing purposes towards third parties.
  • We never sell or rent Google data to third parties.
  • We do not train AI models on your Google data. AI summaries are generated per request; the data is not used for model training after being sent to the AI provider (see section 5).
  • We do not share Google data with other tenants; multi-tenant isolation guarantees that agency A can never see data from agency B.
  • We do not use Google data for research or profile building beyond the specific feature you consented to.

3.4 Retention of Google data

  • OAuth tokens are stored encrypted until you disconnect via Senly or revoke your consent at myaccount.google.com/permissions.
  • Statistics (GA/GSC/GBP) are cached for at most 10 minutes per time period to save quota. AI summaries are cached for 24 hours.
  • Gmail emails are displayed locally in your portal; we do not store a full copy beyond what is necessary for the feature.
  • Calendar bookings are retained for as long as you use Senly, with an audit log for 12 months.

3.5 How do you disconnect?

You can disconnect in two ways:

  • Inside Senly: go to Integrations → Website & findability (or the relevant integration page) and click "Disconnect". Tokens are removed immediately.
  • At Google: go to myaccount.google.com/permissions and remove access for Senly.

3b. Social media platform integrations (Meta, LinkedIn, X, TikTok, Pinterest, YouTube, Threads, Bluesky, Mastodon)

Within the Senly Content Planner, an agency can connect its end-client's social media accounts to schedule and publish content on their behalf. Each connection uses the official OAuth flow or API of the respective platform, and any use of the obtained data is fully subject to the applicable Platform Developer Agreement (Meta Platform Terms, LinkedIn API Terms of Use, TikTok Developer Terms, X Developer Agreement, Pinterest Developer Guidelines, YouTube API Services Terms, Threads Platform Policy, Bluesky Terms, Mastodon API Terms) as well as the GDPR. Below we explain, per platform, which permissions we request, what we do and do not do with the resulting data, how long we retain it and how you can revoke it.

3b.1 Which platforms, permissions and purpose?

CategoryExamplesPurpose
Meta — Facebook Pagespages_show_list, pages_read_engagement, pages_manage_posts, business_managementOn behalf of the agency's client, show which Pages are managed, publish scheduled posts and display publication status. Through this publishing connection we do not read DMs or ads data and do not moderate comments; advertising runs only through the separate ads connection below.
Meta — Instagram (Business account linked to a Facebook Page)instagram_basic, instagram_content_publishPublish scheduled posts, reels or stories to the client's Instagram Business account and show the account in the connections list. We only process direct messages when the agency separately activates the message inbox (see below).
Meta — Threadsthreads_basic, threads_content_publish, threads_manage_insights; threads_read_replies, threads_manage_replies (only after separate activation)Publish scheduled Threads posts on behalf of the connected account, display the profile name and show follower and view counts in the analytics. Only when the agency separately activates the comment inbox: show replies to the account's own posts in the agency's inbox and answer them at the request of a signed-in agency employee. We do not store replies; we fetch them live from Threads. We do not process mentions or trending topics.
Meta — Ads (separate connection)ads_management, ads_readOnly when the agency activates this connection separately: show the client's selected ad account and Facebook Page, display campaign results (spend, reach, clicks, conversions) and, at the request of a logged-in agency user, create, pause or activate campaigns. Campaigns are always created paused; budget is only spent after explicit confirmation. We do not sell or share this data or use it for any other purpose.
Google Ads — Advertising (separate connection)adwordsOnly if the agency activates this connection separately: show the client's chosen Google Ads account, display campaign results (spend, impressions, clicks, conversions) and, at the request of a logged-in agency staff member, create, pause or activate search campaigns. Campaigns are always created paused; budget is only spent after explicit confirmation. We do not sell or share this data and do not use it for other purposes.
Meta — Message and comment inbox (separate activation)pages_messaging, instagram_manage_messages, pages_manage_metadata, instagram_manage_comments, pages_read_user_content, pages_manage_engagementShow direct messages from Instagram and Facebook Messenger, and comments on the client's Instagram and Facebook posts, in the agency's inbox, and reply to them at the request of a signed-in agency employee. Only if the agency turns it on, Senly also replies automatically: to a comment or DM with a set keyword with a public reply and/or a private message, and with an AI assistant (Google Gemini, see section 5) to DMs, using information the agency entered about the business. To do so, the assistant also transcribes voice messages and looks at the story someone replies to. An automatic message only goes to someone who commented or sent a message themselves, within the period Meta allows; we do not send bulk messages. With its first reply, the assistant makes clear that it is an automatic reply. Anyone who sends "stop" gets no more automatic DMs ("start" turns them back on); on Facebook, a comment with a keyword can still lead to one automatic private message. If a conversation is handed over to the team, the assistant sends at most one short holding message. Messages and the contacts a funnel produces (name, and email, phone or answers if the person gave them) are kept as long as the connection exists, and deleted when you disconnect, when the client is removed and when access is revoked or deletion is requested via Meta; the agency can also delete a single person or export their data. We do not store comments in the inbox, we fetch them live from Meta; we only keep a comment with a keyword, to be able to send the private message. We remove text, name and answers from the funnel log after 12 months; only the counts remain. We delete completed question rounds, appointment proposals and requests after 90 days, as well as notifications to the team about a conversation (also when the person is deleted). We also delete conversations of a connection that has not been active for 90 days. We do not sell or share this data and do not use it to train models.
LinkedIn — personal profilesopenid, profile, w_member_socialPublish scheduled posts to the personal LinkedIn profile of the user who approved the connection. We do not read connections, inbox or feed.
LinkedIn — Company Pages (Community Management API)w_organization_social, r_organization_social, rw_organization_adminPublish scheduled posts to the client's LinkedIn Company Page (for which the connecting user is admin), display publication status and show aggregate post performance (impressions, clicks, engagement) to the agency as part of client reporting. We also show comments on the page's posts in the agency's inbox and, at the request of a signed-in agency employee, post a reply on behalf of the page; we do not store comments. Apart from the commenter's name, we do not read personal profiles of followers or connections. Use of this data is subject to the <a href="https://legal.linkedin.com/api-terms-of-use" target="_blank" rel="noopener noreferrer">LinkedIn API Terms of Use</a> and the additional Marketing Developer Platform terms.
X (Twitter)tweet.read, tweet.write, users.read, offline.accessPublish scheduled tweets on behalf of the connected account. We do not read DMs or follower lists.
TikTokuser.info.basic, video.publish, video.uploadUpload and publish scheduled videos to the connected TikTok Business account, and display the account name. We do not read personal feeds or DMs.
Pinterestpins:write, boards:read, user_accounts:readPublish Pins to boards the user selected and display the account name.
YouTubeyoutube.upload, youtube.readonly; youtube.force-ssl (only after separate activation)Upload scheduled videos to the connected YouTube channel and display the channel name. Show comments on the channel's videos in the agency's inbox; after separate activation, a signed-in agency employee can reply to them on behalf of the channel. We do not store comments; we fetch them live from YouTube. We do not read viewer statistics beyond what you have published.
BlueskyApp password (created by you in Bluesky settings)Publish scheduled posts to your Bluesky account via the AT Protocol. We store the app password encrypted and use it solely for publication and, if you grant the app password direct message access, for showing and answering your Bluesky messages in the inbox.
MastodonPer-instance access token (via OAuth on your own instance)Publish scheduled toots to your Mastodon account on the instance you specify. If the token has read permission, we show mentions of the account in the agency's inbox and a signed-in agency employee can reply to them. We do not store mentions.
Google Business Profilebusiness.managePublish scheduled updates to the connected Business Profile, and show the reviews of that location in the agency's inbox so a signed-in agency employee can reply on behalf of the business. We do not store reviews; we fetch them live from Google.

3b.2 What do we do with the platform data?

We use the obtained data solely to deliver the requested planner functionality to the agency that approved the connection:

  • Publishing: the text, images and videos entered by the agency are posted to the connected account at the client-approved time, via the platform's official publishing endpoint.
  • Display: account name, avatar and (for Meta) the list of manageable Pages/IG accounts are shown in the connections list so the agency sees what is connected.
  • Status: per scheduled post we display whether publication succeeded, failed or is still pending — including the platform's error message on failure so the agency can act on it.
  • Reporting (LinkedIn Company Pages only, aggregate metrics only): impressions, clicks and engagement per published post plus follower count of the Company Page are shown to the agency as part of client reporting.
  • Client approval: for each scheduled post the agency can send a review link to the client. The client can approve or reject the post prior to publication; only approved posts are published.

3b.3 What do we NOT do with the platform data?

  • We never use platform data for advertising or to target any audience other than the owner's own audience.
  • We never sell, rent or share platform data with third parties or between tenants. Multi-tenant isolation guarantees that agency A can never see agency B's data, and that page X of client 1 is not visible to client 2 within the same agency.
  • We do not train AI models on platform data. AI caption suggestions are generated per-request based on user-supplied prompt input; the resulting posts and analytics are never sent as training data to an AI provider (see section 5).
  • Apart from the separate Meta message and comment inbox (3b.1), we do not read personal inbox messages, DMs or private content. The other requested scopes are strictly limited to publishing and (for LinkedIn Company Pages) aggregate page analytics.
  • We do not build personal profiles based on follower lists, likes or other behavioural data; we do not request those scopes.
  • We do not use platform data for research or any purpose outside the specific publication and reporting function you consented to.
  • Questions from followers that the agency keeps as knowledge are stripped of names and contact details before the assistant uses them in other conversations.

3b.4 Retention of platform data

  • OAuth tokens (access + refresh): stored encrypted with per-tenant AAD (AES-256-GCM). Retained until you disconnect within Senly, until the platform signals deauthorization via our webhook, or until the token expires and can no longer be refreshed.
  • App passwords / instance tokens (Bluesky, Mastodon): stored encrypted until you disconnect.
  • Publication history (scheduled posts, timestamps, media URLs, publication status, external post id): retained as long as the agency uses Senly, unless the user deletes a post. Deleted posts and events older than 90 days are automatically pruned by our retention cron.
  • LinkedIn Company Page analytics: raw metrics are cached for a maximum of 24 hours; aggregated reporting figures are retained as long as the agency uses Senly.
  • Page and account metadata (name, avatar, page-id/IG-id): retained until disconnect.

3b.5 Deauthorization and data deletion

  • Meta webhook: when you deauthorize Senly from your Facebook settings or submit a data deletion request, our webhook at https://app.senly.io/api/planner/webhooks/meta receives the signal and we remove all associated tokens, page metadata and publication data for the affected account within 30 days. A confirmation code is available on request.
  • LinkedIn: token revocation via linkedin.com/psettings/permitted-services immediately invalidates token access. On the next publication attempt we clean up the expired connection and, on request, delete all associated stored data.
  • Threads / Instagram / X / TikTok / Pinterest / YouTube: similar deauthorization flows are available via each platform's own account settings. Upon a valid deauth signal or explicit deletion request we remove all associated stored data.
  • Individual deletion request: you can always manually request deletion of all platform data for a specific connection by disconnecting inside Senly (Manage connections → × next to the connection) or by contacting us at info@senly.io.

3b.6 How do you disconnect?

3c. YouTube API Services

Senly uses the YouTube API Services for the YouTube integration in the Content Planner. By connecting your YouTube account through Senly, you agree that your use of YouTube data is subject to the YouTube Terms of Service and the Google Privacy Policy. Senly complies with the YouTube API Services Developer Policies, including the Limited Use requirements and the prohibition on unauthorized transfer of YouTube data.

  • Scopes: youtube.upload (used only to upload the videos you schedule) and youtube.readonly (used only to display the channel name, avatar and public channel statistics in your reporting).
  • What we do: upload the videos you schedule to the connected channel and display public channel/video statistics in the agency dashboard.
  • What we do NOT do: we do not fetch viewer data, watch history, comments or personal recommendations; we do not sell, rent or transfer YouTube data to third parties; we do not train AI models on YouTube data; we do not share data between tenants.
  • Retention: encrypted OAuth tokens (AES-256-GCM, per-tenant AAD) and public channel metadata (name, avatar, statistics). Tokens are deleted immediately upon disconnect and publication history within 30 days upon request.
  • Revoking access: you can revoke Senly's access to your YouTube account at any time via the Connections modal in Senly, or directly at myaccount.google.com/permissions. For full deletion of stored YouTube data please contact info@senly.io.
  • Google Privacy Policy: in addition to this statement, the Google Privacy Policy also applies to data processed through the YouTube API.

3d. Other integrations (tasks, design, email, meetings, storage, CRM and invoicing)

In addition to the social media platforms and Google services in sections 3, 3b and 3c, Senly offers optional integrations with a range of external tools. Every integration is created by you explicitly via OAuth or an API key; we store tokens/keys encrypted (AES-256-GCM, per-tenant AAD) and use them only for the requested function. We never sell platform data, do not share it between tenants and do not train AI models on it.

Tasks and project management

Monday.com, ClickUp, Asana, Notion, Linear, Jira (Atlassian), Basecamp, Todoist, Teamwork, Trello, Wrike: connect via OAuth or API token to import your assigned tasks/issues as Senly tasks. We only read what the connecting user is allowed to see; we do not write tasks back unless you explicitly enable that.

Design and content assets

Canva: fetch designs via OAuth to display them in the client profile. Figma, Adobe Express: connect design files. Google Drive, Dropbox, OneDrive, iCloud: optional connection to display client folders; we do not copy files to our own storage unless you explicitly upload.

Email and calendar

Gmail (Google), Outlook (Microsoft Graph), IMAP/SMTP: connect via OAuth or username+password to send and read emails from the portal on behalf of the connected account. Google Calendar, Outlook Calendar: display available times on your public booking page and add bookings to the calendar. IMAP/SMTP passwords are stored encrypted.

Meetings and notifications

Slack, Microsoft Teams, Discord: connect your workspace/server and pick a channel for notifications (e.g. new lead, published post). We only receive a webhook URL or OAuth token and post messages to the channels you choose; we do not read existing conversations.

CRM and leads

HubSpot, Pipedrive, Salesforce, GoHighLevel, Typeform: optionally connect to import contacts and form submissions as leads into Senly. We only read the fields you select at contact/deal level and only write back if you explicitly activate a sync.

Invoicing and payments

Moneybird, Xero, QuickBooks, Mollie: connect your accounting to display invoices and payments in Senly. We read invoice metadata (number, client, amount, status). Stripe: Senly uses Stripe for our own subscriptions and Stripe Connect for affiliate payouts (see section 8).

Email marketing

Mailchimp, Klaviyo: connect your audiences and campaigns so you get an overview in Senly. We only read aggregate figures and list names; we do not send emails through your account unless you activate a specific workflow.

Website analytics

Google Analytics (GA4), Google Search Console, Google Business Profile: see section 3 above for scopes and retention.

Alternative social planners (proxy)

Metricool, Buffer, Hootsuite, Later, Sprout Social: optionally connect when using Senly alongside an existing planner. We only read what is needed to display your connected accounts and publications; we do not post through these tools without an explicit instruction.

Meeting recordings and transcripts

Fireflies.ai, tl;dv: you connect your agency's own account with an API key (stored encrypted) and a secret webhook URL. After a meeting, Senly retrieves the transcript and looks for the matching appointment, client or lead. If that succeeds, Google Gemini turns it into a proposed meeting report (summary, agreements, tasks and follow-up). A shortened version of the transcript (up to 20,000 characters) is kept in that proposal so you can review it; we delete that text as soon as a decision is made on the proposal, and at the latest when the proposal expires after 14 days. If no match is found, we keep only characteristics (title, time and up to 10 guest addresses), never the text, for at most 30 meetings and at most 14 days. Disconnecting deletes the key immediately. You choose and control the recording service as an agency; it is not a Senly sub-processor.

How to disconnect any of these integrations

You can disconnect each integration within Senly via Integrations or Manage connections. On disconnect the token/API key and cached metadata are removed immediately; historical sync records (e.g. imported tasks) remain until you delete them yourself. You can also always revoke access at the platform level (e.g. in the connected tool's account settings). For full deletion of stored data for a specific integration, contact info@senly.io.

4. Senly Connector Chrome extension

When you install the optional Senly Connector Chrome extension and manually click "Connect" within a client profile, the extension reads the session cookies of the relevant social media platform (LinkedIn, Facebook, TikTok or Instagram) from your own browser and sends them encrypted to our server.

  • Encryption: AES-256-GCM, bound to your agency. Cookies from agency A cannot be read by agency B.
  • Purpose: solely to be able to run automation features (growth tools, invite tools) on behalf of your agency, without you having to share passwords. These actions run in your own browser via the Senly Connector, not on our server. On our server we use the cookies to check whether the connection is still valid and which account is connected.
  • Collection: the session cookies are only sent to Senly after an explicit user action ("Connect" button). In addition, the extension checks in your own browser, for example before a growth run, whether the right account is logged in; no cookies are sent to Senly for that, at most an irreversible derivative (hash) of the account id.
  • Retention: until you click "Disconnect" or the cookies are invalidated by the platform itself.
  • No passwords: the extension does not read passwords, only already-active session tokens. Your client passwords never enter our system.

5. AI functionality (Gemini, Groq, Cloudflare and others)

Senly offers AI-assisted features such as caption suggestions, brand checks, note suggestions and weekly Insights summaries. We use a tiered AI fallback ladder:

  • Google Gemini (first choice, with data processing terms confirmed by Google — data is not used for model training).
  • If Gemini is down, for features involving data of agencies and their clients Senly only falls back on AI services with a documented basis for transfers outside the EU (EU-US Data Privacy Framework, or a data processing agreement with SCCs): Groq, Cloudflare Workers AI, xAI Grok, OpenAI and Anthropic (Claude), depending on which API keys are configured.
  • We use Cerebras and OpenRouter only for Senly's own internal content, never with data of agencies or their clients.
  • Senly creates meeting reports (from a transcript, your notes or a recording) and reply suggestions for comments and DMs with Google Gemini only.

We send only the data needed for the request to the AI provider. AI summaries of your Insights data contain only numbers and top-N lists — no personal data of your end clients. Content features such as caption suggestions, brand check and note suggestions do process the content you provide (such as the brand profile, a client name or your own text) in order to perform the feature. Several AI providers are located in the United States; each provider's location and the basis for transfers outside the EU are listed on our Sub-processors page.

Agencies can optionally set their own Gemini API key in Integrations → AI; in that case the AI request goes directly via your own account. Senly only processes recordings for a meeting report with such an own Gemini key. For text features, an agency can also set its own key for another AI service (such as Claude, ChatGPT or Mistral); the request then goes via the agency's own account with that service, which the agency chooses and controls itself. If that request fails, Senly falls back on the ladder above. Note: on the free tier of Google AI Studio, Google may use the input to train its models, including messages from followers. So use a paid tier for your own Gemini key.

5b. Email, messages and meetings: what Senly prepares for you

Senly prepares work that a member of the agency reviews and approves, such as a task, a draft reply, a meeting report or a proposal for a new lead. For this we process the data below on behalf of the agency. Nothing is ever sent to a client without someone from the agency approving it, and email is only sent from the approver's own connected mailbox.

  • Mailbox scan: for a connected mailbox (Gmail, Outlook or IMAP), Senly checks new messages in the inbox and the Sent folder roughly every fifteen minutes: sender, recipients, subject, message identifier and time. We do not store the email itself. Only for email from a known client or open lead do we keep a short plain-text snippet (up to 280 characters, without attachments or quoted history) in the task to reply to that email, with a link to the email. A reply, including one from your own email program, closes the task. The agency can turn these tasks off. If the agency turns on the CRM timeline for email, the subject of email to and from open leads also appears as a touchpoint with that lead. Email from other senders stays outside Senly, except for a lead proposal (below).
  • Scan logs: to avoid processing the same email twice we keep only a message identifier, and to recognise Senly's own automatic emails in the Sent folder a non-reversible code (hash) of recipient and subject. We delete both after 90 days.
  • Proposal for a new lead: if someone who is not yet a client, lead or contact sends a business enquiry (recognised by fixed keywords, without AI), Senly prepares a proposal with the address, name, subject and a snippet of up to 280 characters. Newsletters, automated email and sales pitches are filtered out. Only the mailbox owner and those allowed to see all leads see the proposal. It stays open for 7 days; it only becomes a lead when approved. The legal basis is the agency's legitimate interest in following up an incoming enquiry.
  • Draft replies to client email and to messages in the client portal (off by default): if the agency turns this on, the text of the client email (with at most two earlier messages from the same thread) or of the unanswered messages in the client portal goes to the AI described in section 5, together with what the agency recorded about the client, the latest meeting report, open tasks and the posts planned for the next two weeks. The draft stays available for 5 days. A draft about an invoice is only visible to agency members with financial rights.
  • Meeting report: from a transcript (section 3d), your own notes or a recording you upload or record in Senly. Senly only processes a recording with the agency's own Gemini key; we do not store the recording and send it to Google only to create the report (a large file is briefly held by Google for this and deleted immediately after processing). After a report of a meeting with an external guest is saved, Senly can prepare a summary for that guest, without additional AI; it is only sent from the own mailbox after approval, or saved as a draft in that mailbox.
  • Social media DMs and comments: if a message or comment on a connected account is awaiting a reply, Senly creates a task containing only the number of waiting messages; the messages themselves stay in the existing inbox.
  • Absence: if a team member is absent, Senly can temporarily assign their tasks, clients, leads and appointments to a colleague. We record what was handed over so it can be returned afterwards.
  • Who sees it: prepared work is only visible within your own agency, to team members with access to that client or lead.
  • How long: a proposal stays open for 3 to 30 days, depending on the type. For draft replies and lead proposals we delete the email and message text (snippet and draft) in the first weekly clean-up once 30 days have passed since the decision or the expiry of the proposal. For a lead proposal the name and subject are removed at that point too, and 12 months after the decision or expiry we delete the whole proposal. See also section 10.

6. Marketing and analytics tracking

Senly uses a proprietary cookieless visitor tracker on the marketing website (senly.io). It hashes IP addresses and User-Agent strings into a 24-hour identifier without storing personal data. Apart from optional Google Analytics (see the cookie list below), which only loads if it is enabled and you accept cookies, we place no third-party tracking cookies such as Facebook Pixel or Google Ads on the website.

When you sign up for a trial, we optionally ask about your role, challenge and platforms (signup quiz) to personalise your onboarding. These answers are stored in your own account and used to improve Senly's marketing — your personal answers are never shared publicly.

7. Client portal and approvals

Agencies can give their end clients access to their own client portal: signing in with email address and password, after an invitation from the agency. There the client approves content, views documents and results and sends messages. For the agency we record who signed in and when, which pages were viewed (at most once per 10 minutes per page), what was downloaded, uploaded, exported, approved or rejected, and which messages were sent. We keep this for 12 months, or shorter if the client is removed from Senly earlier. To secure the session we store the IP address and browser details; we delete these in the first weekly clean-up after the session has been expired for 30 days. We place no tracking cookies in the client portal. Older review links no longer show content and point to the client portal.

8. Payments via Stripe

Subscriptions are billed via Stripe. Stripe is an independent controller for your payment data. We only receive a Stripe customer ID, invoice status and the chosen currency (EUR or USD, automatically detected based on your IP address and adjustable until the first payment).

For the affiliate programme Senly uses Stripe Connect to automatically process payouts to partners. Affiliates are paid directly from Stripe.

9. Legal basis for processing

  • Performance of the contract — delivering the SaaS service.
  • Consent — when you connect a Google/Microsoft/social account via OAuth.
  • Legitimate interest — security, fraud prevention, technical stability and product improvement.
  • Legal obligation — tax retention duties and requests from supervisory authorities.
  • Legitimate interest of the agency — for example for a proposal for a new lead from a business enquiry by an unknown sender, and for keeping track of client portal usage. The agency is the controller for this.

10. Retention periods (summary)

  • Account data: for as long as the subscription is active + up to 90 days afterwards.
  • End client and content data: for as long as the agency does not delete it via the portal.
  • OAuth tokens (Google, Microsoft, social): until disconnection or token revocation at the provider.
  • Insights cache (GA/GSC/GBP/AI): 10 min (data) up to 24 hours (AI summary).
  • Log data (audit, SyncLog): up to 12 months.
  • Stripe link: for as long as the subscription is active; financial records 7 years (tax).
  • Senly's own bookkeeping (invoices, receipts, bank lines, tax returns, hours and trips): 7 years after the end of the financial year (statutory tax retention); an asset for as long as it is depreciated, plus 7 years; OSS returns 10 years. Uploaded files never attached to a booking: after 24 hours.
  • After cancellation: account data is retained for up to 90 days (reactivation window with advance email notice) and is then permanently deleted. An explicit erasure request is honoured within 30 calendar days, unless otherwise required by law (e.g. the tax retention obligation for invoices).
  • Transcript text in a proposed meeting report: until a decision is made on the proposal (then deleted within an hour), and at most 14 days. Meetings that cannot be matched to a client or lead: only title, time and guest addresses, at most 14 days.
  • Recordings for a meeting report: not stored.
  • Email snippets in tasks: for as long as the task exists. The list of client emails still awaiting a reply on a task disappears when the task closes, and otherwise after 90 days without changes. Mailbox scan logs: 90 days.
  • Email and message text in draft replies and lead proposals: deleted in the first weekly clean-up once 30 days have passed since the decision or expiry of the proposal. For a handled lead proposal the name and subject are removed at that point too; only the address is kept, so the same proposal does not come back. We delete the whole lead proposal 12 months after the decision or expiry. Other data of a proposal for a client or lead: for as long as that client or lead exists.
  • Calendar appointments with clients and leads from a connected calendar: up to 90 days after they end.
  • Client portal usage (who signed in when, and what was viewed, downloaded or decided): 12 months, or shorter if the client is removed from Senly earlier. Client portal sign-in sessions with IP address and browser details: up to 30 days after the session has expired.
  • Handovers during absence (work temporarily assigned to a colleague): 12 months after the last day of absence and the completion of the handover. A handover that is still running is kept.
  • Growth tools (profiles the growth tools found or approached): a profile that was never approached is deleted after 90 days. Unfollowed accounts, follow actions and invitations are deleted 12 months after they ended. A short log of sent welcome messages is kept as long as the connection exists, so nobody receives a second welcome message.
  • DMs and funnel contacts (messages, contacts, answers): as long as the connection is active. Text, name and answers in the funnel log: 12 months, after that only the counts. Completed question rounds, appointment proposals and requests, and notifications to the team about a conversation: 90 days. Raw webhook messages from Meta: 90 days.

11. Sub-processors

Data we process for agencies and their clients is shared only with sub-processors that are necessary for the service. The complete, always-current list — with each party's location and the basis for transfers outside the EU — is on our Sub-processors page:

  • Railway — Platform hosting and database (United States (Google Cloud)).
  • Google (Gemini, Drive) — AI features: text and content generation, image analysis, meeting reports and draft replies; storage of client files in Senly's Drive for agencies without their own cloud storage (US / EU).
  • Microsoft — Outlook calendar and mail (Graph API) (US / EU).
  • Anthropic — AI features: captions, content generation, support assistant, Advisory Board and help with automations; AI visibility (asking Claude the customer questions); fallback when other AI services are unavailable (United States).
  • Cloudflare — CDN, AI edge inference and a proxy for public Instagram profile data (United States).
  • Groq — AI features (supplementary) (United States).
  • xAI — AI features (supplementary) (United States).
  • OpenAI — AI features (supplementary / fallback); AI visibility (asking ChatGPT the customer questions) (United States).
  • Cerebras — AI for internal content (AI team, blog); no customer data in prompts (United States).
  • OpenRouter — AI gateway for internal content (AI team, blog); no customer data in prompts (United States (+ upstream providers)).
  • Resend — Sending transactional email (United States).
  • Stripe — Payment processing (incl. affiliate payouts) (United States).
  • Mollie — Online payment of an agency's invoices to its clients, when the agency connects its Mollie account (Netherlands (EU)).
  • KVK — Company data (lead enrichment) (Netherlands (EU)).
  • Moneybird — Accounting and invoicing integration (Netherlands (EU)).
  • Enable Banking — Bank connection: fetching payments to match them to invoices (Finland (EU)).
  • Metricool — Social media analytics (Spain (EU)).
  • Canva — Design integration (United States).
  • GoHighLevel — Task and CRM sync (optional, when enabled) (United States).

For our own operations, where Senly itself is the controller (support for agencies, contact with prospects, our internal team and our own bookkeeping), we also use these services. Data of an agency's clients does not go to them:

  • Telegram — notifications and approvals for our own team, such as a support question from an agency or a reply from a prospect, and receipts and questions about Senly's own bookkeeping (including name and amount of invoices to agencies).
  • Twilio, Infobip — WhatsApp messages and calls with our own team.
  • ElevenLabs, Microsoft — spoken versions of internal briefings for our own team (not for agencies).
  • Onze boekhouder (accountantskantoor) — Senly's own bookkeeping and tax returns: monthly packages with invoices to agencies (company name, contact, address, VAT number, amounts), receipts and bank statements; the accountant has read access in Senly and can download documents (every download is logged), and receipts may be sent to the scan address of the accountant's bookkeeping software.
  • Tavily, Brave — web searches for our own team, for public information.

We never sell or rent personal data to third parties. External services you connect yourself as an agency (CRM, accounting, e-mail marketing, cloud storage and the like) are controlled by you; they are not Senly sub-processors.

12. Security

  • Encrypted connections (HTTPS/TLS) for all communication.
  • Passwords stored as bcrypt hash (never readable).
  • OAuth tokens encrypted at rest (AES-256-GCM, per-tenant key derivation).
  • Strict multi-tenant isolation: each agency only sees its own data.
  • Rate limiting on login attempts and API routes to block brute-force attacks.
  • Audit log of critical actions (SyncLog).
  • JWT sessions with a maximum validity of 30 days.
  • Automatic error monitoring with anonymised stack traces.

13. Your rights

As a data subject you have the right under the GDPR to access, rectification, erasure, restriction, portability and objection. Please direct your request in the first instance to the agency you work with. Agencies can handle these requests via the portal or contact us at info@senly.io.

You also have the right to lodge a complaint with the Dutch Data Protection Authority (Autoriteit Persoonsgegevens).

14. Data breaches

In the event of a data breach that poses a risk to data subjects, we will inform the relevant agency without undue delay (within 24 hours of discovery). The agency is responsible for notifying the Data Protection Authority within 72 hours if required.

15. International transfers

Our primary hosting and data storage runs via Railway in the United States. Some sub-processors (Stripe, Google, Microsoft, AI providers) also process data outside the EU. For these transfers outside the EU we rely on the EU Standard Contractual Clauses (SCCs) and, where applicable, the EU-US Data Privacy Framework. We keep track of which processor processes which data outside the EU and can explain this on request. This also covers the content and prompts processed by the AI features: what you or your end clients enter into an AI feature may be processed by an AI provider outside the EU under the basis described above. A current overview of our sub-processors is available at /subverwerkers.

16. Contact

For privacy questions you can reach us via:

Social Media Tools
Nieuwlandsedijk 66, Lage Zwaluwe
info@senly.io

17. Changes

We may amend this statement. For material changes we will inform agencies via the portal or by email. The date at the top indicates when the statement was last updated. We keep earlier versions internally for reference.