ReBALKAN treats security as a continuous process requiring regular review, technical improvement, access control, and risk assessment rather than a one-time setting. This page explains our general security approach in language users can understand. Protection thresholds, keys, and internal architecture details are not disclosed publicly for security reasons. No internet-based service can guarantee absolute security, so platform safeguards and responsible user behavior are both important.
From account access and data integrity to abuse prevention and incident handling, our approach is explained through twelve clear topics. Without exposing sensitive technical details, we describe the safeguards in place and the practical steps users should take to protect themselves.
Technical and organizational safeguards are applied to protect personal data, accounts, listings, and system integrity. Security controls are reviewed as risks and the platform evolve. Our priorities are reducing unauthorized access, preserving data integrity, limiting abuse, and supporting service continuity.
Users may sign in through supported identity providers such as Google or Facebook. ReBALKAN does not request or store the password used with that identity provider. Session cookies are configured to be sent only over secure connections and not to be readable by client-side browser code. Users remain responsible for signing out on shared devices, protecting their social account, and responding to unfamiliar sessions.
User, administrator, and other protected operations are subject to role and permission checks. Being signed in does not grant access to every resource. Administrative pages and data-changing operations are available only to accounts with the required authority. Unauthorized requests may be rejected, sessions may be restricted, or additional verification may be required.
The platform enforces HTTPS and supports secure transport policy in production. Browser security headers help prevent ReBALKAN pages from being embedded without permission on other websites. Data-changing forms use validation mechanisms where appropriate to reduce forged form requests and session misuse.
Suspicious path scans, repeated security probes, spam, and high-confidence abuse patterns may be evaluated by technical controls. Risky requests may be rejected and temporary access restrictions may be applied to the relevant IP address. These controls are developed to protect platform and server resources while minimizing the effect on legitimate users.
Publishing may be subject to account, phone verification, Coin, and administrative checks. Fake, misleading, illegal, spam-like, or rule-breaking content may be rejected, suspended, or removed. Users should not place identity documents, banking details, passwords, verification codes, or unnecessary personal information in listing titles, descriptions, or images.
Listing, Coin, Premium, and account operations verify the authenticated user, permissions, current record state, and applicable business rules on the server. Critical data-changing operations use validation, parameterized database queries, and transaction integrity where appropriate. Values submitted by the browser are not trusted on their own.
Limited technical records such as date, request path, related account identifier when available, and IP address may be retained to investigate errors, suspicious requests, and security incidents. Their purpose is troubleshooting, attack detection, and service security. Logging scope and cleanup processes are reviewed to avoid unnecessary records and unlimited retention.
Third-party providers may be used for authentication, cloud infrastructure, content delivery, measurement, or similar technical services. These providers maintain their own security and privacy terms. ReBALKAN aims to limit data to what the service requires and configure provider connections securely. Detailed processing information should be considered together with the Privacy and Cookie policies.
When suspicious access, possible account compromise, a data integrity issue, or another security incident is detected, the relevant session may be terminated, an account or IP may be temporarily restricted, content may be suspended, and a technical review may begin. Safeguards may be updated and required notification procedures may be followed according to the nature of the incident.
Do not share your password, SMS code, social-account verification code, or card details with anyone you meet through ReBALKAN. Do not pay before seeing the property or vehicle, verifying the other party, and establishing a safe contractual process. Unusually low prices, pressure to pay quickly, requests to leave the platform, and demands for identity information are important warning signs.
Users should protect the connected Google or Facebook account and their device, sign out on shared devices, and report suspicious account activity promptly. If you notice a page impersonating ReBALKAN, a suspicious message, a fake listing, or a possible vulnerability, send the details through the support channel available to your registered account. Never include a password, verification code, or unnecessary personal data in the report.
Send suspicious messages impersonating ReBALKAN, fake listings, unusual account activity or a possible vulnerability through the support channel available to your registered account. Never include passwords, verification codes or unnecessary personal data.
Review how data is processed and how cookies are used on the related policy pages, or contact our support team with a specific security report.