Identity & access
Role-based permissions, least privilege, MFA, SSO, and lifecycle controls where supported.
Survey
A clear overview of how SierraTec Survey approaches platform protection, identity, data handling, incident response, vendor risk, and the shared responsibilities that help customers run safer studies.
Role-based permissions, least privilege, MFA, SSO, and lifecycle controls where supported.
Transport security, encryption practices, retention controls, and protected exports.
Risk-based monitoring, backups, recovery practices, and documented incident response.
Secure development, vendor review, subprocessor transparency, and shared responsibility.
This Security Policy summarizes SierraTec Survey’s customer-facing security commitments and practices. It does not disclose confidential defensive details and does not replace an Enterprise security exhibit, BAA, DPA, SLA, or other negotiated security terms.
SierraTec may support strong password requirements, multi-factor authentication, SSO, SAML, OpenID Connect, and other identity controls depending on plan and configuration. Customers should enable the strongest appropriate authentication options available to them.
SierraTec uses encryption and transport security appropriate to the information and systems involved. Specific encryption, key-management, and architecture details may be provided through applicable Enterprise security documentation where appropriate.
SierraTec may use reputable cloud and infrastructure providers. Hosting regions, redundancy, availability architecture, and data-residency commitments may vary by product configuration and written agreement.
SierraTec may maintain security, authentication, administrative, application, and infrastructure logs to detect abuse, troubleshoot issues, investigate incidents, and support compliance. Log access and retention should be limited according to operational and legal needs.
SierraTec maintains risk-based processes for vulnerability identification, dependency management, remediation prioritization, patching, and response.
SierraTec incorporates security considerations into software development and change management, including access controls, code review, dependency management, secret handling, testing, and deployment controls appropriate to the risk of the change.
SierraTec may maintain backups and recovery procedures for operational resilience. Backup architecture and recovery objectives may vary by service tier and Enterprise agreement. Backups are not a substitute for a Customer’s own archival obligations unless expressly agreed.
SierraTec maintains an incident-response process addressing identification, containment, investigation, recovery, documentation, and legally or contractually required notifications.
Where SierraTec acts as a processor, it will notify the applicable controller of qualifying personal-data breaches as required by the DPA and applicable law. Where SierraTec acts as controller, it will make required regulator or individual notifications.
Access to production systems and sensitive information is limited to authorized personnel based on job responsibilities. SierraTec uses confidentiality, onboarding, access-review, and offboarding practices appropriate to the Service.
SierraTec assesses material service providers based on the nature of access and risk and uses contractual, privacy, security, and confidentiality requirements appropriate to the services they provide.
SierraTec will make subprocessor information available where legally or contractually required.
Eligible plans may support SSO, domain verification, just-in-time provisioning, SCIM, and other administrative controls. Customers remain responsible for identity-provider configuration, provisioning logic, certificates, secrets, and role mappings.
Customers must protect API keys, webhook secrets, service-account credentials, and integration tokens. SierraTec may rate-limit, rotate, revoke, or disable credentials where necessary to protect the Service.
Security-related logs and records may be retained for periods appropriate to fraud prevention, investigations, legal obligations, and operational needs. Customer Content follows the applicable retention, deletion, and backup rules described in the Terms, Privacy Policy, and applicable agreements.
SierraTec Survey is not automatically approved for PHI. HIPAA-regulated use requires an expressly approved configuration and a BAA where required. Applicable subcontractors and security controls must be included within that approved environment.
Education customers should use appropriate role, sharing, retention, and identity controls. FERPA applicability depends on the institution’s use and legal basis, not merely on use of SierraTec Survey.
Suspected vulnerabilities or security incidents may be reported to info@sierratecsecure.com until SierraTec publishes a dedicated security contact. SierraTec may publish a dedicated vulnerability-disclosure or security-reporting channel as the Service evolves.
No online service can guarantee absolute security. SierraTec’s security measures are designed to reduce risk and should evolve with the threat environment, product architecture, and applicable obligations.
SierraTec may update this Security Policy as controls, infrastructure, certifications, vendors, or legal requirements change. Material contractual security commitments remain governed by the applicable written agreement.