FFyLinx

Privacy Policy

Effective: 28 September 2026 Service: FyLinx Website: fylinx.runxera.com

This Privacy Policy explains what information FyLinx processes, why it is processed, how Google user data is used, where information is stored, when information may be shared, how long information is retained, and the controls available to users of the FyLinx Windows desktop application.

FyLinx is designed primarily as a local desktop photo-processing and delivery tool. Connecting a cloud storage provider, including Google Drive, is optional and occurs only when the user chooses to configure that integration.

Google API Services User Data Policy. FyLinx's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

1. Information FyLinx processes

Photos and local files

FyLinx processes photos that the user places in or selects through a configured source folder. Photo resizing, optional watermarking, temporary preparation, and related image operations occur locally on the user's Windows device. FyLinx does not require users to upload source photos to a FyLinx-operated server for processing.

Application settings

FyLinx stores application settings locally on the user's device. These may include source and backup folder locations, cloud destination settings, image resize preferences, watermark preferences, automatic upload settings, provider selection, and connection configuration.

Google OAuth and connection information

If the user connects Google Drive, Google handles the sign-in and authorization flow. FyLinx receives OAuth authorization data needed to access the Google Drive resources permitted by the user. OAuth tokens and the associated FyLinx/rclone configuration are stored locally on the user's device.

FyLinx does not ask the user to provide their Google password to FyLinx, and FyLinx does not store the user's Google password.

2. Google Drive permission requested

FyLinx requests the following Google Drive scope:

https://www.googleapis.com/auth/drive.file

This limited permission allows FyLinx to create Drive files and to work with specific Drive files or folders created by, opened with, or otherwise made available for use with FyLinx. FyLinx does not request the broader https://www.googleapis.com/auth/drive scope for full access to all files in the user's Google Drive.

3. Why Google user data is accessed and how it is used

Google user data is accessed only to provide functionality requested by the user, including:

  • authenticating the Google Account the user chooses to connect;
  • maintaining an authorized Google Drive connection on the user's device;
  • creating or accessing Drive destinations used with FyLinx;
  • uploading processed photos to those destinations;
  • checking or performing Drive operations needed to complete an upload workflow initiated or configured by the user; and
  • allowing the user to reconnect or disconnect Google Drive from FyLinx.

FyLinx does not use Google user data for advertising, behavioural profiling, credit decisions, data brokerage, or sale of personal information.

4. Data collection by the FyLinx website

The public website at https://fylinx.runxera.com/ provides product, privacy, and terms information. Viewing these public pages does not require a FyLinx account or Google login.

The website does not itself request Google Drive authorization. Google OAuth authorization is initiated from the FyLinx desktop application when the user chooses to connect Google Drive.

5. Data storage and security

FyLinx stores its application configuration and cloud authorization configuration locally on the user's Windows device. Users are responsible for protecting access to that device and Windows user account.

Processed photos are sent directly from the user's device to the cloud provider selected by the user. FyLinx does not operate a central photo-processing service that keeps an additional server-side copy of those uploaded photos.

Temporary local working files created during image processing or upload preparation are used only for the workflow and are removed according to the application's normal processing lifecycle.

6. Data sharing and third-party services

FyLinx does not sell Google user data or photos processed through the application.

Information is transmitted to Google only as necessary to authenticate the user and perform Google Drive operations requested through FyLinx. Google processes information according to Google's own terms and privacy policies.

FyLinx uses rclone as a local transfer component for supported cloud integrations. rclone runs on the user's device as part of the desktop application's cloud-transfer workflow and uses the provider authorization configured by the user.

FyLinx does not transfer Google user data to third parties for advertising, marketing databases, profiling, or unrelated commercial purposes.

7. Retention

Local FyLinx settings remain on the user's device until they are changed, reset, or removed by the user or the application. OAuth tokens remain locally available until they expire, are refreshed or replaced, the local connection configuration is removed, or access is revoked by the user.

Photos uploaded to the user's own cloud account remain subject to that cloud provider's storage settings and the user's actions. Local originals and backup copies remain under the user's control according to the FyLinx settings selected by the user.

8. Disconnecting FyLinx and revoking Google access

Users can disconnect the configured Google Drive connection from within FyLinx. Users can also revoke FyLinx's access from their Google Account's third-party connections or security settings.

Revoking Google authorization prevents FyLinx from obtaining new Google access tokens until the user explicitly authorizes the application again.

9. Deleting local FyLinx data

Because FyLinx stores its application configuration locally, users can remove local FyLinx configuration and authorization data from their device. Disconnecting the cloud provider and revoking access from the Google Account are recommended when the user no longer wants FyLinx to access Google Drive.

Removing FyLinx from a device does not automatically delete photos already stored in the user's Google Drive; those files remain under the user's control in their Google Account and can be deleted there by the user.

10. User choices and control

Users control:

  • whether Google Drive is connected at all;
  • which Google Account is authorized;
  • the local source and backup folders;
  • the Drive destination used for uploads;
  • image resize and watermark settings;
  • whether automatic upload is enabled; and
  • whether Google authorization is later disconnected or revoked.

11. Children's privacy

FyLinx is a professional desktop photo workflow and is not directed to children. The service is not designed to knowingly collect children's personal information.

12. Changes to this Privacy Policy

This Privacy Policy may be updated when FyLinx functionality, cloud integrations, data practices, or legal requirements change. The effective date shown at the top of this page identifies the current version.

13. Contact

For privacy questions, data-practice questions, or support related to FyLinx, contact support@runxera.com.

FyLinx website: https://fylinx.runxera.com/

Runxera website: https://runxera.com/