App privacy policy.

1. Information we handle and why

• Account and profile information: your SocketJack username, authentication information, account role, beta access, and any avatar, biography or profile links you choose to provide. We use these to sign you in, identify creators and manage access. Your SocketJack account can also be used in other SocketJack apps.
• Projects and collaboration: project names and descriptions, FL Studio project archives, samples, MIDI and other project files, versions, recovery copies, artwork, audio previews, invitations, membership and sharing choices. Supported session edits and project discussion messages are processed to let permitted participants work together.
• Connected cloud accounts: provider name, account identifier and display name, granted permissions, authorization tokens and deadlines, app-folder and file identifiers, file sizes and checksums, and transfer progress or errors. These let us connect the account you selected, transfer and verify your files, and identify connections that need attention.
• Service operation: IP address, username when available, request path without its query string, request method, response status, timing, transfer usage and error records. We use these for service operation, usage limits, troubleshooting, abuse prevention and administrator traffic summaries. The portal may send a public visitor IP address to ipapi.is to obtain approximate country, region and city information. This is IP-based geography, not your device's precise location.

Sign-in cookies and local browser preferences support authentication and interface behavior. The portal session cookie can last up to 120 days; signing out ends authenticated access. Browser controls let you clear cookies and local site data, which may require signing in again. Our request analytics do not retain request bodies, query strings, authentication cookies or cloud tokens.

2. Private projects, Public projects and collaborators

You control visibility and download permission in Manage project. Later working versions and recovery copies stay private until you explicitly publish another ZIP. Public audio previews are playable by visitors. Invitations grant access to the named collaborator; you can revoke that access.

Changing a project back to Private removes its public listing and public download access through SocketJack. Disabling public downloads stops further public ZIP downloads. Former public cloud snapshots are moved into Private in the background; provider outages can delay that folder update. Copies already downloaded, recorded or saved by other people cannot be recalled. Revoking collaboration also cannot erase another person's existing copies.

Private describes access through the service. It does not mean end-to-end encryption: the server processes project contents to provide synchronization and downloads. Authorized service administrators may access stored information where needed to operate, secure or troubleshoot the service or handle a request.

3. Dropbox, OneDrive and Google Drive

Connecting cloud storage is optional and uses the provider's authorization page. FruityLoopsCollab does not receive your cloud-account password. Dropbox and OneDrive use their application folders. Google Drive uses access to files created by, or specifically made available to, this app. We do not request broad access to unrelated drive files as part of the standard connection.

After connection, the app organizes Private and Public folders in the provider's app area (inside FruityLoopsCollab on Google Drive). Selecting cloud storage allows automatic transfers of project files, assets and recovery copies, including while you are offline. Files pass through the SocketJack service for permitted collaboration and downloads. Cloud capacity and availability are governed by your provider.

The Public folder stores the exact snapshots approved for public downloads. Neither its name nor moving a file into it manually grants public access through SocketJack. The integration does not automatically create provider-native public links or expose your cloud credentials to collaborators or downloaders. Sharing outside the app through your cloud provider follows that provider's settings.

Cloud authorization tokens are stored in protected server-side storage. They are not included in project ZIPs, VST state or shared download links. Administrators see connection status, account attribution and expiry or reconnect reminders; token values are not displayed in those reminders.

Disconnect stops transfers and removes the active tokens from the application's connection record. It preserves existing cloud files and connection or transfer records needed to explain and recover interrupted work. You can also revoke access in your cloud provider's account settings. To resume, reconnect the original account. Disconnecting does not delete a project or unpublish an existing public release; change project visibility separately.

Information obtained through Google APIs is used for the storage and collaboration features you choose. FruityLoopsCollab's use and transfer of this information adheres to the Google API Services User Data Policy and Google Workspace user data and developer policy, including their Limited Use requirements. Cloud-drive data is not used for advertising or to train general-purpose AI models.

Provider policies also apply: Dropbox, Microsoft and Google.

4. When information is shared

We share project information with the collaborators and audiences you select, and transfer files to the cloud provider you connect. Hosting, network delivery and necessary operational services process information to run SocketJack. External links, embedded content or provider sign-in pages may send your browser's ordinary connection information to their operators and follow their own policies.

We do not sell FruityLoopsCollab project content or connected-drive data. Information may also be accessed or disclosed when needed to comply with applicable law, investigate abuse, protect users or the service, or carry out a request you authorize. Do not include another person's private information in a public project without their permission.

5. Retention, deletion and your controls

Account, project, collaboration and recovery information is kept while needed to provide the service and preserve your work. Portal request logs and visitor analytics are currently pruned after 30 days, with size limits that may remove older entries sooner. Diagnostic records, transfer history and operational backups can have different retention periods; there is no published automatic deletion deadline for all stored information.

You can edit profile and project information, remove public previews or artwork, change project visibility, revoke collaborators, disconnect a cloud account, and use Delete project after its confirmation. Deleting a project removes its current service project and access, but does not recall downloaded copies or automatically erase files retained in your cloud drive. Manage those copies through your provider. Operational backups or records needed for security, legal obligations or resolving disputes may persist after removal from the active service.

For account deletion or access, correction and deletion requests that are not available in the interface, contact the operator below. We may need to verify that you control the account before acting. Available privacy rights depend on your location and applicable law; this policy does not promise a particular response or backup-removal deadline.

6. Contact and policy updates

For FruityLoopsCollab privacy questions, account deletion, or access, correction and deletion requests, email the operator, heirow, at zytonicrecords@gmail.com. Include your SocketJack username and the nature of your request. Do not send passwords or cloud authorization tokens. We will ask for any additional information needed to verify your request through an appropriate private channel.

We will update this page and its last-updated date when our practices change. Material changes to cloud access or publishing choices will also be explained in the relevant app flow before new permission is requested.