Veri işleme

Verilerinizin nerede barındırıldığı, neyin toplandığı, ne kadar saklandığı ve kimin erişebildiği — hizmetin bugünkü yapılandırmasıyla.

Barındırma: KZSürüm 2026-10-17
Where data lives
MongoDBAccounts, organizations, workspaces and monitored materials; Social Space comments, direct messages and connected-account credentials live in a separate scano_social database on the same servers in Kazakhstan.
ElasticsearchA search index of monitored materials, hosted alongside the application in Kazakhstan.
RedisShort-lived cache entries, locks and event streams; Redis is not a system of record.
S3-compatible object storageMedia files attached to materials and generated reports; the bucket is provided by the hosting provider.
RabbitMQTransient queues between the crawlers and the ingest pipeline; a message is removed once it has been processed.
BackupsMongoDB backups are taken daily and written to object storage.
What we collect
Account dataName, e-mail address, role, a bcrypt hash of the password, and login records (time, IP address, browser).
Connected-account tokensOAuth access and refresh tokens for the social accounts a workspace connects, stored encrypted.
Comments, messages and posts from connected accountsComments, mentions, direct messages and posts fetched from the platforms for the connected accounts, scoped to the workspace that connected them.
Public material for monitoringPublic news articles and social posts that match a workspace's keywords, with the author's public name or handle, avatar link, publication time and engagement counts.
Billing dataCard details are entered on Stripe's hosted checkout and never reach Scano servers; Scano stores the Stripe customer id, subscription id and billing status.
Product activity journalActions users take in the product (for example exports and workspace changes), kept for 3 months.
Retention
Account and workspace dataKept while the account is active; after the 30-day grace period of a deletion request the data is removed by Scano staff through the erasure pipeline, and automation of that step is planned.Planlanıyor
Audit log24 months, then deleted by the daily journal cleanup.
Activity journal3 months, then deleted by the daily journal cleanup.
Material metrics snapshots180 days, enforced by a database TTL index.
Monitored materialsEach ingested material is stamped with a retention horizon (RETENTION_DAYS, default 730 days from publication); the purge job that enforces it is planned.Planlanıyor
YouTube API dataComments and replies fetched from the YouTube API are deleted 30 days after they were last stored or refreshed.
LinkedIn API dataMember comments and commenter profiles are read live from the LinkedIn API and are not stored; the retention job additionally enforces a 48-hour cap on member comments and a 24-hour cap on commenter profile data.
Meta platform data (Facebook, Instagram, Threads)Deleted on request of the user or of Meta through the erasure pipeline; an automated deletion-callback endpoint and the annual Data Use Checkup are planned.Planlanıyor
Telegram dataTelegram data is not used to train machine-learning models.
Outreach e-mail bodiesMessage bodies and recipient addresses are blanked 90 days after sending (Outreach module).
Sign-up verification tokensDeleted at expiry by a database TTL index.
Stripe webhook recordsEvent identifiers are kept 90 days, enforced by a database TTL index.
Connected-account tokensKept while the account is connected; on disconnect the credential is detached from the workspace and no longer used; deletion of detached credentials is planned.Planlanıyor
Deletion
Account deletion requestAn organization admin can request deletion of the organization in the product; the request is recorded in the audit log, the Scano team is notified and a 30-day grace period starts.
Cancelling a requestAn organization admin can cancel the request within the grace period; the cancellation is recorded in the audit log.
Purge after the grace periodAfter the grace period the organization's data is removed through the erasure pipeline by Scano staff; automation of this step is planned.Planlanıyor
Erasure of a person's dataA request about a person appearing in monitored material is executed by Scano staff through the erasure pipeline across MongoDB, Elasticsearch, object storage and caches, and is recorded in an erasure log.
Suppression listAn erased or objecting person is added to a suppression list so re-crawled content about them is dropped before ingest.
Platform-initiated deletionDeletion callbacks from Meta and Google (YouTube) are planned; today such requests are handled through the erasure pipeline.Planlanıyor
Disconnecting an accountDisconnecting detaches the stored credential from the workspace so it is no longer used; deleting the detached credential and the account's stored comments is planned.Planlanıyor
Access control
RolesThree roles per organization (admin, manager, guest) with permissions assigned per role; superuser is a separate flag held only by Scano staff.
Organization scopingEvery read and write is scoped to the caller's organization; cross-organization access is refused.
Staff admin panelThe staff admin panel is served from a separate host; restricting its API to a private network via a secret header (admin host gate) is implemented in code and its enforcement in production is planned.Planlanıyor
AuthenticationPasswords are hashed with bcrypt; sessions use short-lived JWTs delivered in Secure, HttpOnly cookies; repeated failed logins are rate-limited.
Audit logLogins, user and role changes, workspace membership, integration connect/disconnect, exports, billing and data-lifecycle events are recorded with actor, IP address and browser, kept 24 months, and visible to the organization's admins.
SecretsApplication secrets are read from the environment; their source of truth is an encrypted secrets repository (SOPS), and a pre-commit and CI scan block secrets from entering the code.
Encryption
Connected-account tokens at restEncrypted with Fernet (AES-128-CBC with HMAC-SHA256); keys can be rotated without downtime (MultiFernet).
PasswordsStored as bcrypt hashes; never in clear text and never written to logs.
In transitThe product is served over HTTPS; session cookies are marked Secure in production.
Database volumesEncryption of database volumes at rest is planned.Planlanıyor
Sub-processors
ResendTransactional e-mail (invitations, password resets, notifications); region: US.
StripeSubscription billing for self-serve plans; card data stays with Stripe; region: US.
SentryApplication error tracking; reports may include request metadata; region: US.
AnthropicLanguage model for the AI Analyst, which receives monitored material text only when the feature is enabled for an organization; region: US.
Social platform APIsGoogle/YouTube, Meta (Facebook, Instagram, Threads), TikTok, VK, Telegram, X, LinkedIn and Reddit, used to read and reply on the accounts a workspace connects; each exchange goes to the platform the account belongs to.
Hosting providerVirtual servers and S3-compatible object storage in Kazakhstan.
Monitoring and logging
Audit eventsThe events listed under audit_events are written to the audit log with actor, IP address and browser.
Error trackingUnhandled errors are reported to Sentry in every non-local environment.
Application logsServer logs are written on the application host; HTTP client loggers are silenced so URLs carrying tokens are never logged.
Login monitoringFailed and rate-limited login attempts are recorded in the audit log.
Infrastructure alertsHost, database and ingest-freshness alerts are sent to the Scano team by the operations monitoring units.
Incident handling
AlertingService and host alerts reach the Scano team through the operations monitoring units; application errors reach the team through Sentry.
RunbooksWritten runbooks exist for deployment, backup and restore, and secret rotation.
Secret exposureA secret committed by mistake must be reported immediately and rotated; the rotation steps are documented.
Customer notificationA written procedure for notifying affected customers after a security incident is planned.Planlanıyor
Change management
Version controlAll application code is in Git; commit messages follow a fixed format enforced by hooks and CI.
Automated checks before deployEvery push to the main branch runs the test suite and the linter; the production deploy runs only when both pass, one deploy at a time.
Secret scanningEvery commit is scanned for secrets, credential files and oversized files locally (pre-commit) and in CI.
Protected branchesForce-pushing to or deleting the main branch is blocked by the Git server.
Peer reviewA mandatory review step before production deploys is planned.Planlanıyor
Your rights
Access and exportMonitored materials and journals can be exported from the product; a copy of account data can be requested at info@scano.kz.
ErasureErasure of your account or of your personal data in monitored material can be requested at info@scano.kz; requests are executed through the erasure pipeline and logged.
Account deletionOrganization admins can request deletion of the whole organization in the product (see Deletion).
ObjectionA person who does not want to appear in monitored material can ask to be added to the suppression list at info@scano.kz.
Contactinfo@scano.kz

Verilerinizle ilgili sorular: info@scano.me

Çerezler oturumunuzun açık kalmasını sağlar ve izninizle, Scano'nun nasıl kullanıldığını anlayarak onu geliştirmemize yardımcı olur. Daha fazla bilgi için: Çerez politikası.