App privacy policy
Last updated · 20 November 2026
This policy covers Sow Social, the app published by MOREpanache, the tool real estate and brokerage professionals use to write, illustrate, schedule and publish their social media content. Data collected through the morepanache.com website is covered by a separate policy.
01Data controller
The app is published by MOREpanache, the communication and digital marketing studio run by Vincent Herbelet. It is a sole proprietorship based in Amsterdam, registered with the Amsterdam Chamber of Commerce under KVK 59874929 (VAT NL002443736B35). Address: Prins Hendrikkade 21e, 1012 TL Amsterdam, the Netherlands. For any privacy-related question, write to hey@morepanache.com.
02What we process
- Account data. Title, first name, last name, business email address, phone number, agency and city, as well as the date of last sign-in. This identifies the user, links them to their agency and allows us to send the messages the service requires; the date of last sign-in is used to delete unused accounts. To keep the user signed in on their device between visits, we also keep a fingerprint of the sign-in token (never the token itself), the type of browser and device, and the token’s creation, use and expiry dates.
- Content created. Text, visuals and posts written or generated in the app, including uploaded photographs and videos. This content may include images of properties and, where the user chooses to publish them, client testimonials. The news websites a user chooses to follow in the News feed (10 at most) are also stored.
- Content strategy. When a user uses “Create my strategy”, we store their personal strategy, separate for each of their agencies: their questionnaire answers (agency name, team size, city, neighbourhoods, activities, goals, tone, networks), the publishing calendar chosen, the ideas suggested with their status (to do, in progress, done, dismissed), their account number and the related dates. Only the user can see it: their colleagues, the agency manager and the network head office have no access to it in the app. To write the ideas, the agency profile, the calendar and the ideas already suggested are sent to our AI provider, without the user's identity (see §04).
- Social media connection data. When a user connects their agency's accounts, we store the Facebook Page ID, the associated Instagram professional account ID, their display names, and an access token issued by Meta. That token allows us only to publish to those accounts and to read their statistics.
- LinkedIn connection data. When a user connects their personal LinkedIn profile (never a company page), we store their LinkedIn member ID, their display name, and an access token with its expiry date. The permissions requested are limited to identifying the member and publishing on their behalf; we do not receive their email address. On LinkedIn, the authorisation appears under the name of our app, Sow Social.
- YouTube connection data. When a user connects their YouTube channel, the only permission requested from Google is to upload videos to that channel (
youtube.upload). We store an access token and a refresh token, both encrypted, the name of the channel (returned by YouTube with the first video published) and the identifier and link of each video published from the app. We do not read the channel, its videos, subscribers, comments or statistics, and we do not receive the user's email address or Google identity. On Google, the authorisation appears under the name of our app, Sow Social. - TikTok connection data. When a user connects their TikTok account, the permissions requested from TikTok are limited to reading their basic profile (
user.info.basic: identifier, display name, avatar) and publishing videos and photos to their account (video.publish). We store the account's identifier for our app (open_id), its display name, an access token and a refresh token, both encrypted, and the identifier and link of each post published from the app. Each time the user opens the publishing window, and again just before a scheduled post is sent, we ask TikTok what the account can publish (username, nickname, avatar, available privacy levels, whether comments, Duet and Stitch are enabled, maximum video length): this information is displayed, not stored, except the display name. The choices the user makes for each post (who can view it, allowed interactions, commercial content disclosure) are stored with that post, so that a scheduled post is published as chosen. We do not read the account's videos, followers, comments, messages or statistics, and we do not receive the user's email address or phone number. - Canva connection (optional). If a user connects their Canva account from “My account”, we store the display name and identifier of their Canva account, an access token and a refresh token (both encrypted), the connection status and the related dates. The permissions requested from Canva are read-only (
design:meta:read,design:content:read,profile:read): we read the list of the user’s designs (title, thumbnail, date) and the content of only the designs they choose to import, as images or videos. We never write to, edit or delete anything in their Canva account. Thumbnails are relayed by our servers and not stored; the images and videos imported are saved with the user’s draft, like their other visuals. - Manual publishing. For networks without direct publishing (WhatsApp, Google Business Profile…, and TikTok when the user has not connected their account), the app prepares the text and the media and the user publishes them themselves, from their phone’s share menu or after downloading them. In that case, the app transmits nothing to the network.
- Publishing reminders and calendar. When a user plans a manual publication in the calendar, we store a reminder: author, agency, network, planned date, text of the post, number of media, linked draft, and status (to publish, published, cancelled). We also store their preferences: whether the morning email is enabled, and the random key of their personal calendar link.
- Getting-started guide and badges. Steps of the “Getting started” guide completed and their dates, badges earned and their dates. This data is derived from actions taken in the app and is visible only to the user.
- Usage statistics. We record the actions performed in the app (generating a text or a visual, importing a listing…), with their author and date, without IP address, to measure use of the service and its cost. After 13 months, they are linked to the agency only.
- Publishing statistics. Follower counts, reach and engagement, collected periodically from Meta. These measurements are aggregated at page level and do not identify any individual.
- Activity logs. For security and traceability, we keep a record of actions performed in the app — publishing, scheduling, editing, cancelling, connecting a social account — with their author, date and originating IP address.
- Support messages. When a user sends a suggestion or reports a problem from within the app, we receive their message together with their name, email address, agency, the page they were on and their browser type, so that we can reply and reproduce the problem.
- Log of emails sent. To check that a message from the service was actually sent and to understand any failure, for each email sent by the app (address verification, password, alerts, reminders…) we keep the recipient address, the type of message, the date, the result of the sending, the reason for any error and the message’s technical identifier. We never keep its subject or its content.
- Newsletter. To send you the newsletter, we use your email address, your first name and your network. We keep the follow-up of each send (status: sent, failed…, reason for any failure, dates) and, where applicable, your unsubscription (date, originating newsletter). We use no tracking pixel (see §11).
- AI assistant. When you talk with the AI assistant, we record the messages of the conversation (what you type or dictate, and the assistant's replies), the date of your requests, the number of tokens used and the drafts it prepares or edits for you. To answer you, it may look at your content strategy, your drafts, your publishing calendar and your agency's listings. Please avoid entering your clients' personal data unless your post needs it. Voice dictation is optional: your browser transcribes your voice, and we only receive the text, never the audio recording.
- AI assistant usage tracking and reminders. When you use the AI assistant, we record that you used it (date of your requests, drafts prepared, opened, scheduled or published, refused requests) and whether the assistant card or panel was displayed to you, without keeping the content of your conversations for this purpose. We use this data to measure and improve the service and to send you, at most once a week, a reminder email to help you finish a first post.
- Rights requests. When a user asks for their account to be deleted, we keep a record of the request and of how it was handled: date, account identity, and any reason given.
- Acceptance of the terms. The version of the terms of service and privacy policy you accepted, the date of acceptance and its origin (sign-up or renewed acceptance). No IP address or browser data is stored with it.
What we do not access. Neither your pages' private messages, nor your contact list, nor your LinkedIn connections, nor your YouTube channel's or TikTok account's data, nor your followers' personal data. Access tokens are encrypted before being stored.
03Legal bases
| Purpose | Legal basis |
|---|---|
| Providing the service and managing the account | Performance of a contract |
| Publishing to the agency's social media accounts and to the user's personal LinkedIn profile, YouTube channel and TikTok account | Performance of a contract |
| Connecting a Canva account and importing the designs the user chooses (optional) | Performance of a contract |
| Publishing reminders, morning email and calendar link | Performance of a contract |
| Getting-started guide and badges | Performance of a contract |
| Security, logging, abuse prevention | Legitimate interest |
| Measuring use of the service | Legitimate interest |
| Service-related notifications | Performance of a contract |
| Tracking the emails sent by the app | Legitimate interest |
| Newsletter to users | Legitimate interest. You can object at any time using the unsubscribe link in each newsletter |
| AI assistant: conversations, drafts and optional voice dictation | Performance of a contract |
| AI assistant usage tracking and reminder emails | Legitimate interest. You can object at any time using the unsubscribe link in each reminder, or by writing to hey@morepanache.com |
| Replying to suggestions and problem reports | Legitimate interest |
| Handling rights requests | Legal obligation |
| The user's content strategy | Performance of a contract |
| Keeping proof that the terms were accepted | Legitimate interest |
| Invoicing and accounting obligations | Legal obligation |
04Recipients and processors
We do not sell any data and never pass it on for advertising purposes. The following providers act on our behalf:
| Provider | Role | Hosting |
|---|---|---|
| Infomaniak | Hosting of the app, its database, its files and their backups; sending the service's emails | Switzerland |
| Meta Platforms | Publishing to Facebook and Instagram, audience measurement | Outside the European Union |
| Publishing to the user's personal profile, at their request | Ireland, with transfers outside the European Union | |
| Google (YouTube) | Publishing videos to the user's YouTube channel, at their request | Ireland, with transfers outside the European Union |
| TikTok | Publishing videos and photos to the user's TikTok account, at their request | Ireland, with transfers outside the European Union |
| Canva | Design service the user chooses to connect: it receives the authorisation and the requests to read and export the designs the user selects. We send it no content from the app | See Canva’s privacy policy |
| Anthropic | Text generation from the instructions entered by the user, ideas for the content strategy from the agency profile, and replies of the AI assistant from the conversation (messages, the user's first name, the agency's name and address, and what the assistant looks at: strategy, drafts, calendar, listings) | Outside the European Union |
| Pexels | Royalty-free image and video library. Searches and display go through our servers: Pexels receives only the keywords entered, with no personal data | Germany |
Voice dictation. If you use the assistant's microphone, your browser transcribes your voice with its own speech recognition service: Google for Chrome, Microsoft for Edge, Apple for Safari, and your device for Firefox. MOREpanache only receives the transcribed text, never the audio recording. This transcription is governed by your browser's terms.
Switzerland is recognised by the European Commission as providing an adequate level of protection. Transfers to the other providers rely on the European Commission's standard contractual clauses.
The people who run the service on behalf of MOREpanache (hosting, maintenance, support) may access data to the extent necessary, under its authority and bound by confidentiality.
When a user subscribes their own calendar (Google Calendar, Outlook, Apple Calendar…) to their personal calendar link, that service retrieves the title, date and text of their planned publications. The user chooses that service, which is governed by its own terms; we transmit nothing to it on our own initiative.
No payment provider is involved at this stage: subscriptions are invoiced directly by the publisher. Should a payment provider be introduced, this page will be updated before it goes live.
05Retention periods
| Data | Period |
|---|---|
| User account and associated content | For as long as the account is used. After 12 months without sign-in, a warning email is sent; without a new sign-in, the account is deleted 14 months after the last sign-in. When the subscription ends, content remains exportable for 30 days, then is deleted |
| Social media access tokens | Deleted as soon as the social account is disconnected or the user account is deleted. LinkedIn tokens also expire on their own after 60 days, after which the user is asked to reconnect. YouTube tokens are also revoked with Google when the channel is disconnected or the account deleted. TikTok access tokens are valid for 24 hours and renewed automatically with the refresh token, which TikTok limits to one year; they are revoked with TikTok when the account is disconnected or the user account deleted |
| Canva connection | Until the user disconnects Canva (“My account”) or deletes their account: the token is then revoked with Canva and permanently deleted. Images and videos already imported stay with the user’s drafts and library, according to their own retention periods |
| Persistent sign-in tokens | 60 days, renewed at each visit; deleted at sign-out, when the password changes or when the account is deleted |
| Publishing reminders, calendar preferences, guide and badges | For as long as the account exists; deleted with it. The calendar link only shows the last 30 days and upcoming publications |
| Temporary copies of visuals exposed for publishing | A few minutes, purged automatically once the network has retrieved them (one hour at most) |
| Publishing statistics | 3 years |
| Activity logs | 12 months |
| Usage statistics | Linked to the account for 13 months, then to the agency only; deleted after 10 years |
| Support messages | 12 months |
| Rights requests | 3 years after they are closed |
| Content strategy | For as long as the user is attached to the agency. If they delete their account or leave the agency, the strategy is kept with no link to them: their account number and identifier are erased, as are the agency name, city, neighbourhoods and the text of the ideas. Only the agency concerned, its region and the choices useful for internal statistics on the use of the feature are kept; nobody can see it in the app any more. Archived ideas are deleted 24 months after being archived |
| Files sent to the video rendering service | Source files deleted as soon as the video is produced, and at most 24 hours after being sent; job records deleted after 7 days |
| Proof of acceptance of the terms | For as long as the account exists; deleted with it |
| Log of emails sent by the app | 13 months (recipient address, message type, date and result of the sending, without the content). When an account is deleted, the address is replaced with “deleted account” |
| Follow-up of newsletter sends | 13 months after sending (address, status, reason for any failure), then deleted; only each newsletter's totals, with no personal data, are kept. When an account is deleted, the address is erased from the follow-up. Unsubscription is kept as long as the account exists |
| Conversations with the AI assistant | 30 days after the last activity. They are erased at once if you click “New conversation” or if your account is deleted |
| AI assistant usage tracking and reminders | No time limit, without the content of your conversations; made anonymous when your account is deleted |
| Backups | 30 days, with a secondary copy on a second Infomaniak hosting service in Switzerland. A deleted item disappears from backups 37 days later at the latest |
| Accounting records | 10 years (legal obligation) |
06Publishing visuals
For a visual or a video to be published to Facebook, Instagram or TikTok, that network's servers must download it themselves. A temporary copy is therefore made available on our domain, under a random, non-guessable file name, for the duration of the upload — a few minutes, one hour at most for TikTok. That copy is deleted as soon as publishing succeeds or fails. The original remains privately stored. For LinkedIn and YouTube, our server sends the visual or the video directly: no temporary copy is exposed.
Videos (slideshows, videos with music or animated text) are assembled by a rendering service that runs on the same Infomaniak server as the app. The photos and videos of a post are passed to it for assembly; no data leaves that server. Source files are deleted as soon as the video is produced.
07Withdrawing the Facebook, LinkedIn, YouTube, TikTok or Canva authorisation
Disconnecting a social account from within the app permanently deletes the access tokens we hold: we can then no longer publish or read anything.
The authorisation nonetheless remains recorded in the account holder's Facebook settings, which only they can change, under Settings & privacy › Settings › Business integrations.
The LinkedIn connection is removed from the My account page of the app. The user can also withdraw the authorisation given to Sow Social from their LinkedIn settings, under Data privacy › Other applications › Permitted services.
The YouTube connection is removed from the My account page of the app: we then revoke the authorisation with Google and delete the tokens. The user can also withdraw it at any time from their Google Account, on the third-party apps and services page (security.google.com/settings/security/permissions).
The TikTok connection is removed from the My account page of the app: we then revoke the authorisation with TikTok and delete the tokens. The user can also withdraw it at any time from the TikTok app, under Settings and privacy › Security & permissions › Apps and services permissions. Posts already published remain on their TikTok account; only they can delete them there.
The Canva connection is removed from the My account page of the app: we then revoke the authorisation with Canva and delete the tokens. The user can also remove the app’s access from their Canva account settings. Designs already imported remain in the user’s drafts and library in Sow Social; nothing is changed in Canva.
08YouTube API Services and Google user data
Publishing to YouTube uses the YouTube API Services. By connecting their channel, the user agrees to be bound by the YouTube Terms of Service. Data passed to YouTube is also processed under the Google Privacy Policy.
Sow Social's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular, this data is used only to publish the videos the user asks us to publish; it is never sold, never used for advertising, never used to train artificial intelligence models, and never read by a human except with the user's consent, for security purposes or to comply with the law.
09TikTok
Publishing to TikTok uses TikTok's Login Kit and Content Posting API. By connecting their account, the user agrees to be bound by the TikTok Terms of Service; data passed to TikTok is processed under the TikTok Privacy Policy. Before each post, the user chooses who can view it and which interactions are allowed, with no option preselected, and declares any commercial content; by publishing, they accept TikTok's Music Usage Confirmation and, for branded content, its Branded Content Policy.
Data received from TikTok is used only to show the user which account they are publishing to and to publish the content they ask us to publish, now or at the time they scheduled. It is never sold, never used for advertising, never used to train artificial intelligence models, and never shared with anyone other than TikTok.
10Reminders, morning email and calendar link
On days when a manual publication is planned, the user receives an email at around 8 a.m. listing the publications of the day and those still pending. No email is sent on other days. The email can be turned off at any time from the My account page.
The personal calendar link lets the user display their publications in the calendar of their choice. It works without signing in and is protected by a random key: anyone who has the link can see the planned publications. The user can create a new link at any time from My account; the previous one then stops working. Publishing from a reminder always requires signing in to the app.
11Newsletter
MOREpanache may send users a newsletter, written by its administrators, to inform them of the service's news and how best to use it. It contains no advertising for third parties.
It is sent from hey@morepanache.com, by Infomaniak (see §04). It is sent only to accounts whose email address has been verified, once per address, and never to an account that has unsubscribed or whose deletion has been requested.
Each newsletter contains an “Unsubscribe” link, and your mail client may offer one-click unsubscription. Unsubscription is immediate and requires no sign-in. To subscribe again, write to hey@morepanache.com.
We use no tracking pixel: we measure neither whether the newsletter is opened nor each recipient's clicks.
12Your rights
You have the right to access, rectify, erase, restrict, object to the processing of, and port your data. You can exercise these rights at hey@morepanache.com. We respond within one month.
To delete your account and all associated data, request it from the My account page in the app, or follow the procedure described on the Data deletion page. You will receive an acknowledgement, then a confirmation once the deletion has been carried out.
You may lodge a complaint with a data protection authority. As the publisher is established in the Netherlands, the lead authority is the Autoriteit Persoonsgegevens. If you reside in another EU member state, you may equally contact your own country's authority: the Regulation leaves that choice to you.
13Security
Traffic is encrypted over HTTPS. Social media access tokens are encrypted before storage. Persistent sign-in tokens are stored only as fingerprints and are replaced at each sign-in. Passwords are stored as non-reversible hashes. Access to an agency's data is restricted to the members of that agency.
14Cookies
The app uses only cookies that are strictly necessary for the service to work. They serve no analytics or advertising purpose, and therefore require no prior consent.
| Cookie | Role | Duration |
|---|---|---|
| Session | Keeps the user signed in during their visit | Until the browser is closed |
| Persistent sign-in | Keeps the user signed in on this device between visits | 60 days, renewed at each visit; deleted at sign-out |
No other cookie is set.
The app's fonts are hosted on our own servers: displaying them involves no connection to any third-party service.
15Changes
This policy may change. The date at the top of the page indicates the version in force. For a significant change, the app informs you the next time you sign in and invites you to read the new version.
