SECURITY AT EDITHUBS
Security
How EDITHUBS is designed to protect uploaded files, processing activity, accounts, and the supporting service infrastructure.
Effective August 31, 2026
Security practices you can understand
This page explains how EDITHUBS protects file transfers, processing workflows, accounts, and supporting service infrastructure.
1. Security approach
EDITHUBS uses secure web connections, controlled file processing, limited file retention, account safeguards, and technical controls designed to support safe use of the service.
2. Protected file transfers
Connections to the EDITHUBS website use HTTPS to protect data while it is transmitted between supported browsers and the service.
3. Controlled file processing
Uploaded PDFs, images, and documents are processed to perform the operation selected by the user. File-processing workflows limit unnecessary access and uploaded content is not used for advertising or unrelated profiling.
4. Automatic file cleanup
Uploaded and processed files are retained temporarily and are automatically removed when their two-hour retention period expires. Temporary processing files may be removed sooner.
5. Account security
Many tools can be used without an account. Account services use password protection, session controls, authentication safeguards, password-recovery protections, and account-management features.
6. Google sign-in
Where Google sign-in is available, EDITHUBS uses it for account authentication. Google independently processes authentication information under its own terms and privacy practices.
7. Access control
Access to service administration and supporting systems is managed as part of EDITHUBS security and operational practices.
8. Infrastructure and service providers
EDITHUBS may use service providers for infrastructure, authentication, communications, security, and related operational functions. Additional information about service-provider data handling is available in the Privacy Policy.
9. Monitoring and abuse prevention
EDITHUBS uses technical controls such as request limits, file-validation safeguards, and service logs where applicable to help reduce abuse and investigate operational or security issues.
10. Vulnerability management
EDITHUBS updates and maintains service components as the platform evolves. Security concerns can be reported through the Contact page for review.
11. Incident response
When a security issue is identified, EDITHUBS may investigate and take appropriate technical or operational action based on the nature of the issue and applicable requirements.
12. Backups and recovery
Users should keep original copies of important files. EDITHUBS file-processing services are not intended to serve as permanent file storage or backup.
13. User responsibilities
Users should keep original copies of important files, review processed output, protect account credentials, use trusted devices, avoid suspicious links, and promptly report suspected unauthorized access or security issues.
14. Security transparency
EDITHUBS provides clear security information about the protections and operational practices used by the service.
15. Reporting a security concern
Security concerns should be submitted through the EDITHUBS Contact page with enough detail to investigate the issue safely. Users should not access, alter, download, or disclose data that does not belong to them while researching a possible vulnerability.
16. Updates to this page
This Security page is updated as service architecture, protections, providers, retention practices, and applicable requirements evolve.
Security that evolves with the service
Security information is updated as EDITHUBS improves infrastructure, authentication, file handling, monitoring, and account protections.
NEED MORE INFORMATION?
Contact the EDITHUBS team
Use the Contact page for questions about this document, accounts, files, security, privacy, or the EDITHUBS service. Security concerns: info@edithubs.com
Contact us