dripLineSOCIAL MEDIA POST ORGANIZER

YOUR WORKSPACE. YOUR CHOICES.

Privacy policy

Last updated October 23, 2026 · Free beta

Who we are

dripLine is a social-media planning and scheduling service operated by Yard Socket LLC in Ohio, United States. Contact hello@dripline.tech about your information or this policy. This policy covers dripline.tech and app.dripline.tech.

Information used by the service

Why we use it

We use this information to sign you in, keep your workspace separate, save your work, connect your chosen accounts, deliver posts you schedule, check delivery status, prevent misuse and provide support. dripLine currently has no advertising trackers, targeted-advertising features or AI-training features, and does not sell your personal information.

Product-update emails

You may choose to receive occasional updates and new-product news from dripLine, Matching Sox Tools and Yard Socket. The signup checkbox is optional and starts unchecked. Change this choice in Account setup at any time, or contact hello@dripline.tech. Essential confirmation, password-reset and account messages are separate. Saved preferences do not automatically subscribe you to an outside mailing service.

dripLine tips emails

If you sign up for “Get dripLine tips” on dripLine.tech, we keep your email address, the consent wording you agreed to, the time and the page you signed up from. We use it only to send occasional dripLine tips and product news, sent through our email provider Resend, and we send you a welcome email with an unsubscribe link. Unsubscribe with that link or by writing to hello@dripline.tech, and we stop sending.

Where information goes

Hostinger provides website hosting and service email. Supabase provides authentication and the application database; earlier media may remain in Supabase Storage while migration is completed. Cloudflare R2 stores uploaded photos and videos, including saved edited videos and cover images. The service sends transactional messages, including enabled support-reply notifications, through Resend. These providers process the information needed for their role in running dripLine. Your own uploaded media and platform-returned account data are distinct; the Google and YouTube section below explains the specific handling of Google API data. When you connect a platform or schedule a post, relevant account information and the content and options you select are sent to that platform through its official services. Supported features and permissions differ by platform.

Business workspaces can be shared with teammates you invite. Their assigned roles determine whether they can draft, review or schedule workspace content. Your personal profile and product-email preference are kept separate from shared workspace content. Optional links to Matching Sox Tools and Yard Socket open those websites without sending your account details or drafts with the link.

Authorized operators may access information when necessary to operate the service, resolve a support request, investigate abuse or meet a legal obligation. Information may also be disclosed when required by law. Services may process information in the United States or other countries where their infrastructure operates.

Published posts follow the audience settings and rules of the destination platform. If you load media from an outside website, that website may receive your browser's request and network information.

Google and YouTube

dripLine uses YouTube API Services to identify your connected channel, publish the uploads you schedule and check their processing and visibility. By connecting YouTube you agree to be bound by the YouTube Terms of Service (youtube.com/t/terms). Google's privacy practices are described in the Google Privacy Policy.

What we access: your channel ID and name (to show which channel is connected), the status of uploads dripLine sent for you, and OAuth access tokens. What we do: publish the uploads you schedule to your channel with the title, description and settings you choose. We store the channel ID and name, the YouTube upload IDs and statuses, and encrypted tokens, and use them only for these features. We do not share Google user data with third parties except our hosting and database providers (Hostinger, Supabase), which run the service, or where the law requires it.

dripLine's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not use Google user data for advertising, sell it, or use it to train AI models. People do not read it except with your permission, for security, or to comply with law.

You can revoke dripLine's access at any time through Google security settings (security.google.com/settings/security/permissions), in addition to requesting deletion from dripLine. Before using YouTube features, you must expressly agree to this Privacy Policy and our Terms, including YouTube’s Terms of Service. We record the policy version and agreement time. Disconnecting stops new YouTube uploads and requests revocation of your Google authorization. We remove your saved channel details and YouTube-returned video identifiers, links and processing details from active storage. If Google is temporarily unavailable, the inaccessible encrypted token is kept only for revocation retries and is removed within seven calendar days. We check connected channel authorization and identity at least daily while the service operates, and remove unrefreshed API data within 30 days. YouTube-returned publishing metadata is removed within 30 days rather than kept indefinitely. Revocation or deletion requests are handled within seven calendar days; applicable legal retention obligations may require limited exceptions. Your own descriptions, uploaded files and drafts are preserved unless you also ask us to delete them. Disconnecting does not delete videos already on YouTube. We do not automatically add promotional text to your YouTube descriptions.

Connecting your own AI

If you choose to connect an outside AI service, dripLine shares supported connected-channel names and identifiers with that service and receives the text and links you ask it to save as drafts. This connector does not send your existing post contents, uploaded media, team information or social credentials to the AI. Google and YouTube channel data is excluded from this connector.

Your AI provider generates the writing under your account with that provider. Its plan, privacy settings, retention and training policies apply to your interactions there. dripLine does not make an AI-generation API call for this connector workflow and does not use your connector data to train AI models.

New AI authorizations are independent of browser sign-in and renew while in use. They expire after 90 days without renewal or at a maximum of one year. Access tokens are short-lived; refresh tokens rotate. You can revoke one or all AI connections in Connections. Password resets through dripLine and account security restrictions end access earlier. Older authorizations keep their original sign-in limit until you explicitly reconnect.

Disconnecting stops new AI access and keeps existing drafts. Authorization and security records may remain after expiry or revocation for operation and troubleshooting. Drafts remain until removed or included in an account-data deletion request. Contact hello@dripline.tech for privacy or deletion requests. See the connector guide for current limits and supported behavior.

Pinterest connections

For Pinterest, we keep encrypted authorization tokens and their expiry and permissions, a locally generated connection reference and label, and your own content and scheduling instructions. We do not retain your Pinterest username, profile, board names, raw board identifiers, returned Pin identifiers or returned Pin links. Board names are fetched from Pinterest when you choose a board and kept temporarily in memory for that composer session. The selected destination is saved as a private, connection-specific reference; the current board list is fetched again to resolve that choice at delivery. If the board is no longer available, the Pin is not sent to a different board. Publishing history keeps a local confirmation reference and delivery status.

Pinterest connections are excluded from our connected-AI tools and Pinterest captions cannot use our AI caption helper. We do not use Pinterest API information to train AI or share it with AI providers. You choose each Pin, its image, destination board and publishing time. Disconnecting removes the saved connection and authorization tokens; your own drafts and local publishing history remain until you remove them or request account deletion.

Account contact and two-step sign-in

You may save an optional contact phone number. It is stored encrypted, is not verified, and is not used for SMS, sign-in, password recovery or advertising. Authorized support operators can view it when helping you. Remove it by clearing the contact field in Account settings. Authenticator-based two-step sign-in is optional for customer accounts and required for administrator accounts. Supabase handles authenticator enrollment and verification. dripLine uses the resulting verification status to protect account access; do not send support your password, authenticator secret or verification codes.

Media editing and uploaded audio

Browser editing processes the video, photos, subtitle text and audio files you select on your device. Selecting a local audio file for that editor does not by itself upload the standalone audio file to dripLine. If you choose to save the finished video or cover to your workspace, that result is uploaded to private storage. Server-side video conversion processes an uploaded video when you request or use that supported workflow. Media chosen from your workspace must be retrieved for preview or editing. Processing and downloading do not by themselves schedule or publish a post. We do not supply a licensed music catalogue or send your editor audio to a transcription service.

Support, service statistics and manual comparisons

Support records include your account identifier and email, messages, any screenshot or attachment you choose to send, ticket category, priority, status, timestamps, and resolution feedback. Authorized support operators can add internal notes that are not displayed to the customer. Enabled ticket emails send notification information through our transactional email provider; ticket notification preferences are separate from marketing consent. Live-chat availability uses administrator presence and activity signals and may show offline when the administrator is inactive or the tab is hidden.

Workspace and administrator statistics are calculated from retained account, post, delivery, connection, media and support records. Customer analytics show operational activity and delivery outcomes; they do not currently fetch social views, likes, reach or follower trends. Optional post comparisons contain the results and notes you enter yourself. Public link-in-bio pages can count visits and link clicks using limited request information for counting and rate protection. A link count does not identify which named person clicked. We do not add a third-party advertising or paid analytics tracker for these statistics.

Partner and referral administration

Authorized administrators may keep business partner contact details, referral references, status, follow-up dates and notes in a private encrypted tracker. These are manually entered business records, not automatic tracking of every visitor or a payment programme. Business contacts may request correction or deletion by emailing hello@dripline.tech, subject to legitimate service, security and legal retention needs.

Copyright and abuse reports

If you send a copyright or abuse report, we use your contact details, statements, referenced content and related account records to assess and respond to it. We may share relevant report or response details with the affected user, rights holder, service provider, advisers or authorities when needed to handle the matter or meet legal requirements. Do not include passwords, access tokens or unnecessary sensitive information. See our copyright policy and reporting instructions.

Cookies and security

Essential cookies keep you signed in and protect sign-in actions. The current session cookie can last up to seven days; a sign-in safety cookie lasts up to one hour. Blocking these cookies can prevent sign-in. We use HTTPS, account access controls and server-side encryption for stored social tokens. No online service can guarantee complete security.

Keeping and removing information

Workspace content remains available while you keep it in the service. You can remove drafts and unused media and disconnect social accounts. Cancel a scheduled post before deleting it. Disconnecting removes dripLine's stored connection; it does not delete your publishing history or posts already sent to a platform.

For deletion of your account, all workspace data, or retained data from a particular platform, follow our data-deletion instructions. Requests are handled manually after ownership verification. We retain information needed for an active service purpose or legal obligation, and review retention when handling deletion requests. Provider backup copies may persist until their normal expiration; we do not use those copies for routine service operation.

Your choices and updates

You can edit your drafts, export workspace records, disconnect accounts or ask for access, correction or deletion at hello@dripline.tech. Additional privacy rights may apply where you live. We will update this page when our practices change. Material changes will be brought to users' attention before the changed use where required. Paid plans are not active; any future payment handling will be described before checkout becomes available.

Password safety and two-step sign-in

When you create or reset a password, dripLine checks it against known breached passwords using Have I Been Pwned’s Pwned Passwords service. Only the first five characters of a password hash are sent; your password and its full hash are not sent to that service. Authenticator-based two-step sign-in is available for customers and required for dripLine administrators.