Privacy Policy
Last Updated: October 18, 2026
This Privacy Policy describes how Foragentis ("Company," "we," "us," or "our") collects, uses, shares, and protects your personal information when you use ForaPost, our AI social media management platform (the "Service").
ForaPost is a product of Foragentis, a California limited liability company.
By using ForaPost, you consent to the data practices described in this Privacy Policy.
1. Information We Collect
1.1 Information You Provide Directly
Account Information:
- Name
- Email address
- Password (encrypted)
- Company/business name
- Profile photo (optional)
- Timezone preferences
Brand and Content Information:
- Brand voice settings and preferences
- Uploaded documents and collateral (PDFs, text files, images, audio, video)
- Files imported from Google Drive or Dropbox that you explicitly select
- Website URLs you provide for content extraction
- URLs you submit for batch content import
- Topics, tone, and style preferences
- Content you create, edit, or approve within the Service
- Product data from connected e-commerce platforms
Payment Information:
- Billing name and address
- Payment method details (processed and stored securely by Stripe; we do not store full card numbers)
Communications:
- Support requests and correspondence
- Feedback and survey responses
1.2 Information from Connected Social Media Accounts
When you connect social media accounts to ForaPost, we access and store only the minimum data necessary to provide the Service:
From All Platforms:
- Account identifiers and usernames
- Profile information (name, profile picture)
- Authentication tokens (encrypted, for API access)
- Basic account status
| Platform | Data Accessed | Purpose |
|---|
| Facebook | Page info, publishing permissions | Publish posts to your Pages |
| Instagram | Business account info, publishing permissions | Publish posts and stories |
| Threads | Profile info, publishing permissions | Publish threads |
| LinkedIn | Personal Profiles: Name, headline, profile picture, OAuth tokens Organization Pages: Page name, admin status, OAuth tokens Post Metrics: Likes, comments, shares, impressions (only for posts published via ForaPost) | Publish posts to personal profiles and company pages you administer Display engagement analytics in dashboard Identify connected accounts |
| Twitter/X | Profile info, posting permissions | Publish tweets |
| YouTube | Channel info, upload permissions, comment data | Upload videos and manage comments |
| TikTok | Profile info, posting permissions | Publish videos |
| Bluesky | Profile info (handle, display name, avatar), posting permissions, App Password tokens, post engagement metrics (likes, reposts, replies) | Publish posts to your Bluesky account Display engagement analytics for posts published via ForaPost |
| Pinterest | Encrypted OAuth tokens, the Pinterest user ID and board ID(s) you selected as configuration, and Pin IDs for content ForaPost created. Profile details, board names/contents, engagement metrics, and comments are fetched live from Pinterest each time they are shown and are not stored. | Publish and schedule Pins to your Pinterest account Display live engagement analytics for Pins published via ForaPost |
What We Do NOT Access:
- Your private messages or DMs
- Your friend lists or follower details
- Your personal browsing activity
- Content from other users
- Data beyond what is necessary for publishing
1.3 Information Collected Automatically
Usage Information:
- Features used and actions taken within ForaPost
- Posts created, scheduled, and published
- Login times and session duration
Device and Technical Information:
- IP address
- Browser type and version
- Device type and operating system
- Referring URLs
Cookies and Similar Technologies:
- Sign-in and security cookies (for authentication)
- Campaign attribution cookies
- Analytics (Google Analytics and Ahrefs)
Section 8.5 lists each cookie, what it is for and how long it lasts.
1.4 Information from Connected Cloud Storage
When you connect cloud storage services to ForaPost, we access and store:
Google Drive:
| Data Accessed | Purpose |
|---|
| File list (when browsing via Picker) | Display files for you to select |
| Selected file contents | Analyze to learn your brand voice |
| Account email | Identify connected account |
Dropbox:
| Data Accessed | Purpose |
|---|
| File and folder list | Display files for you to select |
| Selected file contents | Analyze to learn your brand voice |
| Account email | Identify connected account |
What We Do NOT Access:
- Files you do not explicitly select
- Shared files or folders you don't own (unless selected)
- Your storage quota or account settings
- Other apps connected to your cloud storage
How Files Are Processed:
- You browse and select specific files through our interface
- We download only the files you select
- Files are processed to extract text and analyze your writing style
- Extracted content is stored as part of your brand intelligence
- Original files are not permanently stored — only the analysis
1.5 Information from E-commerce Platforms
When you connect e-commerce platforms to ForaPost, we access:
| Platform | Data Accessed | Purpose |
|---|
| Shopify | Product names, descriptions, images, prices, inventory, store name; aggregated order data from the past 30 days (order ID, timestamp, product variant ID, quantity) for stockout-aware post scheduling | Create product-aware content; avoid promoting products predicted to sell out within 7 days |
| WooCommerce | Product names, descriptions, images, prices, inventory, store name | Create product-aware content |
| Etsy | Listing titles, descriptions, images, prices, shop name | Create product-aware content |
| Amazon | Product titles, descriptions, images, prices, inventory | Create product-aware content |
What We Do NOT Access:
- Customer names, emails, phone numbers, or any other personally identifiable information
- Shipping or billing addresses
- Payment method or financial transaction details
- Order line item prices, discount codes, or refund details
- Customer reviews or feedback (unless public)
- Tax or accounting data
1.6 Free Market Scan
If you request a free market scan on our website, we collect the email address you give us and the business details you enter (business name, city, state or region, country and type of business). We use your email address only to send you that one report, which includes an invitation to sign up. We do not add it to marketing emails unless you create an account or separately agree to receive them. We keep the request and the report on file. You can ask us to delete them at any time by emailing privacy@foragentis.com.
1A. User-Uploaded Content
ForaPost allows you to upload, import, and submit various types of content to enhance your brand voice and create social media content. This section specifically addresses how we handle user-uploaded content and your responsibilities regarding that content.
1A.1 Types of User-Uploaded Content
User-uploaded content includes:
- Documents uploaded directly (PDF, DOCX, PPTX, TXT files)
- Images (JPG, PNG, GIF, WebP, etc.)
- Audio files (MP3, WAV, M4A, etc.)
- Video files (MP4, MOV, AVI, etc.)
- Files imported from Google Drive or Dropbox
- Content extracted from URLs you provide
- Product data from connected e-commerce platforms
- Any other materials you provide to the Service
1A.2 Your Ownership and Responsibility
Important: By uploading, importing, or submitting content to ForaPost, you represent and warrant that:
- You own the content or have obtained all necessary permissions, licenses, and rights from the content owner(s) to use, upload, and authorize ForaPost to process the content
- The content does not infringe upon any copyright, trademark, trade secret, privacy, publicity, or other intellectual property or proprietary rights of any third party
- You have proper licenses for any licensed materials (stock photos, fonts, music, etc.) that permit use in social media distribution
1A.3 How We Use Your Uploaded Content
We use your uploaded content solely to:
- Analyze and learn your brand voice, tone, and writing style
- Create AI social media content tailored to your brand
- Create visual content based on your provided materials
- Improve the quality and relevance of content created for your account
1A.4 What We Do NOT Do With Your Content
- We do not share your uploaded content with other users
- We do not use your content to train general AI models sold to others
- We do not sell or distribute your uploaded content
- We do not claim ownership of your content
1A.5 Copyright Verification
ForaPost does not verify copyright ownership of content you upload. You are solely responsible for ensuring you have the legal right to use all content you provide. Uploading copyrighted content without authorization may constitute copyright infringement and could result in legal liability for you.
If you believe content on ForaPost infringes your copyright, please see our DMCA policy in our Terms of Service.
2. How We Use Your Information
We use collected information for the following purposes:
2.1 Providing the Service
- Creating and managing your account
- Connecting and maintaining social media integrations
- For LinkedIn: Publishing organic content to personal profiles and company pages you authorize; retrieving engagement metrics exclusively for content published through ForaPost; no advertising, recruiting, or social feed functionality
- Creating AI content based on your preferences
- Scheduling and publishing content to your accounts
- Processing payments and managing subscriptions
2.2 Improving the Service
- Analyzing usage patterns to improve features
- Developing new functionality
- Fixing bugs and technical issues
- Training AI models using aggregated, anonymized data only
Note: Data obtained from Google APIs (including YouTube and Google Drive) is never used for AI/ML training, advertising, or any purpose other than providing and improving the core functionality you have authorized.
2.3 Communications
- Sending transactional emails (account verification, password reset, billing)
- Providing customer support
- Sending product updates (with opt-out option)
- Notifying you of important changes
2.4 Safety and Compliance
- Detecting and preventing fraud or abuse
- Enforcing our Terms of Service
- Complying with legal obligations
- Responding to legal requests
3. Platform-Specific Data Handling
We comply with each platform's developer terms and data policies:
3.1 TikTok
- We access only the minimum data necessary for publishing
- We protect your identity and do not share TikTok user data with third parties
- We do not remove TikTok watermarks without your authorization
- We comply with TikTok's Community Guidelines and Developer Terms
3.2 X (Twitter)
- Data obtained from X is used solely for publishing on your behalf
- We comply with X's Developer Agreement and Developer Policy
- We do not use your data for purposes outside the stated functionality
- We respect X's automation rules and rate limits
3.3 LinkedIn
ForaPost's use of LinkedIn data complies with LinkedIn's API Terms of Use, Marketing API Program Terms, and Community Management API requirements.
What Data We Access:
When you connect your LinkedIn account to ForaPost, we access only the minimum data necessary:
| Data Category | Specific Data | Purpose | Retention |
|---|
| Personal Profile | Name, headline, profile picture | Identify your connected account | Deleted within 24 hours of disconnection |
| Organization Pages | Page name, organization URN, admin status | Verify posting permissions | Deleted within 24 hours of disconnection |
| Publishing Permissions | OAuth access tokens | Post content on your behalf | Deleted immediately upon disconnection |
| Post Activity | Likes, comments, shares, impressions (only for posts published via ForaPost) | Display engagement analytics | Retained for 48 hours after retrieval, then aggregated |
| Account Status | Connection status, last sync time | Maintain integration | Deleted within 24 hours of disconnection |
What We Explicitly Do NOT Access:
We cannot and will not access:
- ✗Your LinkedIn connections, network, or follower lists
- ✗Your LinkedIn messages, InMail, or private conversations
- ✗Your LinkedIn feed or content from other members
- ✗Other members' profile data beyond what's publicly visible
- ✗Your job search activity or applications
- ✗Your LinkedIn Learning courses or certificates
- ✗Your endorsements or recommendations
- ✗Your saved jobs or saved posts
- ✗Data about other members who interact with your posts (beyond public engagement metrics)
Restricted Uses - What We Never Do:
In strict compliance with LinkedIn's Marketing API Terms, ForaPost will NEVER:
Advertising & Targeting:
- ✗Use your LinkedIn data for advertising purposes
- ✗Target advertisements to you based on LinkedIn data
- ✗Sell advertising based on LinkedIn member data
- ✗Create advertising audiences from LinkedIn data
Recruiting & Talent:
- ✗Use LinkedIn data for recruiting purposes
- ✗Build candidate databases from LinkedIn
- ✗Screen job applicants using LinkedIn data
- ✗Contact LinkedIn members for recruitment
Social Feed & Content:
- ✗Display LinkedIn feeds in our application
- ✗Create a "LinkedIn-like" social network
- ✗Show content from other LinkedIn members
- ✗Aggregate LinkedIn posts from multiple users
Data Aggregation & Sale:
- ✗Export LinkedIn member data for external use
- ✗Create aggregated databases of LinkedIn information
- ✗Combine LinkedIn data with data from other sources
- ✗Sell or license LinkedIn data to third parties
- ✗Share your LinkedIn data with other ForaPost users
Scraping & Unauthorized Access:
- ✗Access LinkedIn content through scraping or crawling
- ✗Use any method other than official LinkedIn APIs
- ✗Circumvent LinkedIn's rate limits or access controls
- ✗Store or cache LinkedIn data beyond permitted durations
How We Use LinkedIn Data:
Publishing Only:
- We use your LinkedIn authorization solely to publish content you explicitly create, edit, or approve within ForaPost
- Content is transmitted directly to LinkedIn's servers using their official APIs
- We do not modify, analyze, or store your published content after transmission
Engagement Analytics:
- We retrieve metrics (likes, comments, shares, impressions) only for posts you published through ForaPost
- Metrics are displayed in your ForaPost dashboard
- Raw metric data is retained for 48 hours, then replaced with aggregated analytics
- We never access engagement data for posts you created directly on LinkedIn
Profile Display:
- We display your name and profile picture solely to identify your connected account in ForaPost
- This information is stored securely and deleted within 24 hours of disconnection
Organization Page Management:
If you connect a LinkedIn Organization Page (company page):
Access Requirements:
- You must be a verified administrator of the LinkedIn Page
- ForaPost verifies your admin status through LinkedIn's API
- We do not request or store your admin credentials
What We Access:
- Organization name and basic page information
- Verification that you have posting permissions
- Engagement metrics for posts published through ForaPost to that page
What We Do NOT Access:
- Page follower lists or demographics
- Other page admins or their information
- Page analytics beyond posts published via ForaPost
- Private page activity or drafts
Data Retention:
- Organization access tokens: Deleted immediately upon disconnection
- Page profile information: Deleted within 24 hours of disconnection
- Post activity data: Retained for 48 hours, then aggregated
- Historical analytics: Aggregated data retained for up to 1 year; can be deleted on request
Member Profile Data Handling:
If you connect a personal LinkedIn profile:
Minimal Data Access:
- We access only your basic profile information (name, headline, profile picture)
- We do NOT access your full work history, education, skills, or endorsements
- We do NOT access your connections or network information
Purpose Limitation:
- Profile data is used exclusively to identify your connected account in ForaPost
- We never use profile data for targeting, advertising, or marketing purposes
Data Retention:
- Profile data is deleted within 24 hours of disconnection
- We do not maintain historical records of profile changes
Your LinkedIn Data Controls:
Before Connecting:
- You will see a LinkedIn authorization screen showing exactly what permissions ForaPost requests
- You explicitly authorize ForaPost to access your LinkedIn account
- You can decline authorization at any time
While Connected:
- View your connected LinkedIn accounts in Settings → Connected Accounts
- See when ForaPost last accessed your LinkedIn data
- Review all posts scheduled or published to LinkedIn
Disconnecting:
- Disconnect your LinkedIn account at any time with one click
- Access tokens are deleted immediately upon disconnection
- Profile and page data are deleted within 24 hours
- Activity data is deleted within 48 hours
- Published post records (for analytics) are retained for up to 1 year unless you request immediate deletion
Revoking Access Through LinkedIn:
You can revoke ForaPost's access directly through LinkedIn:
- Go to linkedin.com/psettings/permitted-services
- Find "ForaPost" in your list of connected applications
- Click "Remove" to revoke all access
What happens after revocation:
- We receive notification that access was revoked
- All access tokens are deleted immediately (within 1 hour)
- Profile and page data are deleted within 24 hours
- Activity data is deleted within 48 hours
- We cannot post on your behalf until you reconnect
Data Deletion Requests:
Request immediate deletion of all LinkedIn-related data:
- Email: privacy@foragentis.com
- Subject: "LinkedIn Data Deletion Request"
- Include: Your ForaPost account email
We will delete within 30 days:
- All LinkedIn access tokens (immediate)
- All profile and page information
- All activity and engagement data
- All historical analytics related to LinkedIn
Cannot be deleted:
- Content already published to LinkedIn (manage through LinkedIn directly)
- Anonymized, aggregated analytics that cannot be attributed to you
Security Measures:
Data Protection:
- All LinkedIn access tokens are encrypted at rest (Fernet: AES-128-CBC with HMAC-SHA256 authentication)
- All data transmission uses TLS 1.3 encryption
- Access tokens are never logged or transmitted to third parties
- Tokens are stored separately from other user data
Access Controls:
- Only authorized ForaPost systems can access LinkedIn data
- Employee access is logged and audited
- Multi-factor authentication required for all system access
- Regular security assessments and penetration testing
Breach Notification:
In the event of a security incident affecting your LinkedIn data:
Our Commitment:
- We will notify you via email within 24 hours of discovery
- We will notify LinkedIn as required by their Terms within 24 hours
- We will provide details of what data was affected
- We will take immediate action to secure your data and prevent further access
Your Actions:
- We recommend immediately revoking ForaPost's access through LinkedIn
- We recommend changing your LinkedIn password if credentials may have been compromised
- We will provide instructions on protecting your LinkedIn account
Compliance & Legal Requirements:
We comply with:
- LinkedIn API Terms of Use
- LinkedIn Marketing API Program Terms
- LinkedIn Community Management API Terms
- LinkedIn's Data Processing Addendum
- All applicable data protection laws (GDPR, CCPA, etc.)
Prohibited Activities:
We commit to NEVER:
- Exceed our authorized API access limits
- Attempt to reverse-engineer LinkedIn's APIs
- Circumvent LinkedIn's security measures
- Access LinkedIn data for purposes outside those explicitly authorized
- Share your access tokens with any third party
- Use LinkedIn data in ways that violate LinkedIn's Terms or your consent
Third-Party Access:
No Third-Party Sharing:
- We do not share your LinkedIn data with advertisers
- We do not share your LinkedIn data with data brokers
- We do not share your LinkedIn data with analytics providers
- We do not share your LinkedIn data with other ForaPost users
Exception - Service Providers:
- Cloud hosting provider (AWS) may process encrypted LinkedIn data
- Infrastructure providers cannot decrypt or access LinkedIn data
- All service providers are contractually bound to LinkedIn API Terms
Questions or Concerns:
For LinkedIn-specific privacy questions:
- Email: privacy@foragentis.com
- Subject: "LinkedIn Privacy Question"
- We will respond within 48 hours
3.4 Google API Services (YouTube)
ForaPost's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
What This Means:
- We only use YouTube data to provide the video publishing features you have authorized
- We do not use YouTube data for advertising, market research, or AI/ML training
- We do not transfer YouTube data to third parties except as necessary to provide the Service
- We do not allow humans to read your YouTube data except with your consent, for security purposes, or to comply with law
YouTube Comments: When you connect your YouTube account, ForaPost may access comments on your YouTube videos to display audience engagement within your dashboard and enable you to respond to comments on your behalf. Comment data is used solely to provide this feature and is not used for advertising, market research, or AI/ML training.
Your Controls:
- You may revoke ForaPost's access at any time through Google security settings: security.google.com/settings/security/permissions
- Upon access revocation, we will delete your YouTube data within 30 days
- You can disconnect your YouTube account from ForaPost at any time in Settings
Compliance:
- We comply with YouTube API Services Terms of Service
- We comply with YouTube's Developer Policies
- We do not download or redistribute YouTube content
3.5 Meta Platforms (Facebook, Instagram, Threads)
- We comply with Meta Platform Terms and Developer Policies
- We only request permissions necessary for publishing
- We do not use Meta data for purposes other than providing the Service
- We do not sell data obtained from Meta platforms
- We allow you to disconnect and delete your data at any time
3.6 Google Drive
ForaPost's use of Google Drive data adheres to the Google API Services User Data Policy, including Limited Use requirements.
What This Means:
- We only access files you explicitly select through the Google Picker
- We use file contents solely to learn your brand voice and create content
- We do not use Google Drive data for advertising, market research, or AI/ML training beyond your personalization
- We do not share your Google Drive files with third parties
- We do not allow humans to read your files except with your consent, for security purposes, or to comply with law
Your Controls:
- You choose exactly which files to import — we cannot access others
- You may revoke access at any time: myaccount.google.com/permissions
- Upon revocation, we delete access tokens immediately; imported analysis is retained unless you request deletion
3.7 Dropbox
- We only access files you explicitly select through our file browser
- We use file contents solely to learn your brand voice and create content
- We do not share your Dropbox files with third parties
- We comply with Dropbox's API Terms of Use and Platform Policy
Your Controls:
- You choose exactly which files to import — we cannot access others
- You may revoke access at any time: dropbox.com/account/connected_apps
- Upon revocation, we delete access tokens immediately; imported analysis is retained unless you request deletion
3.8 E-commerce Platforms (Shopify, WooCommerce, Etsy, Amazon)
- We access product catalog data (titles, descriptions, images, prices, inventory) necessary for content creation
- For Shopify, we additionally access aggregated order data from the past 30 days (order timestamps, product variant identifiers, and quantities sold) to predict per-product sales velocity. We use this to avoid scheduling posts that promote products predicted to sell out within seven days — protecting your inventory and the buyer experience
- We do not access customer personal information, shipping or billing addresses, payment methods, or financial transaction details
- Product and aggregated order data is used solely for content scheduling and recommendations
- We do not sell or share your product or order data with third parties
- We comply with each platform's API terms and developer policies
Your Controls:
- You may disconnect any e-commerce platform at any time in Settings
- Upon disconnection, product data is deleted within 30 days
- You may request immediate deletion by contacting privacy@foragentis.com
3.9 Bluesky
ForaPost's use of Bluesky complies with Bluesky's Terms of Service, Developer Guidelines, Community Guidelines, and AT Protocol standards.
What Data We Access:
When you connect your Bluesky account to ForaPost, we access:
| Data Type | Specific Data | Purpose |
|---|
| Profile Information | Handle (username), display name, avatar image | Identify your connected account in ForaPost |
| Account Credentials | App Password tokens | Authenticate and post on your behalf |
| Post Engagement | Likes, reposts, replies, quote posts (only for posts published via ForaPost) | Display analytics in your dashboard |
| Account Status | Connection status, last sync time | Maintain integration |
What We Do NOT Access:
We cannot and will not access:
- ✗Your private direct messages
- ✗Your follower lists or following lists
- ✗Your home timeline or feed content
- ✗Posts from other users (except public engagement on your posts)
- ✗Your muted or blocked accounts
- ✗Your notification preferences
- ✗Your lists or starter packs
- ✗Content from other AT Protocol applications you use
How We Use Bluesky Data:
Publishing Only:
- We use your Bluesky authorization solely to publish posts you explicitly create, edit, or approve within ForaPost
- Content is transmitted to Bluesky via the AT Protocol
- We do not modify, analyze, or store your published content after transmission
Engagement Analytics:
- We retrieve basic engagement metrics (likes, reposts, replies, quote posts) only for posts you published through ForaPost
- Metrics are displayed in your ForaPost dashboard
- We do not access engagement data for posts you created directly on Bluesky
Profile Display:
- We display your handle and avatar to identify your connected account
- This information is stored securely and deleted within 24 hours of disconnection
Understanding the AT Protocol (Decentralized Network):
Bluesky runs on the Authenticated Transfer Protocol (AT Protocol), a decentralized social networking protocol. This has important implications for your data:
What Decentralization Means:
- Your content is distributed across multiple servers (not just Bluesky's)
- Other applications built on AT Protocol may access your public posts
- Content you publish becomes part of a decentralized network
- No single company controls the entire network
Content Deletion on Decentralized Networks:
- When you delete content, we immediately remove it from our systems
- We notify the AT Protocol network that you have deleted your content
- However, due to the decentralized nature of AT Protocol, we cannot force other services to delete cached or distributed copies
- Complete deletion across the entire network may not always be possible
- Some posts may continue to exist on other AT Protocol applications outside our control
What This Means for You:
- Think carefully before posting, as complete deletion may not be guaranteed
- Content published through ForaPost may appear on other AT Protocol apps
- We are not responsible for content retention by other AT Protocol services
- To request removal from other services, contact them directly
Developer Guidelines Compliance:
As a Bluesky developer, ForaPost commits to the following:
No Spam:
- We do not produce bulk or scripted interactions
- We do not create fake followers or engagement
- We do not use account-creation tools
- All posts are explicitly created or approved by you
Content Deletion:
- We maintain a system for deleting content when you request it
- We process deletion requests promptly
- We notify the AT Protocol network of deletions
- We comply with Bluesky's content deletion requirements
User Reports:
- We maintain a system for responding to user reports of violations
- We investigate reported issues promptly
- We take appropriate action on confirmed violations
- We keep records of reports and our responses
Security Measures:
- We maintain reasonable security measures to protect your data
- App Password tokens are encrypted at rest (Fernet: AES-128-CBC with HMAC-SHA256 authentication)
- All data transmission uses TLS 1.3 encryption
- Access to Bluesky data is logged and audited
- Regular security assessments and penetration testing
Your Bluesky Data Controls:
Before Connecting:
- Bluesky will show you what permissions ForaPost requests
- You can review and decline authorization at any time
- Bluesky uses "App Passwords" for third-party applications
While Connected:
- View your connected Bluesky account in Settings → Connected Accounts
- See when ForaPost last accessed your Bluesky account
- Review all posts scheduled or published to Bluesky
- Monitor engagement metrics for your Bluesky posts
Disconnecting from ForaPost:
- Disconnect your Bluesky account with one click in Settings
- App Password tokens are deleted immediately
- Profile data is deleted within 24 hours
- Engagement data is deleted within 48 hours
- Published post records retained for up to 1 year for analytics (deletable on request)
Revoking Access Through Bluesky:
You can revoke ForaPost's access directly through Bluesky:
- Open Bluesky app or website
- Go to Settings → Privacy and Security
- Select "App Passwords"
- Find "ForaPost" in your list of app passwords
- Click "Revoke" or "Delete" to remove access
What happens after revocation:
- We receive notification that access was revoked (or detect it on next API call)
- All App Password tokens are deleted immediately (within 1 hour)
- Profile data is deleted within 24 hours
- Engagement data is deleted within 48 hours
- We cannot post on your behalf until you reconnect and create a new App Password
Data Deletion Requests:
Request immediate deletion of all Bluesky-related data:
- Email: privacy@foragentis.com
- Subject: "Bluesky Data Deletion Request"
- Include: Your ForaPost account email and Bluesky handle
We will delete within 30 days:
- All Bluesky App Password tokens (immediate)
- All profile information (handle, display name, avatar)
- All engagement data and analytics
- All historical post records related to Bluesky
Cannot be deleted:
- Content already published to Bluesky and distributed across AT Protocol network (manage through Bluesky directly and contact other AT Protocol services)
- Anonymized, aggregated analytics that cannot be attributed to you
Data Retention:
| Data Type | Retention Period |
|---|
| App Password tokens | Deleted immediately upon disconnection |
| Profile data (handle, avatar) | Deleted within 24 hours of disconnection |
| Engagement data | Retained for 48 hours after retrieval, then aggregated |
| Aggregated analytics | Up to 1 year; deletable on request |
Compliance & Legal Requirements:
We comply with:
- Bluesky Terms of Service
- Bluesky Developer Guidelines
- Bluesky Community Guidelines
- Bluesky Privacy Policy
- AT Protocol specifications and standards
- All applicable data protection laws (GDPR, CCPA, etc.)
Prohibited Activities:
We commit to NEVER:
- Produce spam or scripted bulk interactions
- Create fake followers or engagement
- Abuse Bluesky features (lists, labels, moderation tools)
- Engage in mass reporting or harassment
- Compromise or exploit Bluesky's systems or APIs
- Bypass rate limits or security features
- Use Bluesky data for purposes outside those explicitly authorized
- Share your App Password tokens with any third party
Third-Party Access:
No Third-Party Sharing:
- We do not share your Bluesky data with advertisers
- We do not share your Bluesky data with data brokers
- We do not share your Bluesky data with analytics providers
- We do not share your Bluesky data with other ForaPost users
Exception - Service Providers:
- Cloud hosting provider (AWS) may process encrypted Bluesky data
- Infrastructure providers cannot decrypt or access Bluesky data
- All service providers are bound by confidentiality obligations
AT Protocol Developer Applications:
Important Notice:
- If you use other applications built on AT Protocol, those applications have their own terms and privacy policies
- We are not responsible for the content or practices of other AT Protocol applications
- Your public posts on Bluesky may be visible to users of other AT Protocol applications
- To understand how other apps handle your data, review their privacy policies
Questions or Concerns:
For Bluesky-specific privacy questions:
- Email: privacy@foragentis.com
- Subject: "Bluesky Privacy Question"
- We will respond within 48 hours
For issues with your Bluesky account or AT Protocol:
3.10 Pinterest
ForaPost integrates with Pinterest through the Pinterest API (v5) to provide content publishing, Pin scheduling, and engagement features within the Service. You connect a Pinterest business account via Pinterest's OAuth flow. ForaPost is an independent product that uses the Pinterest API; it is not endorsed by, affiliated with, sponsored by, or otherwise officially connected to Pinterest, Inc.
Compliance & Scope:
- We comply with the Pinterest Developer Guidelines, the Pinterest Developer and API Terms of Service, and the Pinterest Acceptable Use Policy.
- Access is OAuth-only — we never see, request, or store your Pinterest password.
- We only request the OAuth scopes necessary for the features you choose to enable. In plain language: ForaPost can view your boards, create boards on your behalf, create and publish Pins on your behalf (at your direction), and read basic account information and engagement metrics for content you publish through ForaPost. We do not request scopes we do not use.
- You consent to each action ForaPost takes on your Pinterest account at the time you authorize that action (e.g., scheduling a Pin, publishing a Pin, viewing engagement).
- This Privacy Policy is intended to be consistent with applicable data-protection laws and with Pinterest's requirement that integrating apps maintain a lawful, accurate privacy policy.
Real-Time Access, Not Retention:
Our core compliance posture for Pinterest is live access, not data warehousing. Specifically:
- Engagement metrics (impressions, saves, clicks, outbound clicks on Pins published through ForaPost) are fetched live from Pinterest each time you view them and are not persisted in our databases as a historical analytics warehouse.
- Comments and replies on Pins are fetched live from Pinterest when you open the relevant view; ForaPost does not maintain a long-lived mirror of Pinterest comment threads.
- Any in-session analysis ForaPost performs on Pinterest data to power Service features is transient — used to render the response and then discarded.
- Pinterest data accessed through your authorization is used solely to provide the Service to the individual user who connected the account. We do not combine your Pinterest data with data from other users' accounts, do not use it to train cross-account AI models, do not use it for competitive benchmarking, do not use it to generate aggregate analytics for purposes unrelated to your use of the Service, and do not use it for advertising.
What ForaPost Retains and Why:
Consistent with the Pinterest Developer Guidelines, ForaPost does not warehouse Pinterest data. The only items associated with your Pinterest connection that ForaPost stores in its own systems are:
- Your Pinterest OAuth token — encrypted at rest (Fernet symmetric encryption) and used solely to make the authorized API calls you direct ForaPost to make on your behalf.
- The opaque identifier(s) you have selected as publishing destinations and as the account this connection belongs to — for example, the Pinterest user ID associated with your authorization and the board ID(s) you have chosen as destinations for Pins you create in ForaPost. These are configuration values you provided when you connected the account and chose where Pins should publish; we do not enrich them or store the surrounding profile or board data.
- Pin IDs that ForaPost itself created on your behalf, retained so that you can review and manage the content you published through ForaPost. This is consistent with Pinterest's exception for campaign-style information about content posted from your own account through ForaPost.
- Your ForaPost-authored content — drafts, scheduled Pins, captions, and media you created or uploaded inside ForaPost. This is your content, not data fetched from Pinterest.
Everything else — your profile details, the names and contents of your boards, your followers, your Pin engagement metrics, comments on your Pins, audience demographics, and any other information returned by the Pinterest API — is fetched live from Pinterest each time it is needed to render a view in ForaPost and then discarded. We do not maintain a historical database of this information.
No Resale, No Redistribution:
We do not sell, license, redistribute, or otherwise share Pinterest content or Pinterest-derived data with any third party, other than the limited service providers necessary to operate the Service (e.g., cloud hosting), which are bound by confidentiality and use restrictions.
What Happens When You Disconnect:
- Your Pinterest OAuth access token is revoked and permanently deleted from our systems within 24 hours.
- The configuration identifiers and Pin IDs described above (board destination IDs you selected, the Pinterest user ID for the connection, and the Pin IDs for content ForaPost created) are permanently deleted within 30 days.
- Because engagement metrics and comments are fetched live and not warehoused, there is no separate historical analytics store to purge — once the token is revoked, ForaPost has no further means of reading Pinterest data on your behalf.
- Pins you published while connected remain on Pinterest under your control — disconnecting from ForaPost does not retroactively remove Pins from Pinterest.
How to Revoke ForaPost's Pinterest Access:
- From ForaPost: Settings → Connected Accounts → Disconnect.
- From Pinterest directly: pinterest.com/settings/apps-and-accounts.
4. How We Share Your Information
We do not sell your personal information.
We share information only in the following circumstances:
4.1 Social Media Platforms
When you use ForaPost to publish content, that content is transmitted to your connected platforms. Each platform's privacy policy governs how they handle your content after publication.
4.2 Service Providers
We share information with third-party vendors who assist in providing the Service:
| Provider | Purpose | Data Shared |
|---|
| Stripe | Payment processing | Billing information |
| Railway | Application hosting | All service data the application processes |
| Amazon Web Services | File storage | Files you upload and media we create for you |
| AI text providers: DeepSeek, OpenAI, Anthropic (Claude), Moonshot AI (Kimi) | Writing posts and other text, learning your brand voice, analyzing images and videos you upload, and transcribing audio (OpenAI) | Prompts built from your brand information, uploaded and imported content, and post drafts |
| Replicate | AI image creation | Image prompts built from your brand information and posts |
| Kie.ai, fal.ai | AI video creation | Video prompts and, for a video made from an image, that image (for example, your product photo) |
| DeepSeek (vision), with OpenAI as a backup | Checking AI-generated images for visible defects before they publish | AI-generated images |
| Titan (email provider) | Sending account, billing and service email | Your name, email address and the email content |
| Axiom | Log storage for troubleshooting and security | Technical logs, which may include account identifiers and email addresses |
| Slack | Internal alerts to our team (for example, a new payment) | Your email address and the plan or item you paid for |
| Google Analytics, Ahrefs | Website analytics (see Section 8.5) | Device, browser and page-view data |
| Google Ads | Measuring sign-ups from our Google Ads (see Section 8.5) | A sign-up conversion event and Google's cookie and device identifiers, only if you arrived from one of our Google ads |
| OpenWeather | Local weather for timely post ideas | Your business's city or location |
| Shopify | Billing for merchants who installed ForaPost from the Shopify App Store | Store, plan and subscription status |
| Google | Cloud storage integration | Files you select to import |
| Dropbox | Cloud storage integration | Files you select to import |
| Shopify/WooCommerce/Etsy/Amazon | E-commerce integration | Product data (to/from your store) |
All service providers are contractually obligated to protect your information and use it only for specified purposes. Some of these providers process data outside the United States; see Section 10. For data obtained from Google APIs, our service providers are also required to adhere to the Google API Services User Data Policy, including Limited Use requirements.
4.3 Legal Requirements
We may disclose information if required by law, legal process, or government request, or to:
- Protect rights, property, or safety
- Detect, prevent, or address fraud or security issues
- Respond to valid legal requests
4.4 Business Transfers
If Foragentis is involved in a merger, acquisition, or sale, your information may be transferred. We will notify you of any such change.
4.5 With Your Consent
We may share information for other purposes with your explicit consent.
5. Data We Do NOT Collect, Sell, or Share
To be clear, ForaPost does NOT:
- ✗Sell your personal information to anyone
- ✗Sell your social media data to data brokers
- ✗Share your data with advertisers for targeting
- ✗Create profiles for sale to third parties
- ✗Aggregate your data with other users for commercial sale
- ✗Use your data to train AI models sold to others
- ✗Share your authentication tokens with third parties
- ✗Access your private messages on any platform
Note: This section applies to data you provide as a ForaPost user, including your brand content, social media accounts, collateral, and business information.
6. Data Retention
We retain your information for as long as necessary to provide the Service:
| Data Type | Retention Period |
|---|
| Account information | Until account deletion |
| Platform access tokens | Until disconnection + 24 hours |
| LinkedIn profile data | 24 hours after disconnection |
| LinkedIn activity data | 48 hours after retrieval, then aggregated |
| LinkedIn access tokens | Deleted immediately upon disconnection |
| LinkedIn post analytics (aggregated) | 1 year after publication; deletable on request |
| Bluesky App Password tokens | Deleted immediately upon disconnection |
| Bluesky profile data | 24 hours after disconnection |
| Bluesky post engagement data | 48 hours after retrieval, then aggregated |
| Bluesky post analytics (aggregated) | 1 year after publication; deletable on request |
| Published post records | 1 year after publication |
| Uploaded collateral | Until deletion or account termination |
| Imported cloud storage files | Processed immediately; original files not stored; analysis retained until account deletion |
| E-commerce product data | Synced while connected; deleted within 30 days of disconnection |
| Payment records | As required by law (typically 7 years) |
| Free market scan requests (email and business details) | Kept with the report until you ask us to delete them |
| Campaign and prospect attribution cookies | 90 days |
| Inactive accounts | Deleted after 60 days of inactivity plus a 14-day warning (see below) |
| Analytics data | 2 years (anonymized) |
After Account Deletion:
- Account information: Deleted within 30 days
- Platform tokens: Deleted immediately
- Uploaded content: Deleted within 30 days
- Published content: Remains on platforms (managed through those platforms)
Inactive Accounts:
We delete accounts that are no longer used. An account counts as inactive when, for 60 days in a row, nobody has signed in to it, it has had no paid subscription or active trial, and no posts have been created, scheduled or published. When an account reaches 60 days of inactivity we email a warning. Signing in cancels the deletion and restarts the 60 days. If the account is still inactive 14 days after the warning, we delete it, and its data is permanently removed 30 days after that. Accounts with an active paid subscription are never deleted for inactivity.
7. Data Security
We implement industry-standard security measures:
- Encryption of data in transit (TLS/SSL)
- Encryption at rest of the access tokens and app passwords for your connected accounts (Fernet: AES-128-CBC with HMAC-SHA256 authentication)
- Secure authentication and password hashing
- Regular security assessments
- Access controls limiting employee access
- Secure cloud infrastructure
- Regular security training for employees
While we strive to protect your information, no method is 100% secure. You are responsible for maintaining the security of your account credentials.
8. Your Rights and Choices
8.1 Account Management
- Access: View your information in Settings
- Update: Modify your profile and preferences at any time
- Delete: Delete your account through Settings or by contacting us
- Export: Request a copy of your data
8.2 Connected Account Management
- View: See all connected social media, cloud storage, and e-commerce accounts in Settings
- Disconnect: Remove any connected account at any time with one click
- Revoke: Revoke access through each platform's security settings
8.3 Platform-Specific Revocation
You can revoke ForaPost's access directly through each platform:
- Google/YouTube/Drive: myaccount.google.com/permissions
- Dropbox: dropbox.com/account/connected_apps
- Facebook: facebook.com/settings?tab=applications
- Instagram: Managed through Facebook settings
- LinkedIn: linkedin.com/psettings/permitted-services
- • Revokes access to both personal profiles and organization pages
- • We delete access tokens within 1 hour of revocation notice
- • Profile/page data deleted within 24 hours
- • Activity data deleted within 48 hours
- • Published content remains on LinkedIn (manage directly through LinkedIn)
- Twitter/X: twitter.com/settings/connected_apps
- TikTok: tiktok.com/setting (Manage Account → Security)
- Bluesky: bsky.app/settings/app-passwords
- • Delete the App Password you created for ForaPost
- • We delete your App Password token immediately upon disconnection
- • Profile data deleted within 24 hours
- • Engagement data deleted within 48 hours
- • Published content remains on the AT Protocol network (see Section 3.9 for details)
- Shopify: Your Shopify Admin → Apps → ForaPost → Remove
- WooCommerce: Your WordPress Admin → WooCommerce → Settings → Advanced → REST API
- Etsy: Your Etsy Account → Settings → Apps → Revoke access
- Amazon: Seller Central → Settings → User Permissions → Manage
8.4 Communications
- Unsubscribe: Opt out of marketing emails via unsubscribe link
- Transactional: Essential service emails cannot be opted out
8.5 Cookies
We use the following cookies and similar technologies:
| Cookie or tool | What it does | How long it lasts |
|---|
| Sign-in cookies (access_token, refresh_token, and the agency equivalents) | Keep you signed in to your account. Required for the Service to work. | Until they expire or you sign out |
| Security cookie (csrf_token) | Protects your account against cross-site request forgery. | 24 hours |
| Campaign attribution cookie (__foragentis_utm_campaign) | Set when you arrive through a link from a Foragentis campaign. It records which campaign brought you to us so we can measure it across Foragentis products. | 90 days |
| Prospect attribution cookie (__foragentis_utm_prospect) | Set when you arrive through a link in an email we sent you. It stores an identifier for that email's recipient so we can tell that the email led to your visit or sign-up. | 90 days |
| Google Analytics | Measures how visitors use our website (pages viewed, device and browser). Google sets its own cookies for this. | Set by Google |
| Ahrefs Analytics | Measures traffic to our website, including visits from search engines. | Set by Ahrefs |
| Google Ads conversion tag | If you came to us from one of our Google ads, tells Google once that you signed up, so we can measure the ad. | Set by Google |
You can block or delete cookies in your browser settings. If you block the sign-in or security cookies, you will not be able to sign in.
9. California Privacy Rights (CCPA)
If you are a California resident, you have additional rights:
9.1 Right to Know
Request information about:
- Categories of personal information collected
- Purposes for collection
- Categories of third parties with whom we share
- Specific pieces of personal information collected
9.2 Right to Delete
Request deletion of your personal information, subject to certain exceptions.
9.3 Right to Opt-Out
We do not sell personal information. If this changes, we will provide an opt-out mechanism.
9.4 Right to Non-Discrimination
We will not discriminate against you for exercising your privacy rights.
9.5 Exercising Your Rights
Contact us at:
We will verify your identity before processing your request.
10. International Users
ForaPost is operated from the United States. If you access the Service from outside the United States, your information will be transferred to and processed in the United States.
Some of the service providers listed in Section 4.2 process data in other countries. In particular, DeepSeek and Moonshot AI (Kimi) are based in China. DeepSeek is our main AI provider for writing and for checking images, and Kimi is a backup we use only when our other AI providers are unavailable. When they are used, the content we send them (prompts built from your brand information, uploaded content, post drafts and AI-generated images) is processed in China.
By using ForaPost, you consent to this transfer and processing.
11. Children's Privacy
ForaPost is not intended for users under 18 years of age. We do not knowingly collect information from children. If we learn we have collected information from a child under 18, we will delete it promptly.
12. Third-Party Links
ForaPost may contain links to third-party websites. We are not responsible for their privacy practices. Review the privacy policies of any third-party services you use.
13. Changes to This Policy
We may update this Privacy Policy periodically. We will notify you of material changes by:
- Posting the updated policy with a new "Last Updated" date
- Sending an email notification for significant changes
- Displaying a notice within the Service
Your continued use after changes take effect constitutes acceptance.