Automate repetitive file-management tasks and organise a perfect document workflow based on Google Drive. Backup files to Google Drive and never loose important data again.
Book a free demo to talk with app creator, get an overview of the features, share ideas and receive 1 month subscription for free! 🚀
Features
Automatically provision Google Drive folders on item creation
Synchronize files from boards to Google Drive
Backup files to Google Drive
Convert item files to Google Drive links
Benefits
Automate repetitive tasks 🤖
Supports Google Docs and Sheets 📄
Backup files to Google Drive 🗄️
Centralise file changes on Google Drive 🎯
About us
ops42 is striving to provide best quality customer experience. Please use the following email to get in touch with us: [email protected]
Security & Compliance
Security
Does the developer periodically perform penetration testing?
No
Does the developer have a dedicated security and privacy point of contact for such issues or questions?
Does the app restrict redirects and forwards only to approved destinations, or show a warning when redirecting to potentially untrusted content?
No
The application does not have a user-facing interface which makes redirects (integration-only)
Does the app protect against mass parameter assignment attacks?
No
The application does not have a user-facing interface (integration-only)
Does the app perform encoding and sanitization on all user supplied parameters to protect against Cross-Site Scripting?
Yes
All user-supplied inputs are sanitized for XSS and validated. Application has 2 sources of user-provided data: 1. Recipe input fields 2. File and folder names The application has the following measures built-in: 1. All data from recipe input fields is sanitized with DOMPurify 2. All user-managed data from Google Drive, like file and folder names is sanitized with DOMPurify 3. Freetext data for folder URL is validated to be a real URL with whitelisted domains
Does the developer protect all state-changing actions against Cross-Site Request Forgery (CSRF)?
Yes
All requests to backend are authenticated with monday.com token. 1. Backend application is verifying request token from monday.com using monday.com signing secret.
Does the developer have mechanisms to notify monday.com in case of a security breach?
Yes
ops42 has an incident management procedure in place to notify monday.com in case of a breach
Does this developer have a process for installing application-level updates and security patches for the service (such as software packages and databases)?
Yes
Application leverages serverless NoSQL DB (AWS DynamoDB) which does not require updates from client. Application code is built and deployed by a CICD pipeline. GitHub Dependabot is used to keep package dependencies up to date.
Compliance
Is the app certified with the information security standard ISO/IEC 27001:2022?
Not answered
Is the app compliant with the Health Insurance Portability and Accountability Act (HIPAA)?
No
Is the app certified with System and Organization Controls (SOC 2 or SOC 3)?
No
Is the app compliant with the General Data Protection Regulation (GDPR)?
Yes
The application is not storing PII or user data apart from usage information. Third-party processors are compliant with GDPR.
Data
Does the app send any data outside of monday.com? If yes, indicate whether the data is customer-submitted (e.g., board names, item names, doc content) or non-customer-submitted (e.g., account ID, board ID, user ID).
Not answered
Where does the app store logs data?
Not answered
Where does the app store the app data?
Not answered
Does the developer ensure application logs do not contain secrets or personally-identifiable information (PII)?
Yes
Application logs are delivered to AWS Cloudwatch Logs log group. The log group has data protection policies enabled for automatic masking and reporting for all sensitive information findings. Enabled policies: Credentials, PII, PHI, Financial information
Is customer data segregated from the data of other customers (for example logically or physically)?
Yes
Software has a multi-tenant architecture. All customer data is segregated logically on the basis of the Account ID. Account ID is retrieved from application session.
Privacy
Does the developer enforce multi-factor authentication on employees access to systems which may process customer data?
Yes
Customer data is processed on AWS cloud. AWS Access is managed with SSO (AWS Identity Center) from Google Workspace. Google workspace has 2-Factor authentication enforced. AWS Root account has MFA set up.
Does the developer protect access to customer data based on the principle of least privilege?
Yes
The company has only one employee. User secrets like OAuth authentication tokens are encrypted with KMS key using client-side encryption.
Reviews
No reviews yet.
Installation history
We have data for December 28, 2024 onwards only. Collected sometime after 00:00 UTC daily.