Privacy Policy

1. Introduction

AbeShare, operated by Dear Daughter Bible Study.

Dear Daughter Bible Study ("we," "us," or "our") operates AbeShare at https://www.abeshare.com (the "Service"). This Privacy Policy explains what information we collect, how we use it, with whom we share or transfer it, and your choices.

By creating an account or connecting a social network, you agree to this Privacy Policy. If you do not agree, please do not use the Service.

2. Information we collect

Account information. When you sign up, we store your email address and account credentials managed by our authentication system (PocketBase).

Connected social accounts. When you click Connect for a platform, we receive and store OAuth tokens, refresh tokens, and related metadata (such as page IDs, channel IDs, usernames, and profile display names) needed to publish on your behalf. We do not receive your social network passwords for OAuth-based platforms.

Content you provide. We store posts, captions, schedules, and media files you upload for publishing.

Platform analytics (where enabled). If you connect a platform that supports insights, we may store aggregated metrics returned by that platform (for example, follower counts or post performance) to display in your dashboard.

Usage and technical data. We may log IP addresses, browser type, and error messages to operate, secure, and improve the Service.

3. How we use information

• Authenticate you and maintain your account
• Publish or schedule content to platforms you connect
• Refresh OAuth tokens so connected accounts remain active
• Display connection status, job history, and optional analytics in your dashboard
• Generate optional AI-assisted caption variants when you request them
• Monitor job status, retries, and failures
• Respond to support requests, data-deletion requests, and legal obligations

We use information only to provide and improve the Service and to perform actions you explicitly request. We do not use platform user data for advertising, profiling, or unrelated purposes.

4. Sharing, transfer, and disclosure of data

We do not sell your personal information or platform user data. We share, transfer, or disclose information only as described below.

With connected platforms (at your direction). When you connect an account and schedule or publish content, we transfer data to the relevant platform's APIs so your post can be delivered. This includes OAuth tokens, post text, media files, and publishing metadata. Data is sent only to the platform(s) you select for that action.

With service providers (on our behalf). We use hosting and infrastructure providers to run the Service (for example, servers that store your account, tokens, posts, and media). These providers process data solely under our instructions to operate AbeShare and are not permitted to use your data for their own purposes.

With AI providers (only if you use AI features). If you request AI-generated captions, the text you submit may be sent to configured AI providers (such as OpenAI, Anthropic, Groq, or a local model you configure) solely to generate draft text for your review. AI providers do not receive your OAuth tokens or platform passwords.

Legal and safety. We may disclose information if required by law, court order, or government request, or when we believe disclosure is necessary to protect rights, safety, or security.

Business transfers. If we are involved in a merger, acquisition, or sale of assets, user information may be transferred as part of that transaction. We will notify you before your data becomes subject to a different privacy policy.

We do not share platform user data with data brokers, advertisers, or unrelated third parties.

5. Platform-specific notices

When you connect a platform, your use is also subject to that platform's terms and privacy policies (linked in each subsection below). The sections below describe what we access and with whom that platform's user data is shared or transferred.

Google and YouTube

If you connect YouTube, we access Google user data through Google OAuth. This section describes how we access, use, share, protect, and delete that data in compliance with the Google API Services User Data Policy, including Limited Use requirements.

Data we access. With your authorization, we access: your Google account identifier (via OAuth), YouTube channel ID and channel name (via YouTube Data API), OAuth access and refresh tokens, and video metadata and media files that you upload in our dashboard for publishing to your channel.

How we use Google user data. We use this data only to: (1) authenticate your YouTube connection, (2) identify which channel to publish to, (3) upload or schedule videos you compose and explicitly submit, and (4) display connection status and publish history in your dashboard. We do not use Google user data for advertising, profiling, credit/lending decisions, or any purpose unrelated to providing the Service.

With whom we share, transfer, or disclose Google user data: Google user data is transferred to Google LLC (YouTube and Google OAuth) when you authorize the connection and when you request publishing. Google user data is processed by our hosting providers solely to store tokens and operate the Service. We do not sell Google user data or share it with advertisers, data brokers, or unrelated third parties.

How we protect Google user data. We store OAuth tokens server-side, transmit data over HTTPS, and restrict access to authenticated users' own accounts. See Section 8 (Security) below.

Retention and deletion. Google OAuth tokens and channel metadata are retained while your account is active and the YouTube connection remains linked. You may disconnect YouTube in the dashboard at any time, which removes stored tokens for that connection. You may revoke our access at Google Account permissions. To delete all account data, see our Data Deletion page.

Limited Use and AI. We do not use Google user data to develop, improve, or train generalized AI/ML models. We do not transfer Google user data to third-party AI services. Optional AI caption features inAbeShare process text you type in the dashboard; they do not receive Google OAuth tokens or YouTube API data from Google.

Limited Use compliance statement: The use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

See also Google's Privacy Policy.

TikTok

If you connect TikTok, we receive OAuth tokens and basic profile information (such as your TikTok username and open ID). We transfer post content and media to TikTok / ByteDance APIs when you publish or schedule. We may also retrieve analytics (such as follower or video metrics) from TikTok when you have granted the relevant scopes. We do not sell or share TikTok user data with unrelated third parties. Your use of TikTok through AbeShare is also subject to TikTok's Privacy Policy and TikTok for Developers policies.

Meta (Facebook, Instagram, Threads, and WhatsApp Business)

If you connect Facebook Pages, Instagram, Threads, or WhatsApp Business, we receive OAuth tokens and metadata such as Page ID, Instagram business account ID, username, and (for WhatsApp) phone number ID and business account identifiers needed to publish. We transfer post text, media, and publishing instructions to Meta Platforms, Inc. APIs when you schedule or publish. If you remove our app from Facebook or Instagram settings, Meta may send a data-deletion request to our callback URL so we can delete associated tokens. We do not sell or share Meta user data with unrelated third parties. Your use of Meta services through AbeShare is also subject to Meta Platform Terms, Meta Privacy Policy, and (for WhatsApp Business) WhatsApp Business Solution Terms.

LinkedIn

If you connect LinkedIn, we receive OAuth tokens and organization or profile identifiers needed to publish on your behalf. We transfer post content to LinkedIn Corporation APIs when you schedule or publish. We do not sell or share LinkedIn user data with unrelated third parties. Your use of LinkedIn through AbeShare is also subject to LinkedIn API Terms of Use and LinkedIn Privacy Policy.

Bluesky

If you connect Bluesky, you provide an app password or session credentials for your Bluesky account. We store these credentials securely and transfer post content to the Bluesky / AT Protocol network (including Bluesky's hosted services or the PDS you use) when you publish. We do not sell or share Bluesky credentials with unrelated third parties. Your use of Bluesky through AbeShare is also subject to Bluesky Terms of Service and Bluesky Privacy Policy.

Spotify

If you use Spotify-related features, we may access Spotify metadata (such as track, album, or episode information from URLs you provide) through the Spotify AB Web API using application credentials or tokens you authorize. We use this data only to enrich posts you compose. We do not sell or share Spotify user data with unrelated third parties. Your use of Spotify through AbeShare is also subject to Spotify Developer Terms and Spotify Privacy Policy.

X (Twitter)

If you connect X (formerly Twitter), we receive OAuth tokens and account identifiers needed to publish on your behalf. We transfer post text and media to X Corp. APIs when you schedule or publish. We do not sell or share X user data with unrelated third parties. Your use of X through AbeShare is also subject to X Developer Agreement and X Privacy Policy.

6. Data retention

We retain account data, connected tokens, posts, and job history while your account is active. OAuth tokens remain until you disconnect a platform or delete your data. Scheduled content and media are retained to complete publishing and provide history in your dashboard.

7. Your rights and choices

Disconnect platforms. In the dashboard, use Disconnect on any connected account to revoke stored tokens for that platform.

Delete your data. See our Data Deletion page for instructions, including how to request removal when you remove our app from Facebook or Instagram.

Revoke Google access. You can revoke AbeShare's access to your Google account at any time at Google Account permissions.

Access or correction. Email us at [email protected] to request a copy of or corrections to your personal data.

8. Security

We use industry-standard practices including HTTPS, server-side token storage, and access controls. No method of transmission or storage is 100% secure; we cannot guarantee absolute security.

9. Children

The Service is not directed to children under 13 (or the minimum age required in your jurisdiction). We do not knowingly collect personal information from children.

10. Changes

We may update this Privacy Policy from time to time. We will post the revised version on this page and update the "Last updated" date. Continued use after changes constitutes acceptance.

11. Contact

Questions about this Privacy Policy: [email protected]
Dear Daughter Bible Study