Semantec SEO · Project responsibilities
Security Overview
Use this page for project access, safe communication and reporting a security concern. Agree the information and permissions needed for a project before sharing sensitive material or authorising website changes.
A general security statement is not a certification or proof that a particular control has been tested. Project responsibilities and any assurance must match the agreed work, the relevant environment and the evidence supporting the statement.
Limit project information
Share only the information needed for the agreed work or the question being raised. Keep information for different clients, projects and purposes distinguishable. Confirm that you have permission to share business, specialist or personal information.
Identify sensitive material before it is sent. Agree a suitable route and handling requirements for the project. Do not include unrelated personal information or confidential files simply because they are available.
Agree permissions and access
Where a project needs website or service access, agree the purpose, authorised people, permissions and period before access is granted. Give only the access needed for that work and use the safeguards supported by the relevant service.
Review permissions when the work changes or ends. Do not bypass a site owner’s controls or use another person’s credentials without authority. Website changes need the approval and release responsibilities stated in the project scope.
Use safe communication
Do not send passwords, authentication codes, secret keys, full payment card details or unrelated sensitive information through an ordinary enquiry. Describe the issue and ask for a suitable route when protected material is needed.
Use support@semantecseo.com for project questions and privacy@semantecseo.com for privacy, security or legal questions. Include the relevant URL, project and minimum context needed. An email thread is not permission to access data or systems beyond the agreed work.
Separate service responsibilities
An external service has its own operator, terms, permissions and security statements. Its assurances do not certify Semantec SEO or establish how a separate project is handled. A provider name alone does not explain who receives client information.
Identify the services, recipients and handling requirements before a project requires sensitive data or system access. Privacy information must describe the processing concerned. Ask questions before transfer where those details are unclear.
Check website changes
A plan, code sample, checklist or staging result does not establish that a change is safe in the target website. Review the relevant CMS, theme, plugins, scripts, permissions and data before release.
Agree suitable recovery arrangements for changes that could affect the website or its information. Keep a record of concerns and decisions. General guidance does not replace the agency’s agreed project work or legal responsibilities.
Report a security concern
Email privacy@semantecseo.com with the subject “Security report”. Include the affected URL or service, date and time, observed behaviour, possible impact and the minimum safe steps needed to describe the concern.
Leave out other people’s data, credentials and unnecessary exploit material. Reporting an issue does not authorise intrusive testing or access. This page does not promise a reward, guaranteed response time, certification or immunity from attack.
