Политика безопасности и хранения данных

Программа безопасности

Мы применяем административные, технические и организационные меры защиты, направленные на охрану платформы и содержащейся в ней конфиденциальной информации о проектах, капитале и организациях. Они включают контроль доступа, шифрование при передаче, заголовки безопасности и политику безопасности контента, администрирование по принципу наименьших привилегий и аудиторское журналирование чувствительных действий. Ни одна система не является абсолютно защищённой, и мы не гарантируем абсолютной безопасности.

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.