Privacy policy

DGTOOHL Social (“the Service”) is an internal publishing console operated by DGTOOHL for its own team. It is not a public consumer product and is not offered for sale. Access is limited to invited superadmins.

For this Service, DGTOOHL is the organisation that decides why and how personal data is processed (the data fiduciary under India’s Digital Personal Data Protection Act, 2023).

This policy explains:

• what information the Service stores when you sign in and publish;
• what we receive from Instagram, YouTube, X, and LinkedIn when you connect an account;
• what we send to those platforms when you publish;
• how caption drafting uses an AI provider;
• cookies, retention, security, and how to disconnect or delete data.

It does not replace the privacy policies of Meta, Google, X (Twitter), LinkedIn, or NVIDIA. Those companies process data under their own terms when we call their APIs.

3.1 Superadmin accounts

When a superadmin is created (first-run setup or invite), we store:

• name and email address;
• a hashed password (we do not store the password in plain text);
• whether two-factor authentication (MFA) is enabled;
• an encrypted MFA secret used only to verify authenticator codes;
• account and session version timestamps.

3.2 Workspaces and publishing

To schedule and send posts we store:

• workspace names, timezone (default Asia/Kolkata), and pause state;
• draft, scheduled, published, failed, and cancelled posts;
• captions, optional titles, caption overrides per destination, and schedule times;
• which connected account each post was sent to, publish status, retry count, and error text;
• platform post IDs returned after a successful publish.

3.3 Media files

Images and videos you upload are stored on the Service’s server with file name, MIME type, size, and a storage path. A copy may be fetched by a social platform during publish through a time-limited public media URL that uses the media record id. Anyone who has that URL can retrieve the file until it is deleted.

3.4 Connected social accounts

When you tap Connect we store, for each destination:

• platform (Instagram, YouTube, X, LinkedIn, or Google Business Profile);
• display name, handle, and the platform’s account or Page id;
• OAuth access tokens and, where issued, refresh tokens — encrypted at rest;
• token expiry, granted scopes, connection status, and Page vs profile metadata.

We do not receive your Instagram, Google, X, or LinkedIn passwords. Those stay with the platform. We only receive tokens you authorise.

3.5 Invites

Superadmin invites store the invitee email, a hashed invite token, expiry, and who created the invite. The raw invite link is shown once to the creator.

3.6 Audit logs

Security-relevant actions (sign-in, connect, publish, disconnect, invites, kill-switch changes) are logged with actor, action, object type, optional metadata, time, and IP address when available.

3.7 Auto-replies

If auto-reply is enabled, we store inbound comments, mentions, DMs, Google reviews, questions, and listing messages that we poll from connected accounts, plus the reply we sent, skip reason, or error. We only send a reply when your keyword rules match.

3.8 What we do not collect

We do not run advertising pixels, do not sell mailing lists, and do not collect payment card data. We do not scrape your social graph or analytics beyond what is required to connect an account, publish, or auto-reply.

The Service uses first-party cookies only:

• social_session — httpOnly signed session cookie. Holds user id, name, email, MFA-complete flag, and session version. Lifetime: 12 hours. Used to keep you signed in.
• oauth_state — short-lived httpOnly cookie (about 10 minutes) during Connect. Holds a signed OAuth state so the callback can be tied to your workspace. It is deleted after Connect finishes.

These cookies are necessary for the Service to work. There are no advertising or cross-site tracking cookies.

We use the information above only to:

• authenticate superadmins and enforce MFA;
• connect and disconnect social accounts you choose;
• compose, schedule, publish, retry, cancel, or clear posts;
• draft captions when you tap Write caption;
• auto-reply to matching comments, DMs, Google reviews, Q&A, and listing messages;
• show status, fail reasons, and a calendar of jobs;
• pause publishing with kill switches;
• invite other superadmins;
• keep an audit trail for security and abuse investigation;
• operate, secure, and repair the Service.

We do not use connected-account data to build advertising profiles, train public AI models for unrelated products, or contact people who are not superadmins of this studio.

Publishing requires sending your caption, media, and the authorised account identity to the platform you selected. Each platform then processes that content under its own policy.

6.1 Instagram (Meta)

We use Instagram Business Login to obtain permission to publish content to the Instagram professional account you connect. We store the Instagram user id, handle, and tokens needed to create and publish media containers. Meta’s policies apply: Instagram Privacy Policy, Meta Privacy Policy.

6.2 YouTube (Google)

This Service uses YouTube API Services to upload videos you submit to the YouTube channel you connect. We store the channel id, title, and Google OAuth tokens for that purpose. By using YouTube Connect and publish, you agree to the YouTube Terms of Service. Google’s rules for data we receive through those APIs are in the Google Privacy Policy. You can revoke our access in your Google Account permissions. We use YouTube data only to upload and manage the videos you send through this studio, not for independent advertising or unrelated profiling.

6.3 X

We use X OAuth to post on the X account you connect. We store the user id, handle, and tokens. X’s policy applies: X Privacy Policy.

6.4 LinkedIn

We use LinkedIn OAuth so you can post as your LinkedIn member profile and/or as Company Pages you administer. Depending on which Connect button you use, we may receive:

• your LinkedIn member id, name, and email (OpenID profile);
• Company Page ids, names, vanity URLs, and your admin role;
• access tokens with scopes such as posting as a member and posting as an organisation.

We use that information only to list destinations in Compose and to publish the post you confirm. We do not sell LinkedIn data, do not use it for advertising, and do not share it with other apps. You can disconnect a profile or Page in Accounts, which stops new publishes and removes stored tokens for that connection. LinkedIn’s policy: LinkedIn Privacy Policy.

6.5 Google Business Profile

We use Google OAuth with Business Profile scopes to list locations you manage and to read/reply to reviews, Q&A, and listing messages when auto-reply is on. Google’s policy: Google Privacy Policy. Revoke access in Google Account permissions.

If you tap Write caption, or if auto-reply generates a response, the Service may send text (and for captions, an attached photo) to NVIDIA NIM or the configured AI provider. That provider processes the request under its own terms. Generated captions are stored with the post if you save, schedule, or publish them. Auto-reply drafts are stored on the matching event. Do not submit content you are not allowed to share with that provider.

We share information only:

• with the social platform you selected, to publish or to complete OAuth;
• with the AI provider when you ask for a caption draft;
• with hosting and infrastructure operators who run this server and database, under our control;
• if required by law, regulation, or a valid legal process;
• to protect DGTOOHL, superadmins, or the public from fraud, abuse, or security incidents.

We do not sell personal data. We do not share connected social data with third-party advertisers. Superadmins of this studio can see workspaces, connected accounts, posts, and media inside the Service.

• Superadmin accounts remain until an operator deletes them.
• Session cookies expire after 12 hours or when you sign out.
• OAuth cookies expire within minutes after Connect.
• Connected-account tokens remain until you Disconnect that account. Disconnect cancels future jobs for that account and drops the stored tokens.
• Posts, media, and audit logs remain until deleted by a superadmin or server operator.
• Invite records remain for audit after expiry or acceptance.

Content you successfully publish also lives on Instagram, YouTube, X, or LinkedIn under that platform’s retention rules. Deleting a job here does not automatically delete the live post on the platform.

We apply these controls:

• passwords hashed; MFA required for the studio;
• OAuth and MFA secrets encrypted at rest;
• HTTPS on social.dgtoohl.in;
• httpOnly session cookies; signed OAuth state;
• role limited to invited superadmins;
• kill switches to halt publishing;
• audit logs of sensitive actions.

No method of transmission or storage is perfectly secure. If you believe tokens or a password were exposed, sign out, rotate the password, disconnect the social account, and reconnect after revoking the app in that platform’s settings.

Superadmins can:

• see and edit posts before they go live;
• choose which profile or Company Page receives a post;
• disconnect any social account in Accounts;
• cancel or clear jobs in Calendar;
• sign out, which clears the session cookie;
• revoke platform access in Instagram, Google, X, or LinkedIn settings.

Depending on applicable law (including India’s DPDP Act, 2023), you may request access, correction, or erasure of personal data we hold, or withdraw consent for processing that relies on consent (for example, a connected social account). Send the request as described in Contact. We may need to verify that you are the superadmin or an authorised operator. Some records (security logs, legal holds) may be kept where the law allows or requires it.

The Service is for DGTOOHL staff superadmins only. It is not directed at children, and we do not knowingly create studio accounts for anyone under 18.

The studio and its database run on infrastructure used by DGTOOHL. Social platforms and the AI provider process data in the regions they operate, which may be outside India. Connecting an account and publishing means that data is transferred to those providers as needed to perform the action you requested.

We may update this page when the Service, platforms, or law change. The “Effective” date at the top will change. Material changes will be reflected on this URL, which is the policy LinkedIn, Google, Meta, and X should use for app review.

Privacy questions and data requests for this Service: DGTOOHL, operators of https://social.dgtoohl.in. Use a signed-in superadmin account or the contact channel published on the DGTOOHL website. Name the Service “DGTOOHL Social” and describe the account or connected platform involved.

Canonical policy URL: https://social.dgtoohl.in/privacy