Security at JubKub

1. Our security approach

JubKub is designed around Privacy by Design and Data Minimization. We aim to reduce unnecessary transmission of user data whenever the requested functionality can be provided locally.

Different tools may use different architectures, so we aim to clearly distinguish browser-based tools from features that require server-side processing.

2. Browser-based processing

Where browser technology allows it, JubKub aims to process files directly on the user's device.

This approach reduces unnecessary data transfer and the need for JubKub to maintain server-side copies of files.

3. Preserving original content

JubKub follows a Preserve Original Fidelity principle for file conversion, compression and modification tools.

• We do not automatically translate user content.
• We do not create new content unless requested.
• We do not intentionally rewrite text inside files.
• We avoid unnecessary layout changes.
• We aim to preserve language, text, dimensions and document structure as closely as the format allows.

Where a file format or conversion cannot preserve the original perfectly, JubKub should disclose the limitation rather than claiming 100% fidelity.

4. Business documents and customer information

We recognize that users may process company documents, product images, customer materials and internal business information using JubKub.

JubKub does not sell the private contents of user files, business documents or customer data to third parties.

For tools that process files locally, the architecture is designed so those files do not need to be transferred to JubKub.

5. HTTPS and connections

When JubKub is deployed on its production domain, the website will be served over HTTPS to encrypt data in transit between the browser and the website.

HTTPS improves transport security but does not mean that any online system can guarantee absolute security.

6. Server-based tools

Some future tools may require server-side processing, such as certain file conversions, backend services or features requiring persistent processing.

If a tool requires file upload, JubKub should clearly disclose that requirement and provide relevant information about processing and retention.

7. Databases and URL shortening

Certain features such as a URL shortener require data to be stored so redirects can continue to function.

These services will be architected separately from tools that can use local processing, with data collection limited to what is reasonably required for the feature.

8. Analytics

JubKub may use analytics to measure visitor counts, page usage, tool usage and website performance.

Measuring tool usage does not mean JubKub reads the private contents of files processed locally inside the browser.

9. Security headers and infrastructure

When deployed to production, JubKub will apply appropriate technical controls such as HTTPS, security headers, administrative access restrictions and infrastructure security settings.

These controls will be reviewed as JubKub's actual architecture and services evolve.

10. Vulnerability handling

If abnormal behavior or a potential vulnerability is identified, we aim to investigate, remediate and improve relevant controls as appropriate.

Once JubKub's contact channel is available, users and security researchers will be able to report potential security issues through that channel.

11. No system is 100% secure

12. Privacy Policy

For more information about how JubKub may collect, use and disclose data, please review our Privacy Policy.