Security

Understand key security considerations for Octoparse accounts, task access, credentials, cookies, and exported data.

Security matters when a task uses login credentials, cookies, cloud execution, team access, or automated exports. This page summarizes the main areas to review when using Octoparse in individual or team workflows.

Key security areas

Account access

Protect account credentials and review who can access shared tasks or exports.

Login and cookies

Handle authenticated sessions carefully when scraping login-required websites.

Export destinations

Make sure exported data is sent only to approved files, sheets, databases, or cloud storage.

Team governance

Assign task ownership and review access when team members change roles.

Account and team access

Use clear access practices when multiple users work in the same account or workspace.

Recommended practices:

• Use individual accounts where possible
• Avoid sharing passwords informally
• Remove access when users no longer need it
• Keep task ownership clear
• Review who can edit tasks, run tasks, or access exported data
• Use strong account authentication settings where available

Credentials and cookies

Some tasks require login or session cookies. Treat these as sensitive because they may allow access to account-specific website content.

Before saving or running login-required tasks, check:

Check	Why it matters
Permission to access data	Login access does not automatically allow data reuse
Session stability	Expired cookies can break task runs
Account risk	Repeated automation can trigger website security checks
Team visibility	Other users may be able to access task setup or outputs
Cloud execution	Session-dependent workflows may behave differently in cloud runs

Export security

Exported data may contain business, customer, pricing, contact, or operational information. Review export destinations carefully.

Best practices:

• Send data only to approved destinations
• Use dedicated folders, sheets, or tables
• Limit access to exported files
• Avoid exposing credentials in task names or field values
• Monitor automated exports after changes
• Coordinate with data owners before connecting databases or cloud storage

Compliance and permitted use

Before collecting data, confirm:

• The target website permits the intended access
• The data use is allowed by applicable terms and laws
• Sensitive or personal data is handled appropriately
• Internal compliance requirements are met
• Exported data is stored in approved systems

Octoparse is a data collection tool. You are responsible for making sure your tasks, credentials, exports, and downstream use comply with website terms, applicable laws, and your organization’s policies.