安全与数据保留政策

安全计划

我们采用旨在保护平台及其所承载的机密项目、资本和机构信息的管理、技术和组织保障措施，包括访问控制、传输加密、安全响应头与内容安全策略、最小权限管理以及对敏感操作的审计日志。没有任何系统是完全安全的，我们不保证绝对的安全性。

What We Monitor

For authenticated platform accounts we record the in-app activity listed below, for auditability and support. Two limits are stated here rather than left to inference: this activity stream is written to local storage in the browser you are using and is read back from there — it is not yet a server-side log — and the platform events written to a server-side audit table today are limited to the following: administrative decisions on registrations, access requests and data-room requests, and the welcome email sent to a registered account; an administrator assuming another persona; and the creation, amendment or removal of a project record, which any member of that project can do and which records the field values submitted.

• Sessions & environment — a locally generated session identifier, the start of a session in a browser tab, and the device type, browser, operating system, and screen size your browser reports. Sign-out, session duration, IP address, IP-based location, and network provider are not recorded in this platform activity record: it has fields for IP address and IP-based location, which are left empty, and no field at all for sign-out, session duration, or network provider. An earlier version of this page listed them as recorded, which overstated what is implemented.
• In-app activity — pages and modules opened, projects and capital rooms viewed, documents viewed or downloaded, and searches. Form submissions are not recorded in this stream; an access request and the decision on it are stored with the request itself, not here.
• Security events — the browser-local activity stream carries a result field and a coarse in-app risk weighting, but no permission-denied or error outcome is written to it today. Detection of failed sign-ins, unusual download volume, and new-device or new-location logins is not yet implemented: a failed sign-in writes no record anywhere today. An earlier version of this page described those as monitored.

Where we do derive location from an IP address — for public-site page requests, not for in-platform activity — it is approximate and is not a verified physical address. We do not conduct covert screen recording; where activity reconstruction is needed, it is assembled from the event log described above. We do not sell activity data.

Administrative Access (Tiered)

Access to monitoring and analytics is restricted by role, on a need-to-know basis. Administrative decisions — approving or rejecting a registration, sending a welcome email — are recorded in an append-only audit table. Administrative reads are not yet recorded: an administrator opening the visitor analytics or a project workspace leaves no audit entry today. An earlier version of this page said every administrative access was logged, which overstated what is implemented.

• Analytics Viewer — aggregate analytics only.
• Security Admin — login, IP, security, and risk records.
• Compliance Admin — audit logs, legal flags, and public-records review.
• Platform Admin — operational and usage analytics.
• Super Admin — full visibility across the platform.

数据保留期限

以下为基准目标；确切期限由法务审查，并可能因法域和法律保全要求而有所不同：

• Security event logs — 1–7 years (a target for server-side security logging, which does not exist today)
• Audit records of administrative decisions — 3–7 years
• Login / session records — 1–3 years (a target; no login or session record is created today — see What We Monitor)
• 文档访问日志 — 3–7 年
• 页面与交互分析 — 12–24 个月
• 汇总／去标识化分析 — 保留更长时间
• 导出日志 — 3–7 年
• 支持记录 — 2–5 年
• 已删除账户记录 — 仅在法律必要范围内保留
• 敏感的部落事务（Tribal Affairs）记录 — 适用经治理机构批准的特殊保留与删除规则，并具备数据主权保护和严格的访问控制。

保障措施与治理

• 对所有监测与分析实行基于角色的访问控制。
• 数据最小化——我们只收集监督与安全所必需的数据，绝不多收。
• 敏感字段脱敏与导出控制，敏感导出须经批准。
• 任何涉及监控敏感性的功能在发布前均须经法律审查。
• 不出售用户活动数据；除已披露内容外不存在隐藏跟踪。

Server-side capture is active

Server-side capture is deployed. Page requests are recorded on our servers, including the country, region, city and time zone derived from your IP address and the network provider it belongs to. Your IP address itself is not stored: it is salted and hashed so a visit can be counted without retaining an identifier. The Privacy Policy describes what is collected and why. An earlier version of this notice said server-only signals such as IP address and geolocation were not collected; that described a prototype phase that has ended and was inaccurate while server-side analytics were live.

报告问题

如需报告安全漏洞，或就活动如何被监测或保留提出关切，请联系 applied@thecefa.org。