Duo Dev Technologies
Ripple Privacy Policy
Ripple
- Version
- 1.0
- Effective
- 5 November 2026
- Source
- legal.duodev.in/products/ripple/privacy-policy
1. Who is responsible for your data
This Privacy Policy explains how Duo Dev Technologies ("we", "us", "our") collects, uses, stores and shares personal data when you use Ripple (the "Service"), a web application for managing social media accounts, available at https://ripple.duodev.in. It also covers our public website pages (landing page, blog and contact form).
Ripple is part of the duodev family of products. You sign in with your duodev account, which is run by duodev at accounts.duodev.in.
The data controller is:
- Duo Dev Technologies
- Registered address: 2/45, JJ Colony, Near Common Service Centre, Mettupattithathanur, Salem, Tamil Nadu - 636103, India
- GSTIN 33AAWFD9000D1ZM
- Contact for privacy questions: support@duodev.in
- Grievance Officer (India, Digital Personal Data Protection Act 2023): Hariharan K, grievance@duodev.in, +91 94876 90260, 2/45, JJ Colony, Near Common Service Centre, Mettupattithathanur, Salem, Tamil Nadu - 636103, India
When you connect a social media account belonging to an organisation (for example a company Facebook Page), the organisation that uses Ripple decides what to publish and manage. For the content and connected-account data that an organisation manages in Ripple, we act as that organisation's processor: we process it only on the organisation's instructions and only to provide the Service. We are the controller of your account data and of the data we need to run, secure and bill the Service. Organisations can ask for a Data Processing Agreement at support@duodev.in.
Ripple is part of the duodev family of products. You sign in with your duodev account, which is run by duodev at accounts.duodev.in.
The data controller is:
- Duo Dev Technologies
- Registered address: 2/45, JJ Colony, Near Common Service Centre, Mettupattithathanur, Salem, Tamil Nadu - 636103, India
- GSTIN 33AAWFD9000D1ZM
- Contact for privacy questions: support@duodev.in
- Grievance Officer (India, Digital Personal Data Protection Act 2023): Hariharan K, grievance@duodev.in, +91 94876 90260, 2/45, JJ Colony, Near Common Service Centre, Mettupattithathanur, Salem, Tamil Nadu - 636103, India
When you connect a social media account belonging to an organisation (for example a company Facebook Page), the organisation that uses Ripple decides what to publish and manage. For the content and connected-account data that an organisation manages in Ripple, we act as that organisation's processor: we process it only on the organisation's instructions and only to provide the Service. We are the controller of your account data and of the data we need to run, secure and bill the Service. Organisations can ask for a Data Processing Agreement at support@duodev.in.
2. Summary
- You sign in with your duodev account. We receive your name, email address and profile picture from it.
- You can connect social media accounts (Facebook, Instagram, YouTube, X, LinkedIn, TikTok, Pinterest, Threads, Bluesky, Mastodon and Google Business Profile) to an organisation in Ripple. We store the access tokens those platforms give us, encrypted, so that Ripple can act on your behalf.
- We read your posts, comments and statistics from those platforms when you open them in Ripple. We do not keep copies of them, apart from short-lived caches described below.
- We store posts you schedule until they are published.
- We do not sell your data and we do not use it for advertising.
- Contact form messages and support tickets are handled by DD Management, another duodev service.
- You can connect social media accounts (Facebook, Instagram, YouTube, X, LinkedIn, TikTok, Pinterest, Threads, Bluesky, Mastodon and Google Business Profile) to an organisation in Ripple. We store the access tokens those platforms give us, encrypted, so that Ripple can act on your behalf.
- We read your posts, comments and statistics from those platforms when you open them in Ripple. We do not keep copies of them, apart from short-lived caches described below.
- We store posts you schedule until they are published.
- We do not sell your data and we do not use it for advertising.
- Contact form messages and support tickets are handled by DD Management, another duodev service.
3. Data we collect and where it comes from
3.1 Account data (from your duodev account)
When you sign in, accounts.duodev.in tells us:
- your duodev user ID,
- your name,
- your email address,
- your profile picture (avatar) URL.
We store these in our user database and update them each time you sign in. Your duodev password is never shared with us.
3.2 Organisation and membership data (from you)
- organisation name and a URL-friendly short name (slug),
- which users belong to each organisation and their role (owner, admin, developer or member),
- which organisation you last selected.
Organisations are workspaces of your duodev account (accounts.duodev.in): their name, members and roles are managed there and Ripple keeps a copy that it refreshes while you use it. Logo, accent colour and timezone are stored by Ripple.
3.3 Connected social account data (from the platform you connect)
When an owner, admin or developer connects a social account, the platform sends us:
- an access token and, for some platforms, a refresh token and their expiry time;
- the ID of the connected account on that platform;
- basic profile information: display name or username, profile picture URL, and for some platforms public counts (see section 5);
- the list of permissions (scopes) you granted.
We store these against the organisation, together with the connection status, the date it was connected or disconnected, and any error message returned by the platform.
3.4 Content you create in Ripple
- Scheduled posts: when you schedule an Instagram post or reel (or queue one that the platform must process), we store the caption, alt text, the URLs of the images or videos, the type of post, the target account, the scheduled time, its status, the ID of the published post and any error. We also record which user created it.
- Files you upload to publish on Facebook (photos or videos) are sent directly to Facebook. We do not keep a permanent copy.
- Comment replies, post edits and deletions you make in Ripple are sent to the platform. We do not keep a copy.
- AI assist (optional, off by default): an organisation owner or admin can turn on AI assist under Organisation settings. While it is on, when a member clicks an AI assist action (rewrite a caption, suggest hashtags, translate, or generate image alt text), we send only the caption text or the one image being worked on (resized, with camera and location metadata removed), and our instructions, to our AI provider (see section 9). We never send access tokens, account or member identifiers, names or email addresses, inbox messages or data read from the social platforms. Suggestions are shown to the member, who decides whether to use them; nothing is posted automatically. We do not store the prompts or the AI responses; we keep an audit log entry recording who used which AI action and how many credits it used, without the content.
3.5 Data read from platforms while you use the Service
When you open a page in Ripple, we fetch data live from the platform's API and display it to you. This can include posts, comments, reactions, statistics and information about other people (for example the names of people who commented on your post). See section 5 for each platform. This data is not stored in our database. Some lists are cached for a few minutes (see section 8).
3.6 Contact form (public website)
When you send a message through our contact form we collect your name, email address, subject and message, plus your IP address, browser user agent and the page you sent it from. These are passed to DD Management (see section 9). Your IP address is also used for a short time to limit abuse (rate limiting).
3.7 Support tickets
When you open a support ticket from inside Ripple, we send DD Management your user ID, name, email address, current organisation ID and name, your subject, message, priority, category, any attachments (images or PDF files), your IP address and browser user agent. Replies and attachments on the ticket are stored by DD Management. Ripple shows you only your own tickets.
3.8 Technical data
- Session data: a session record on our servers (our cache database) containing a session ID, your user ID, IP address, browser user agent, last activity time and session contents (for example sign-in tokens from accounts.duodev.in and temporary security values used while connecting a platform).
- Server logs: error and activity logs, which may include your user ID, platform name, error messages and, depending on configuration, information about your duodev account.
- Background job records: when a scheduled post is published, a job record is created; failed jobs are kept for troubleshooting.
- Audit log: for each organisation we record important actions (for example connecting or disconnecting a platform, publishing, scheduling, rescheduling or cancelling posts, approval decisions, brand, template and media library changes, data exports and deletion requests). Each entry stores who did it (your user ID and name at the time), what was done and to which item, the time, your IP address and your browser user agent (browser and operating system). Actions performed automatically by Ripple are recorded as "System" without an IP address. Owners and admins of the organisation can view the audit log and export it as a CSV file; it is included in the organisation's data export.
We do not use analytics or advertising trackers.
When you sign in, accounts.duodev.in tells us:
- your duodev user ID,
- your name,
- your email address,
- your profile picture (avatar) URL.
We store these in our user database and update them each time you sign in. Your duodev password is never shared with us.
3.2 Organisation and membership data (from you)
- organisation name and a URL-friendly short name (slug),
- which users belong to each organisation and their role (owner, admin, developer or member),
- which organisation you last selected.
Organisations are workspaces of your duodev account (accounts.duodev.in): their name, members and roles are managed there and Ripple keeps a copy that it refreshes while you use it. Logo, accent colour and timezone are stored by Ripple.
3.3 Connected social account data (from the platform you connect)
When an owner, admin or developer connects a social account, the platform sends us:
- an access token and, for some platforms, a refresh token and their expiry time;
- the ID of the connected account on that platform;
- basic profile information: display name or username, profile picture URL, and for some platforms public counts (see section 5);
- the list of permissions (scopes) you granted.
We store these against the organisation, together with the connection status, the date it was connected or disconnected, and any error message returned by the platform.
3.4 Content you create in Ripple
- Scheduled posts: when you schedule an Instagram post or reel (or queue one that the platform must process), we store the caption, alt text, the URLs of the images or videos, the type of post, the target account, the scheduled time, its status, the ID of the published post and any error. We also record which user created it.
- Files you upload to publish on Facebook (photos or videos) are sent directly to Facebook. We do not keep a permanent copy.
- Comment replies, post edits and deletions you make in Ripple are sent to the platform. We do not keep a copy.
- AI assist (optional, off by default): an organisation owner or admin can turn on AI assist under Organisation settings. While it is on, when a member clicks an AI assist action (rewrite a caption, suggest hashtags, translate, or generate image alt text), we send only the caption text or the one image being worked on (resized, with camera and location metadata removed), and our instructions, to our AI provider (see section 9). We never send access tokens, account or member identifiers, names or email addresses, inbox messages or data read from the social platforms. Suggestions are shown to the member, who decides whether to use them; nothing is posted automatically. We do not store the prompts or the AI responses; we keep an audit log entry recording who used which AI action and how many credits it used, without the content.
3.5 Data read from platforms while you use the Service
When you open a page in Ripple, we fetch data live from the platform's API and display it to you. This can include posts, comments, reactions, statistics and information about other people (for example the names of people who commented on your post). See section 5 for each platform. This data is not stored in our database. Some lists are cached for a few minutes (see section 8).
3.6 Contact form (public website)
When you send a message through our contact form we collect your name, email address, subject and message, plus your IP address, browser user agent and the page you sent it from. These are passed to DD Management (see section 9). Your IP address is also used for a short time to limit abuse (rate limiting).
3.7 Support tickets
When you open a support ticket from inside Ripple, we send DD Management your user ID, name, email address, current organisation ID and name, your subject, message, priority, category, any attachments (images or PDF files), your IP address and browser user agent. Replies and attachments on the ticket are stored by DD Management. Ripple shows you only your own tickets.
3.8 Technical data
- Session data: a session record on our servers (our cache database) containing a session ID, your user ID, IP address, browser user agent, last activity time and session contents (for example sign-in tokens from accounts.duodev.in and temporary security values used while connecting a platform).
- Server logs: error and activity logs, which may include your user ID, platform name, error messages and, depending on configuration, information about your duodev account.
- Background job records: when a scheduled post is published, a job record is created; failed jobs are kept for troubleshooting.
- Audit log: for each organisation we record important actions (for example connecting or disconnecting a platform, publishing, scheduling, rescheduling or cancelling posts, approval decisions, brand, template and media library changes, data exports and deletion requests). Each entry stores who did it (your user ID and name at the time), what was done and to which item, the time, your IP address and your browser user agent (browser and operating system). Actions performed automatically by Ripple are recorded as "System" without an IP address. Owners and admins of the organisation can view the audit log and export it as a CSV file; it is included in the organisation's data export.
We do not use analytics or advertising trackers.
4. Why we use your data and our legal bases (GDPR)
| Purpose | Data | Legal basis (GDPR Art. 6) |
|---|---|---|
| Sign you in and run your account | Account data, session data | Contract (6(1)(b)) |
| Organisations, roles and access control | Organisation and membership data | Contract (6(1)(b)) |
| Connect social accounts and act on your behalf (read, publish, reply, moderate, show statistics) | Connected account data, content, platform data | Contract (6(1)(b)); for data about other people shown from the platforms (e.g. commenters): our and our customers' legitimate interests in managing their social presence (6(1)(f)) |
| Publish scheduled posts | Scheduled posts | Contract (6(1)(b)) |
| Answer contact messages | Contact form data | Legitimate interests in replying to enquiries (6(1)(f)); steps before a contract (6(1)(b)) |
| Provide support | Support ticket data | Contract (6(1)(b)) |
| Keep the Service secure, prevent abuse, fix errors | Technical data, IP address | Legitimate interests in security (6(1)(f)) |
| Audit log: let organisation owners and admins see who did what, investigate mistakes and misuse | Audit log entries (user ID and name, action, item, time, IP address, browser user agent) | Legitimate interests in accountability and security of the organisation's accounts (6(1)(f)) |
| AI assist (only when the organisation turns it on): suggest caption rewrites, hashtags, translations and image alt text | The caption text or image a member submits to AI assist | Performance of our contract with the organisation, at the member's request (6(1)(b)); any personal data inside the caption or image is processed only to produce the suggestion |
| Comply with the law | Any, as required | Legal obligation (6(1)(c)) |
We do not make decisions about you based solely on automated processing.
5. Data we access on each social platform
You choose which platforms to connect. Only organisation owners, admins and developers can connect or disconnect accounts. The platform shows you the permissions we ask for and you can decline. The permissions listed below are the ones Ripple requests by default; an administrator of our service may change them in the platform settings.
5.1 Facebook (Meta)
Permissions requested: public_profile, pages_show_list, pages_read_engagement, pages_read_user_content, pages_manage_posts, pages_manage_engagement, read_insights.
What we access and why:
- Your Facebook user ID, name and profile picture: to identify the connected account.
- The Facebook Pages you manage, including Page name, category, description, website, profile and cover pictures, follower and fan counts, username, location, public phone and email, and a Page access token: to let you choose and manage a Page.
- Page posts (published and scheduled), posts by visitors and posts the Page is tagged in, comments and reactions (including the names and profile pictures of the people who wrote or reacted): to show your feed and let you moderate.
- Page and post statistics (insights): to show analytics.
- Creating, editing and deleting posts, photos, videos and reels; replying to, hiding, unhiding and deleting comments: only when you do so in Ripple.
5.2 Instagram (Meta)
Instagram accounts are connected through Facebook Login and must be Instagram Business or Creator accounts linked to a Facebook Page.
Permissions requested: instagram_basic, instagram_content_publish, instagram_manage_comments, instagram_manage_insights, pages_show_list, pages_read_engagement, business_management.
What we access and why:
- Your Instagram professional accounts: ID, username, name, profile picture, biography, website, follower, following and media counts.
- Your media and stories (images, videos, captions, links, like and comment counts), comments on your media, and media in which your account is mentioned or tagged.
- Account and media statistics (insights).
- Public media for hashtags you search, and public profile information of other business or creator accounts you look up (business discovery).
- Publishing images, reels and carousels; replying to, hiding and deleting comments: only when you do so in Ripple.
Instagram Login (second way to connect). Instagram professional accounts that are not linked to a Facebook Page can be connected by signing in with Instagram (Instagram API with Instagram Login). Permissions requested: instagram_business_basic, instagram_business_content_publish, instagram_business_manage_comments, instagram_business_manage_messages, instagram_business_manage_insights. We read the account's ID, username, name, account type, profile picture and follower, following and media counts, its media, comments and direct messages (for the inbox) and account and media statistics, and we publish and moderate only when you do so in Ripple. Hashtag search, business discovery and tagged media are not available for these accounts. Deletion requests from Instagram are handled like those from Facebook (section 4 of the data deletion page).
5.3 YouTube (Google)
Permissions requested: https://www.googleapis.com/auth/youtube.readonly, https://www.googleapis.com/auth/youtube.upload, https://www.googleapis.com/auth/youtube.force-ssl, https://www.googleapis.com/auth/yt-analytics.readonly.
What we access and why: when you connect, we read your channel ID, title, custom URL, thumbnail, subscriber count and video count, to identify the connected channel and show it in Ripple. When you use these features in Ripple, we also list your videos and playlists; upload the videos and thumbnails you choose (with their title, description, privacy setting and scheduled publishing time); edit or delete videos and playlists; read, reply to, moderate and delete comments; and show channel statistics from YouTube Analytics.
Ripple uses YouTube API Services. By connecting a YouTube channel you agree to be bound by the YouTube Terms of Service. Google's handling of your data is described in the Google Privacy Policy. See section 6 for our Google API commitments.
5.4 X (formerly Twitter)
Permissions requested: tweet.read, tweet.write, users.read, media.write, like.read, offline.access.
What we access and why: when you connect, we read your X user ID, name, username, profile picture, verified status and public metrics (such as follower count), to identify the connected account. offline.access lets us keep the connection active without asking you to sign in again. When you use these features in Ripple, we read your timeline, your posts and your mentions; publish the posts and threads you create or schedule (with images, a GIF or video, or a poll); delete them; like, repost or reply when you ask us to; and show statistics for your own recent posts.
5.5 LinkedIn
Permissions requested: openid, profile, email, w_member_social.
What we access and why: when you connect, we read your LinkedIn member ID, name, profile picture and email address, to identify the connected account. w_member_social allows posting on your behalf: Ripple publishes, edits and deletes the posts you create or schedule as your member profile (text, articles, images, video and documents) and their comments. LinkedIn does not let Ripple read your other member posts, so Ripple lists only the posts published through it.
LinkedIn Pages (company Pages, Community Management API). Permissions requested: r_basicprofile, r_organization_social, w_organization_social, rw_organization_admin, r_organization_social_feed, w_organization_social_feed. We read your member ID and name, the company Pages you administer and your role on them, the Pages' posts, comments on those posts and Page, follower and post statistics, and we post, comment and delete as the Page only when you do so in Ripple. Comments by LinkedIn members are kept in the inbox for at most 48 hours; we do not fetch or store the commenters' profiles. Daily Page statistics are kept for one year.
5.6 TikTok
Permissions requested: user.info.basic, user.info.profile, user.info.stats, video.list, video.upload, video.publish.
What we access and why: when you connect, we read your TikTok open ID, union ID, display name and avatar, to identify the connected account. When you use these features in Ripple, we read your profile statistics and your videos with their counts, and publish the videos or photo posts you create (or upload them to your TikTok inbox as drafts), with the privacy and interaction settings you choose.
5.7 Pinterest
Permissions requested: user_accounts:read, boards:read, boards:write, pins:read, pins:write.
What we access and why: when you connect, we read your Pinterest user ID, username, business name and profile image, to identify the connected account. When you use these features in Ripple, we list and manage your boards and board sections; create, edit, delete and save the pins you create (images, carousels and videos); and show account and pin statistics (business accounts).
5.8 Threads (Meta)
Permissions requested: threads_basic, threads_content_publish, threads_read_replies, threads_manage_replies, threads_manage_insights, threads_manage_mentions, threads_delete.
What we access and why: your Threads user ID, username, name, profile picture and follower count, to identify the connected account; your posts and their statistics, replies and mentions (for the post pages and the inbox); and account statistics. We publish the posts you create or schedule (text, links, images, videos and carousels), reply, hide replies and delete your posts only when you do so in Ripple.
5.9 Bluesky
Permissions requested: atproto, transition:generic (Bluesky's OAuth; no app registration).
What we access and why: your Bluesky handle, DID (account identifier), display name, avatar and follower, follows and post counts, to identify the connected account; your posts, replies, mentions and quotes (for the post pages and the inbox); and the likes, reposts, replies and quotes of your own posts (for statistics). We publish the posts you create or schedule (text, links, up to 4 images or a video) and reply or delete your posts only when you do so in Ripple. The Bluesky search you set up in Listening runs through your connected account.
5.10 Mastodon
Permissions requested: profile, read:statuses, read:notifications, write:statuses, write:media (read:accounts instead of profile on older servers). Ripple registers itself as an app on your Mastodon server when you connect.
What we access and why: your account ID, username, display name, avatar and follower counts on your server, and the server's posting limits, to identify the account and respect its limits; your posts, replies and mentions, including private (direct) mentions, for the post pages and the inbox; and the favourites, boosts, replies and quotes of your own posts (for statistics). We publish the posts you create or schedule (with visibility, content warning, language and media) and reply or delete your posts only when you do so in Ripple. The hashtag searches you set up in Listening run through your connected account.
5.11 Google Business Profile
Permissions requested: openid, profile, business.manage.
What we access and why: your Google account ID, name and profile picture, to identify the connected account; the business locations you manage, with their name, rating and statistics (profile views, calls, website clicks, direction requests and bookings); and the reviews of those locations, including the reviewers' names and comments, for the inbox. We publish, and delete, the posts you create for a location (updates, events and offers with one photo), and reply to, edit or delete replies to reviews only when you do so in Ripple. Google's handling of your data is described in the Google Privacy Policy.
5.12 What we never do with platform data
- We do not sell platform data or share it with advertisers, data brokers or information resellers.
- We do not use it to serve ads, to build profiles for advertising, or to decide creditworthiness.
- We only use it to provide the Ripple features you use.
- We do not use it to train artificial intelligence or machine learning models.
5.1 Facebook (Meta)
Permissions requested: public_profile, pages_show_list, pages_read_engagement, pages_read_user_content, pages_manage_posts, pages_manage_engagement, read_insights.
What we access and why:
- Your Facebook user ID, name and profile picture: to identify the connected account.
- The Facebook Pages you manage, including Page name, category, description, website, profile and cover pictures, follower and fan counts, username, location, public phone and email, and a Page access token: to let you choose and manage a Page.
- Page posts (published and scheduled), posts by visitors and posts the Page is tagged in, comments and reactions (including the names and profile pictures of the people who wrote or reacted): to show your feed and let you moderate.
- Page and post statistics (insights): to show analytics.
- Creating, editing and deleting posts, photos, videos and reels; replying to, hiding, unhiding and deleting comments: only when you do so in Ripple.
5.2 Instagram (Meta)
Instagram accounts are connected through Facebook Login and must be Instagram Business or Creator accounts linked to a Facebook Page.
Permissions requested: instagram_basic, instagram_content_publish, instagram_manage_comments, instagram_manage_insights, pages_show_list, pages_read_engagement, business_management.
What we access and why:
- Your Instagram professional accounts: ID, username, name, profile picture, biography, website, follower, following and media counts.
- Your media and stories (images, videos, captions, links, like and comment counts), comments on your media, and media in which your account is mentioned or tagged.
- Account and media statistics (insights).
- Public media for hashtags you search, and public profile information of other business or creator accounts you look up (business discovery).
- Publishing images, reels and carousels; replying to, hiding and deleting comments: only when you do so in Ripple.
Instagram Login (second way to connect). Instagram professional accounts that are not linked to a Facebook Page can be connected by signing in with Instagram (Instagram API with Instagram Login). Permissions requested: instagram_business_basic, instagram_business_content_publish, instagram_business_manage_comments, instagram_business_manage_messages, instagram_business_manage_insights. We read the account's ID, username, name, account type, profile picture and follower, following and media counts, its media, comments and direct messages (for the inbox) and account and media statistics, and we publish and moderate only when you do so in Ripple. Hashtag search, business discovery and tagged media are not available for these accounts. Deletion requests from Instagram are handled like those from Facebook (section 4 of the data deletion page).
5.3 YouTube (Google)
Permissions requested: https://www.googleapis.com/auth/youtube.readonly, https://www.googleapis.com/auth/youtube.upload, https://www.googleapis.com/auth/youtube.force-ssl, https://www.googleapis.com/auth/yt-analytics.readonly.
What we access and why: when you connect, we read your channel ID, title, custom URL, thumbnail, subscriber count and video count, to identify the connected channel and show it in Ripple. When you use these features in Ripple, we also list your videos and playlists; upload the videos and thumbnails you choose (with their title, description, privacy setting and scheduled publishing time); edit or delete videos and playlists; read, reply to, moderate and delete comments; and show channel statistics from YouTube Analytics.
Ripple uses YouTube API Services. By connecting a YouTube channel you agree to be bound by the YouTube Terms of Service. Google's handling of your data is described in the Google Privacy Policy. See section 6 for our Google API commitments.
5.4 X (formerly Twitter)
Permissions requested: tweet.read, tweet.write, users.read, media.write, like.read, offline.access.
What we access and why: when you connect, we read your X user ID, name, username, profile picture, verified status and public metrics (such as follower count), to identify the connected account. offline.access lets us keep the connection active without asking you to sign in again. When you use these features in Ripple, we read your timeline, your posts and your mentions; publish the posts and threads you create or schedule (with images, a GIF or video, or a poll); delete them; like, repost or reply when you ask us to; and show statistics for your own recent posts.
5.5 LinkedIn
Permissions requested: openid, profile, email, w_member_social.
What we access and why: when you connect, we read your LinkedIn member ID, name, profile picture and email address, to identify the connected account. w_member_social allows posting on your behalf: Ripple publishes, edits and deletes the posts you create or schedule as your member profile (text, articles, images, video and documents) and their comments. LinkedIn does not let Ripple read your other member posts, so Ripple lists only the posts published through it.
LinkedIn Pages (company Pages, Community Management API). Permissions requested: r_basicprofile, r_organization_social, w_organization_social, rw_organization_admin, r_organization_social_feed, w_organization_social_feed. We read your member ID and name, the company Pages you administer and your role on them, the Pages' posts, comments on those posts and Page, follower and post statistics, and we post, comment and delete as the Page only when you do so in Ripple. Comments by LinkedIn members are kept in the inbox for at most 48 hours; we do not fetch or store the commenters' profiles. Daily Page statistics are kept for one year.
5.6 TikTok
Permissions requested: user.info.basic, user.info.profile, user.info.stats, video.list, video.upload, video.publish.
What we access and why: when you connect, we read your TikTok open ID, union ID, display name and avatar, to identify the connected account. When you use these features in Ripple, we read your profile statistics and your videos with their counts, and publish the videos or photo posts you create (or upload them to your TikTok inbox as drafts), with the privacy and interaction settings you choose.
5.7 Pinterest
Permissions requested: user_accounts:read, boards:read, boards:write, pins:read, pins:write.
What we access and why: when you connect, we read your Pinterest user ID, username, business name and profile image, to identify the connected account. When you use these features in Ripple, we list and manage your boards and board sections; create, edit, delete and save the pins you create (images, carousels and videos); and show account and pin statistics (business accounts).
5.8 Threads (Meta)
Permissions requested: threads_basic, threads_content_publish, threads_read_replies, threads_manage_replies, threads_manage_insights, threads_manage_mentions, threads_delete.
What we access and why: your Threads user ID, username, name, profile picture and follower count, to identify the connected account; your posts and their statistics, replies and mentions (for the post pages and the inbox); and account statistics. We publish the posts you create or schedule (text, links, images, videos and carousels), reply, hide replies and delete your posts only when you do so in Ripple.
5.9 Bluesky
Permissions requested: atproto, transition:generic (Bluesky's OAuth; no app registration).
What we access and why: your Bluesky handle, DID (account identifier), display name, avatar and follower, follows and post counts, to identify the connected account; your posts, replies, mentions and quotes (for the post pages and the inbox); and the likes, reposts, replies and quotes of your own posts (for statistics). We publish the posts you create or schedule (text, links, up to 4 images or a video) and reply or delete your posts only when you do so in Ripple. The Bluesky search you set up in Listening runs through your connected account.
5.10 Mastodon
Permissions requested: profile, read:statuses, read:notifications, write:statuses, write:media (read:accounts instead of profile on older servers). Ripple registers itself as an app on your Mastodon server when you connect.
What we access and why: your account ID, username, display name, avatar and follower counts on your server, and the server's posting limits, to identify the account and respect its limits; your posts, replies and mentions, including private (direct) mentions, for the post pages and the inbox; and the favourites, boosts, replies and quotes of your own posts (for statistics). We publish the posts you create or schedule (with visibility, content warning, language and media) and reply or delete your posts only when you do so in Ripple. The hashtag searches you set up in Listening run through your connected account.
5.11 Google Business Profile
Permissions requested: openid, profile, business.manage.
What we access and why: your Google account ID, name and profile picture, to identify the connected account; the business locations you manage, with their name, rating and statistics (profile views, calls, website clicks, direction requests and bookings); and the reviews of those locations, including the reviewers' names and comments, for the inbox. We publish, and delete, the posts you create for a location (updates, events and offers with one photo), and reply to, edit or delete replies to reviews only when you do so in Ripple. Google's handling of your data is described in the Google Privacy Policy.
5.12 What we never do with platform data
- We do not sell platform data or share it with advertisers, data brokers or information resellers.
- We do not use it to serve ads, to build profiles for advertising, or to decide creditworthiness.
- We only use it to provide the Ripple features you use.
- We do not use it to train artificial intelligence or machine learning models.
6. Google API Services: Limited Use
Ripple'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:
- we only use data from Google APIs to provide or improve user-facing features that are prominent in Ripple;
- we only transfer it to others when needed to provide those features with your consent, for security purposes, to comply with the law, or as part of a merger, acquisition or sale of assets with your explicit prior consent;
- our staff do not read this data unless you have agreed to it for specific data, it is necessary for security (for example investigating abuse or a bug), it is necessary to comply with the law, or it is aggregated and used for internal operations in line with applicable law;
- we do not transfer or sell it to advertising platforms, data brokers or information resellers, and we do not use it for advertising or to determine creditworthiness or for lending.
Revoking access: in addition to disconnecting YouTube in Ripple, you can revoke Ripple's access to your Google data at any time on the Google security settings page: https://security.google.com/settings/security/permissions.
- we only use data from Google APIs to provide or improve user-facing features that are prominent in Ripple;
- we only transfer it to others when needed to provide those features with your consent, for security purposes, to comply with the law, or as part of a merger, acquisition or sale of assets with your explicit prior consent;
- our staff do not read this data unless you have agreed to it for specific data, it is necessary for security (for example investigating abuse or a bug), it is necessary to comply with the law, or it is aggregated and used for internal operations in line with applicable law;
- we do not transfer or sell it to advertising platforms, data brokers or information resellers, and we do not use it for advertising or to determine creditworthiness or for lending.
Revoking access: in addition to disconnecting YouTube in Ripple, you can revoke Ripple's access to your Google data at any time on the Google security settings page: https://security.google.com/settings/security/permissions.
7. How we store and protect your data
- Encryption of tokens: platform access tokens and refresh tokens are encrypted before they are stored in our database (AES-256 using the application's encryption key). The OAuth client secrets Ripple uses to talk to each platform are also encrypted at rest.
- Encryption in transit: the Service is served over HTTPS, and all calls to the social platforms, accounts.duodev.in and DD Management use HTTPS.
- Access control: only members of an organisation can see that organisation's connected accounts; only owners, admins and developers can connect or disconnect them. Tokens are never sent to your browser.
- Connection security: platform connections use the OAuth state parameter and, where supported (YouTube, X), PKCE, to prevent request forgery.
- Rate limiting on sign-in, contact and support forms.
- Backups: the database and uploaded files are backed up every night into archives encrypted with AES-256, stored on our server in India. Backups are kept as 7 daily, 4 weekly and 6 monthly copies (about 7 months in total) and then deleted automatically.
- Hosting: Oracle Cloud Infrastructure, Hyderabad (ap-hyderabad-1), India. Platform tokens and backups are encrypted as described above; the database itself is not encrypted at rest.
- Staff access: only named Duo Dev Technologies staff have administrative access to the Service, and they access personal data only to provide support, keep the Service secure or comply with the law.
No system is completely secure. If a personal data breach occurs we will notify you and the authorities where the law requires it.
- Encryption in transit: the Service is served over HTTPS, and all calls to the social platforms, accounts.duodev.in and DD Management use HTTPS.
- Access control: only members of an organisation can see that organisation's connected accounts; only owners, admins and developers can connect or disconnect them. Tokens are never sent to your browser.
- Connection security: platform connections use the OAuth state parameter and, where supported (YouTube, X), PKCE, to prevent request forgery.
- Rate limiting on sign-in, contact and support forms.
- Backups: the database and uploaded files are backed up every night into archives encrypted with AES-256, stored on our server in India. Backups are kept as 7 daily, 4 weekly and 6 monthly copies (about 7 months in total) and then deleted automatically.
- Hosting: Oracle Cloud Infrastructure, Hyderabad (ap-hyderabad-1), India. Platform tokens and backups are encrypted as described above; the database itself is not encrypted at rest.
- Staff access: only named Duo Dev Technologies staff have administrative access to the Service, and they access personal data only to provide support, keep the Service secure or comply with the law.
No system is completely secure. If a personal data breach occurs we will notify you and the authorities where the law requires it.
8. How long we keep data
| Data | How long |
|---|---|
| Account data (name, email, avatar) | Until your Ripple account is deleted. There is no self-service account deletion yet; ask us at support@duodev.in. Accounts are not deleted automatically after a period of inactivity. |
| Organisations and memberships | Until the organisation is deleted. Owners can delete Ripple's data for an organisation under Data & privacy; it is permanently deleted 14 days later unless cancelled (platform connections, posts, drafts, media and exports). The organisation itself (the workspace, its name and its memberships) is managed in your duodev account and deleted there; Ripple's copy of it is kept while the workspace exists. |
| Access and refresh tokens | Until you disconnect the platform in Ripple, or until the token is replaced on reconnection. Disconnecting deletes the tokens immediately. |
| Connected account ID, username and profile details | Deleted within 7 days after the account is disconnected. Until then they are kept so the connection can be shown as "disconnected" and reconnected. |
| Scheduled posts (caption, media URLs, status) | Published, failed, cancelled and rejected posts are deleted automatically 30 days after their last update. Posts still waiting to be published or approved are kept until they are published, cancelled or rejected. |
| Media uploaded for a post and made available to a platform at a public link | 48 hours after the post's scheduled publishing time, then deleted automatically. |
| Organisation data exports | 7 days; the download link and the file expire together. |
| Bulk-scheduling CSV files (imported rows) | 7 days. |
| Media library files | Until the organisation deletes them or the organisation is deleted. |
| AI assist requests (captions and images sent to the AI provider) | Not stored by Ripple. The AI provider keeps them only as its commercial API terms allow (see section 9). The audit log entry for each use (action and credits, no content) follows the audit log retention. |
| Analytics snapshots and best-time-to-post data | As long as the organisation exists. |
| Inbox items (comments, mentions and direct messages, when the unified inbox is available) | While the account stays connected in Ripple; items marked done are deleted 90 days later. LinkedIn comments are deleted 47 hours after they arrive. |
| LinkedIn Page statistics (daily analytics snapshots) | 1 year. |
| Cached platform data | About 5 minutes (list of your Facebook Pages or Instagram accounts, Instagram account and media ownership checks). Blog content from DD Management is cached for about 5 minutes. |
| Session data | Sessions expire after 120 minutes of inactivity. Expired session records are removed periodically by the framework. |
| Temporary OAuth values (state, PKCE verifier) | Up to 10 minutes, in your session. |
| Audit log entries (including IP address and browser user agent) | 1 year (365 days) from the action, then deleted automatically. Deleted earlier when the organisation is deleted. After a Meta data deletion request, account names are removed from the related entries. |
| Server logs | 14 days (one log file per day, older files deleted automatically). |
| Error reports (when error tracking is enabled) | 90 days. |
| Browser security reports (Content Security Policy violations: page path, blocked web address origin, browser user agent; no query strings or account data) | 90 days after the last matching report. |
| Backups | 7 daily, 4 weekly and 6 monthly copies (about 7 months), then deleted automatically. Data you delete from Ripple stays in existing backups until they expire. |
| Failed background job records (technical details of a failed task, which may include the IDs of the records involved) | Kept until our staff remove them. |
| Contact form messages and support tickets | Stored by DD Management until the matter is closed; ask us to delete them. |
9. Who we share data with
We share data only as described here:
- Social platforms you connect (Meta: Facebook, Instagram and Threads; Google: YouTube and Business Profile; X, LinkedIn, TikTok, Pinterest, Bluesky and Mastodon servers): we send them your requests (for example a post to publish) using your tokens. Their use of data is governed by their own privacy policies.
- duodev accounts (accounts.duodev.in): provides sign-in. Operated by Duo Dev Technologies.
- DD Management: a duodev service that receives contact form messages and support tickets and provides our blog content. Operated by Duo Dev Technologies.
- Service providers (sub-processors) that host and run the Service: - Hosting / infrastructure: Oracle Cloud Infrastructure, Hyderabad (ap-hyderabad-1), India - Email delivery: our own mail server (mail.duodev.in), operated by Duo Dev Technologies - Backups: on our own server (Oracle Cloud Infrastructure, Hyderabad, India) - AI assist (only for organisations that turn it on): Anthropic, PBC (Claude API), United States. Receives the caption text or image a member asks AI assist to work on. Under Anthropic's commercial terms, API inputs and outputs are not used to train its models and are kept only for the limited period those terms and its data retention policy allow.
- Other members of your organisation see the organisation's connected accounts, scheduled posts and platform content.
- Authorities, if the law requires it, and a buyer or successor in a merger or acquisition (for Google user data, only with your explicit prior consent).
We do not sell personal data.
- Social platforms you connect (Meta: Facebook, Instagram and Threads; Google: YouTube and Business Profile; X, LinkedIn, TikTok, Pinterest, Bluesky and Mastodon servers): we send them your requests (for example a post to publish) using your tokens. Their use of data is governed by their own privacy policies.
- duodev accounts (accounts.duodev.in): provides sign-in. Operated by Duo Dev Technologies.
- DD Management: a duodev service that receives contact form messages and support tickets and provides our blog content. Operated by Duo Dev Technologies.
- Service providers (sub-processors) that host and run the Service: - Hosting / infrastructure: Oracle Cloud Infrastructure, Hyderabad (ap-hyderabad-1), India - Email delivery: our own mail server (mail.duodev.in), operated by Duo Dev Technologies - Backups: on our own server (Oracle Cloud Infrastructure, Hyderabad, India) - AI assist (only for organisations that turn it on): Anthropic, PBC (Claude API), United States. Receives the caption text or image a member asks AI assist to work on. Under Anthropic's commercial terms, API inputs and outputs are not used to train its models and are kept only for the limited period those terms and its data retention policy allow.
- Other members of your organisation see the organisation's connected accounts, scheduled posts and platform content.
- Authorities, if the law requires it, and a buyer or successor in a merger or acquisition (for Google user data, only with your explicit prior consent).
We do not sell personal data.
10. International transfers
Our servers are located in India (Oracle Cloud Infrastructure, Hyderabad). The social platforms you connect are mostly based in the United States and process data globally. Where personal data is transferred outside the European Economic Area or the United Kingdom, we rely on Standard Contractual Clauses or the other safeguards the law allows. Transfers from India follow the Digital Personal Data Protection Act, 2023. You can ask us for a copy of the safeguards at support@duodev.in.
11. Your rights
Depending on where you live, you have the right to:
- access the personal data we hold about you;
- correct it (your name, email and avatar come from your duodev account and can be changed there);
- delete it;
- restrict or object to processing based on legitimate interests;
- portability: receive the data you gave us in a structured, machine-readable format;
- withdraw consent at any time, where we rely on consent;
- complain to a data protection authority, for example in your country of residence.
To exercise these rights, email support@duodev.in. We will reply within one month (or as required by applicable law). Organisation owners can export an organisation's data and delete the organisation themselves under Data & privacy; other requests (including deleting your user account) are handled manually.
You can stop Ripple accessing a platform at any time by disconnecting it on the Platforms page and by removing Ripple in that platform's settings. See our Data Deletion Instructions.
- access the personal data we hold about you;
- correct it (your name, email and avatar come from your duodev account and can be changed there);
- delete it;
- restrict or object to processing based on legitimate interests;
- portability: receive the data you gave us in a structured, machine-readable format;
- withdraw consent at any time, where we rely on consent;
- complain to a data protection authority, for example in your country of residence.
To exercise these rights, email support@duodev.in. We will reply within one month (or as required by applicable law). Organisation owners can export an organisation's data and delete the organisation themselves under Data & privacy; other requests (including deleting your user account) are handled manually.
You can stop Ripple accessing a platform at any time by disconnecting it on the Platforms page and by removing Ripple in that platform's settings. See our Data Deletion Instructions.
12. Cookies and local storage
We use only what is needed for the Service to work:
We do not use advertising or analytics cookies.
| Name | Type | Purpose | Duration |
|---|---|---|---|
| Session cookie (ripple_session) | Cookie, first-party, HTTP-only | Keeps you signed in and protects forms | Until 120 minutes of inactivity |
| XSRF-TOKEN | Cookie, first-party | Protects against cross-site request forgery | Same as session |
| dd-theme | Browser local storage | Remembers light or dark theme | Until you clear it |
| dd-sidebar-collapsed and other interface preferences | Browser local storage | Remembers whether menus are open or collapsed | Until you clear it |
13. Children
Ripple is a business tool and is not intended for anyone under 18 years old (a duodev account requires you to be 18 or older). We do not knowingly collect data from children. If you believe a child has given us personal data, contact us and we will delete it.
14. Changes to this policy
We may update this policy. We will change the "Last updated" date and, for significant changes, tell you by email or in the Service before they take effect. If we change how we use data from Google APIs or another platform, we will ask for your consent where required.
15. Contact
Duo Dev Technologies 2/45, JJ Colony, Near Common Service Centre, Mettupattithathanur, Salem, Tamil Nadu - 636103, India Email: support@duodev.in
Platform policies referenced
- Google Privacy Policy
- YouTube Terms of Service
- Google API Services User Data Policy
- Meta Privacy Policy and Meta Platform Terms
- X Privacy Policy
- LinkedIn Privacy Policy
- TikTok Privacy Policy
- Pinterest Privacy Policy
- Bluesky Privacy Policy
- Mastodon: the privacy policy of the server your account is on
Platform policies referenced
- Google Privacy Policy
- YouTube Terms of Service
- Google API Services User Data Policy
- Meta Privacy Policy and Meta Platform Terms
- X Privacy Policy
- LinkedIn Privacy Policy
- TikTok Privacy Policy
- Pinterest Privacy Policy
- Bluesky Privacy Policy
- Mastodon: the privacy policy of the server your account is on