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.
This is a courtesy translation. The Dutch version is the legally binding original. View the Dutch version →
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.
| Category | Examples | Purpose |
|---|---|---|
| Account data | Name, email address, password hash, role, language, avatar | Authentication, access control, personalisation |
| Company data | Company name, logo, colours, domain, contact person | White-label portal and invoicing |
| End client data | Company name, contact person, email, notes, subscription stage | CRM functionality within the portal |
| Content | Designs (Canva/Metricool), captions, files, posts, calendars | Content and scheduling management |
| Payment data | Stripe customer ID, subscription status, billing address, currency (EUR/USD) | Subscription billing via Stripe |
| OAuth tokens | Encrypted access and refresh tokens from Google, Microsoft, LinkedIn, Facebook, etc. | Authorised API calls on behalf of the connected user |
| Email data | Connected Gmail/Outlook/IMAP accounts, emails sent and received within the portal, signatures | Email functionality in the portal |
| Calendar data | Connected Google/Outlook calendars, available time slots, bookings via the public booking page | Appointment management and calendars |
| Insights data | Statistics from Google Analytics, Search Console and Business Profile as connected by the user | Dashboard widgets and AI summaries |
| Log data | IP address, timestamp, action, user agent | Security, debugging and audit log |
| Session data | JWT token, language cookie (portal_locale) | Staying signed in, remembering language preference |
| Marketing tracking | Cookieless tracker (anonymised), UTM parameters, signup quiz answers | Insight into which campaigns generate leads |
| Social session cookies | Auth cookies from LinkedIn, Facebook, TikTok, Instagram — only when you explicitly click "Connect" via the Senly Connector | Running automation features on behalf of your agency |
| Conversation data | Transcript, 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 report | Preparing a meeting report, tasks and follow-up |
| Client communication | Sender, 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 portal | Reply tasks, CRM touchpoints, draft replies |
| Lead proposals | Address, name, subject and a short snippet of a business enquiry from a sender who is not yet a client, lead or contact | Letting the agency decide whether to create a new lead |
| Client portal | Name 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 details | Access to the client portal, approvals and insight for the agency |
| Billing details of buyers | Company name, address, postcode, city, country, billing email address and optionally Chamber of Commerce and VAT number, entered when accepting a quote | Preparing the first invoice |
| Calendar appointments with clients and leads | Title, time, location or meeting link and guests (name, email) of appointments in a connected calendar to which a client or lead is invited | Preparation, report and follow-up of the meeting |
| Team absence | Absence period of a team member and which tasks, clients, leads and appointments were temporarily handed over to a colleague | Handing work over and returning it afterwards |
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.
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.We use your Google data solely to deliver the Senly functionality you request:
You can disconnect in two ways:
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.
| Category | Examples | Purpose |
|---|---|---|
| Meta — Facebook Pages | pages_show_list, pages_read_engagement, pages_manage_posts, business_management | On 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_publish | Publish 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 — Threads | threads_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_read | Only 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) | adwords | Only 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_engagement | Show 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 profiles | openid, profile, w_member_social | Publish 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_admin | Publish 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.access | Publish scheduled tweets on behalf of the connected account. We do not read DMs or follower lists. |
| TikTok | user.info.basic, video.publish, video.upload | Upload and publish scheduled videos to the connected TikTok Business account, and display the account name. We do not read personal feeds or DMs. |
pins:write, boards:read, user_accounts:read | Publish Pins to boards the user selected and display the account name. | |
| YouTube | youtube.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. |
| Bluesky | App 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. |
| Mastodon | Per-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 Profile | business.manage | Publish 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. |
We use the obtained data solely to deliver the requested planner functionality to the agency that approved the connection:
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.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.
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).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.
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.
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.
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.
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.
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.
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).
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.
Google Analytics (GA4), Google Search Console, Google Business Profile: see section 3 above for scopes and retention.
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.
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.
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.
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.
Senly offers AI-assisted features such as caption suggestions, brand checks, note suggestions and weekly Insights summaries. We use a tiered AI fallback ladder:
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.
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.
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.
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.
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.
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:
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:
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.
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).
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.
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.
For privacy questions you can reach us via:
Social Media ToolsWe 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.