Faryen is a social publishing service operated by Ingeniom LLC, 30 N Gould St Ste N, Sheridan, WY 82801, United States. Contact us at office@faryen.com. This policy covers the Faryen website and app.

Information you give us

We process your sign-in email, workspace name and timezone, the accounts you select, drafts, captions, uploaded media, scheduled times, comment plans, and support messages you send us. We also record publishing status and errors so you can see what happened to each destination. Our hosts process request and error logs needed to operate and protect the service.

Platform access and why we use it

You choose which social accounts to authorize. Faryen receives account identifiers and names, a platform access token, and the data covered by the permissions you grant. Tokens are kept in protected server-side storage and are not sent to the browser app. We use platform access to show the accounts you can select, publish the posts and comments you schedule, confirm publishing outcomes, and display available insights. We do not sell social account data.

For Facebook Pages and linked Instagram professional accounts, the Meta connection requests pages_show_list, pages_read_engagement, pages_manage_posts, pages_manage_engagement, read_insights, instagram_basic, instagram_content_publish, instagram_manage_comments, instagram_manage_insights, and business_management. These permissions let Faryen show available Pages and business assets, identify linked professional accounts, publish selected content, manage follow-up comments, and retrieve available Page and Instagram insights. Meta may also require pages_read_user_content as a dependency of the connection. We use that Page visitor-content access only for the account and comment functions you authorize.

For TikTok, YouTube, Pinterest, X, and LinkedIn connections, the authorization screen identifies the access requested by that platform. Faryen uses only the account, publishing, comment, and insights data made available for the features you authorize on that connection. Availability varies by account type, post format, and platform API.

Google and YouTube data

Faryen uses YouTube API Services. When you connect a channel, we access its channel identity, authorized video information and available analytics. We store the channel connection, protected authorization tokens, publishing receipts and the reporting data shown in your workspace. We send the videos, titles, descriptions, visibility choices and eligible comments you explicitly choose to publish. YouTube Analytics access supports the channel and content reports you request.

We use Google API data for these visible account, publishing and reporting features. We do not sell it, use it to target advertisements, or use it to train general-purpose AI models. Faryen's use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. Google's handling of information is described in the Google Privacy Policy.

You can revoke Faryen's Google access at any time in your Google account permissions. To delete information held by Faryen, use the account controls or contact us as described below. Removing data from Faryen does not delete videos or comments already held by YouTube.

Disconnecting YouTube in Social accounts removes its stored channel details, reports and remote post/comment references from Faryen, while preserving your own writing and original media. Faryen requests revocation at Google immediately; if that request fails, a restricted encrypted token is kept only for bounded revocation retries, for no more than six days. It cannot be used for publishing or reporting. Google may also revoke related channel connections.

While a connection remains authorized, Faryen refreshes channel identity and checks retained videos. Data that cannot be revalidated is removed on a 28-day expiry schedule. A confirmed rejected grant removes the associated stored YouTube data. Historical authorized statistics can remain while authorization is rechecked. Removing Faryen data does not remove the original content from YouTube.

When you authorize a YouTube connection, Ingeniom LLC processes the Google and YouTube data described above to provide your requested Faryen features. The following service providers may process that data on our behalf for the stated purposes:

Supabase: runs Faryen's authentication, database, private media storage and server functions. It stores and processes channel identifiers and profile information, authorization tokens, video and comment references, publishing records, and YouTube analytics used in your workspace.
GitHub Actions: runs our private backup and recovery jobs. Its temporary runners process database and media exports, which can contain Google and YouTube data, to create encrypted backups and verify recovery. Temporary working files are removed after the jobs; customer data is not published in the source repository or public build artifacts.
Backblaze B2: stores the encrypted off-site backup copies created by those jobs. Backup contents are encrypted before upload, using a recovery password held separately from the stored backup.
Netlify: serves the Faryen website and app and processes web-request metadata and OAuth callback requests needed for hosting and security. The app displays your authorized channel data in your browser; Google access and refresh tokens remain in Faryen's protected server-side storage.

Google and YouTube also receive the videos, metadata, privacy settings and comments you instruct Faryen to send through their APIs. Content you choose to publish is made available according to the visibility you select on YouTube. We do not share your Google authorization tokens or YouTube analytics with Resend, our email provider, or Stripe, our payment provider; those services process the separate account-email and billing information needed for their functions.

We limit transfers of Google user data to providing or improving the features you authorize, necessary security investigations, applicable legal obligations, or a business transfer with your prior explicit consent, as permitted by Google's Limited Use requirements. We do not transfer Google user data to advertising platforms, data brokers or information resellers. Human access is limited to assistance you affirmatively authorize, necessary security investigations, legal obligations, or permitted internal operations using aggregated data.

How we protect sensitive data

We use HTTPS/TLS to protect information in transit between your browser, Faryen's hosted services and Google APIs. Google access and refresh tokens are encrypted at rest in Supabase Vault and are read by authorized server-side functions, rather than returned to the browser app. Server credentials are kept in protected secret stores.

Authenticated workspace checks, database permissions and row-level security restrict access to stored account information and reports. Uploaded original media is held in private storage with authorized access controls. Administrative access is restricted to authorized operators for the purposes described in this policy.

Off-site database and media backups are encrypted before they are uploaded to Backblaze B2. Backup and recovery jobs use restricted credentials and temporary working storage; recovery copies follow the retention and deletion limits described below. These controls are designed to protect sensitive data against unauthorized access, disclosure, alteration and loss.

How long we keep information

We keep your workspace settings, connected account information, drafts, uploaded media, schedules, publishing records, and available analytics while needed to provide the service or until you remove the relevant item. We keep a platform token while its connection remains authorized; disconnecting or a verified deletion request ends its use and removes the stored credential, subject to the restricted Google revocation retry described above. Your own writing and local action history can remain after a connection is removed. See the data deletion instructions to request removal of related stored data.

Account deletion runs through a protected cleanup process. Limited records may remain where required for billing, security or legal obligations. Encrypted recovery copies follow backup retention rather than being rewritten immediately when an individual record is deleted.

Where information is handled

Supabase provides authentication, database, media storage, and server functions. Netlify hosts the website and app. Resend delivers account and operational emails. Stripe processes subscription and payment information; Faryen does not store full payment-card numbers. GitHub Actions runs private backup and recovery jobs, and encrypted off-site recovery copies are stored with Backblaze B2. Connected social platforms process information sent through their APIs under their own policies. The marketing website does not access your connected social tokens. The Google and YouTube data-sharing disclosures above explain which providers process that data and why.

Browser storage

The app uses browser storage for your sign-in session, workspace preferences and recovery of unfinished composer work, including locally selected media where supported. Signing out or confirming account deletion clears the app's local recovery data on that browser. Other devices and files you download remain under your control.

Your choices and deletion

In Faryen Settings, you can download your account data and request account deletion with password confirmation. Original media downloads are provided separately. Social accounts lets you disconnect a platform connection, and you can also revoke access in the platform itself.

For a copy, deletion of data for a specific connection, or questions about our privacy practices, email office@faryen.com from your account's email address. We verify the request before acting. See the data deletion instructions for the steps and the limits of deleting already published posts. Do not send passwords, access tokens or recovery links.

Changes to this policy

We will update this page when our data practices change and show the new date above. Material changes will receive appropriate notice.