Secure password handling
Password-based accounts use secure one-way password hashing. Original passwords are not stored in readable form, and password changes replace existing credentials rather than exposing them.
Trust & Safety
Security and Data Protection
Resumes and account information can contain personal and professional data. ResuPulse uses multiple technical and operational safeguards designed to help protect that information while you use the platform.
Security principle
No online service can guarantee absolute security. This page explains our approach at a practical level without exposing sensitive internal security configuration.
Security Practices
How ResuPulse helps protect accounts and data
Security depends on several protections working together. The controls below describe the main areas we use to reduce risk without publishing sensitive implementation details.
Authentication and session safeguards
ResuPulse uses protected authentication and session mechanisms designed to reduce unauthorized account access and limit exposure of account credentials.
Request and input validation
Requests and uploaded files are checked against expected formats, sizes, permissions, and other validation rules before they are processed where applicable.
Access controls
Account-related information is checked against the authenticated user before protected records can be viewed, changed, or deleted. Features intentionally designed for link-based sharing follow separate access rules.
Abuse and availability protection
ResuPulse uses safeguards such as usage controls, monitoring, and abuse-prevention measures to reduce automated abuse, fraudulent activity, and unnecessary load on platform services.
Private document storage where required
Documents that need continued storage, such as recruitment files, are kept in private managed storage with controlled application access. Temporary resume-tool uploads follow the data-handling practices described in our Privacy Policy.
Data Protection
How information is handled across ResuPulse
Protecting information also depends on how it is transmitted, processed, stored, and accessed. We keep those responsibilities separated and use trusted service providers where infrastructure or specialized processing is required.
Transmission
Encrypted data in transit
Information sent between your browser and ResuPulse is transmitted over encrypted HTTPS connections. When a feature requires a trusted third-party processor, relevant information is transmitted securely as part of the requested service.
Storage
Storage based on feature needs
Some product records and generated results may be stored so features such as account history and reports can work. Documents that require continued storage are kept separately from temporary uploads where appropriate.
AI Processing
Only relevant information is processed
AI-assisted features may send the information needed for the requested task to an applicable AI provider. Uploaded resume PDFs used with applicable public tools are not intentionally retained as permanent tool files after processing.
Access
Access is limited by product context
Authenticated account data uses access controls tied to the relevant user. Reports or features intentionally designed to be shared through a unique link should be treated as private links and shared carefully.
Credentials
Service credentials stay server-side
Sensitive service credentials used to operate ResuPulse are kept outside browser-facing application code and are managed through protected server-side systems.
Privacy Controls
Data controls are documented separately
Account deletion, exports, guest-report requests, recruitment-data requests, retention information, and third-party processing details are documented in the ResuPulse Privacy Policy.
Responsible Disclosure
Found a possible security issue?
If you believe you have discovered a vulnerability affecting ResuPulse, send us enough information to understand and reproduce the issue safely.
Email Security TeamHelpful details to include
- The affected page, tool, or feature
- A clear description of the issue
- Steps that reproduce the behavior
- The potential security impact
- Screenshots or supporting information when useful
Please avoid
- Accessing another user's private information
- Changing or deleting data that is not yours
- Disrupting normal platform availability
- Running destructive or excessive automated tests
- Publicly disclosing sensitive details before we can review the issue