Her finner du en samlet, strukturert oversikt over hvordan GoRabbit fungerer – for kunder, tekniske brukere og governance/styring.
Data protection + safe operations.
Security in GoRabbit means three things: (1) protecting customer data and tokens, (2) ensuring stable operation without Facebook restrictions, and (3) maintaining governance, traceability and auditability. The platform is designed to minimize risk across all levels — technical and operational.
Always encrypted, never in Git.
tokens.json contains sensitive Facebook session cookies. The proprietary internal mechanism handled automatically by the system. Access is permission-controlled and all changes are logged in Slack for audit purposes.
Strict permissions and isolated directories.
All keys and tokens reside in folders with tightly restricted read/write access. Public or shared folders are never used for sensitive files. Each proprietary internal mechanism handled automatically by the system.
Never store tokens in Git.
Tokens, cookies, keys and customer-specific data must never be pushed to Git. The repo contains only code and configuration templates. Sensitive files remain proprietary internal mechanism handled automatically by the system.
proprietary internal mechanism handled automatically by the system.
GoRabbit reduces risk through proprietary internal mechanism handled automatically by the system. The entire system is engineered for safe large-scale operation.
Full GDPR alignment.
Yes. GoRabbit does not process personal data beyond what Facebook exposes in the normal user interface. The system stores no names, emails or private information. No customer data is sent to third parties. All operations follow GDPR principles.
Full traceability across systems.
All critical actions are logged: login attempts, proprietary internal mechanism handled automatically by the system. Everything is stored in Slack and proprietary internal mechanism handled automatically by the system.
Slack = real-time monitoring.
Slack provides real-time monitoring of everything happening inside GoRabbit: risk events, errors, proprietary internal mechanism handled automatically by the system. The system ensures developers catch issues before customers do.
Security across multiple layers.
Multi-level security means stacking protections: account security (tokens), operational safety (proprietary internal mechanism handled automatically by the system.
No personal data stored.
No. GoRabbit stores no personal data. The system only uses Facebook’s public group and page IDs, and images or teasers uploaded by the customer. This makes the platform inherently privacy-friendly.
Account health constantly monitored.
GoRabbit monitors risk signals, posting failures, warnings and behavioral changes from Facebook. Upon detecting risk, cooldown activates, proprietary internal mechanism handled automatically by the system. The system always protects the account first.
AI-assisted risk detection.
Yes. The system analyzes patterns from posting errors, timing anomalies, DOM behavior and user activity to predict when Facebook is approaching restrictions. The AI model enables pre-emptive action.
Automatic proprietary internal mechanism handled automatically by the system.
If an proprietary internal mechanism handled automatically by the system. The proprietary internal mechanism handled automatically by the system. This is a core part of GoRabbit’s reliability.
Full transparency and strong routines.
Customers receive full transparency on security policy, operations, proprietary internal mechanism handled automatically by the system. GoRabbit provides an enterprise-level security experience.
Multi-layer security + full traceability.
GoRabbit uses multi-layer security to protect tokens, customers, operations and account health, combined with full traceability, AI-based risk detection and enterprise-grade governance — designed for safe and scalable operations.
Documented rules for all operations.
Governance means GoRabbit operates under documented procedures that ensure quality, security and stable operation. This includes rules for tokens, operations, error handling, proprietary internal mechanism handled automatically by the system. All modules follow a unified standard.
Owner, Developer, Operator.
There are three roles: (1) System Owner — responsible for security, tokens and critical operational decisions, (2) Developer — maintains code and tools, (3) Customer Operator — uses the system but has no access to tokens or technical files.
GoRabbit operates — customer owns content.
GoRabbit manages the platform, operations, security and posting logic. The customer owns all content, images, teasers and Facebook accounts. GoRabbit never receives the customer’s Facebook password — only session cookies stored on the customer’s machine.
Every 2–4 weeks as needed.
Tokens should be rotated when Facebook requests re-login, when risk is detected or after security-related events. Cookies normally last for months. GoRabbit recommends periodic checks every 2–4 weeks depending on campaign load.
Staging → testing → production.
Change control means all changes to code, selectors, UI adaptation and configurations follow a defined procedure: staging → test → production. Nothing is updated directly without verification. This protects customers from downtime.
Dedicated staging environment.
Yes. A dedicated proprietary internal mechanism handled automatically by the system. UI changes, new modules and risk adjustments are tested here before being pushed live. This keeps the platform safe even when Facebook changes rapidly.
Only campaign data — never personal data.
Customer data is stored only in GoRabbit Studio (frontend database) and consists of campaign information, teasers and images uploaded by the customer. GoRabbit never stores more than strictly required, and nothing is shared with third parties.
Encryption + offline proprietary internal mechanism handled automatically by the system.
Yes. tokens.json and all sensitive files are encrypted or stored in secure directories. Communication between modules is proprietary internal mechanism handled automatically by the system. This reduces the attack surface significantly.
No open ports. Outbound only.
No. GoRabbit runs locally on the proprietary internal mechanism handled automatically by the system. All external communication is outbound only, limited to Facebook and Slack API. This provides very high security and minimal exposure.
Code in Git — tokens proprietary internal mechanism handled automatically by the system.
RabbitEngine, RabbitAgent and Studio code is stored in Git and can be restored at any point. tokens.json and proprietary internal mechanism handled automatically by the system. No sensitive data is sent to cloud services outside of customer control.
Full recovery in under 30 min.
Yes. In case of critical failure or loss of a server, a new proprietary internal mechanism handled automatically by the system. Tokens are restored from customer backup. The entire system can be operational again in under 30 minutes.
Customer retains full control.
Yes. GoRabbit never requests passwords and never modifies account settings. The customer retains full control. GoRabbit only uses session cookies generated by the customer via login in their own browser.
Instant reporting + safe mode.
All security events are reported instantly in Slack. The system enters safe mode (cooldown), logs the incident and provides clear instructions for next steps. Events are documented and included in the audit trail.
proprietary internal mechanism handled automatically by the system.
The system uses proprietary internal mechanism handled automatically by the system. No actions are performed faster than a human realistically would. Account health is monitored continuously.
Layered security.
GoRabbit operates under a layered security model: technical safety (tokens, permissions, encryption), operational safety (proprietary internal mechanism handled automatically by the system. The result is an extremely safe platform.
proprietary internal mechanism handled automatically by the system.
The proprietary internal mechanism handled automatically by the system. If risk is detected, posting frequency decreases, proprietary internal mechanism handled automatically by the system. This gives extreme robustness.
Full isolation between staging and production.
Yes. Staging runs on its own proprietary internal mechanism handled automatically by the system. Production is never affected by tests. Changes are validated in staging before deployment. This eliminates downtime risk and reduces errors dramatically.
All internal communication is proprietary internal mechanism handled automatically by the system.
All data flow is proprietary internal mechanism handled automatically by the system. No internal APIs or hidden network calls are used. This makes the system robust, easily debuggable and extremely secure.
Customer data is fully isolated.
Each customer is isolated into its own segment in Studio and its own proprietary internal mechanism handled automatically by the system. proprietary internal mechanism handled automatically by the system. This ensures both compliance and operational safety.
Engineered for minimal Facebook risk.
GoRabbit automates user actions, so it must operate within safe boundaries: low posting frequency, proprietary internal mechanism handled automatically by the system. The system is engineered for minimal risk. Customers use their own accounts and remain responsible, while GoRabbit manages all risk mitigation.
INFO → WARNING → ERROR → CRITICAL.
GoRabbit uses several log levels: INFO (normal operation), WARNING (unexpected DOM behavior), ERROR (posting stopped), CRITICAL (risk signals), SECURITY (proprietary internal mechanism handled automatically by the system. This provides full insight and audit depth.
Yes, with dynamic risk control.
Yes. The proprietary internal mechanism handled automatically by the system. This prevents aggressive posting patterns that could trigger Facebook restrictions.
Tokens = passwords. Never in cloud.
Tokens provide full access to the user’s Facebook account and must therefore be treated as passwords. They must never be stored in Dropbox, Google Drive or Git. Only proprietary internal mechanism handled automatically by the system. This is a core principle of GoRabbit security.
tokens.json + cookies + proprietary internal mechanism handled automatically by the system.
The following are considered sensitive: tokens.json, session cookies, user-specific proprietary internal mechanism handled automatically by the system. These must never be moved without security procedures.
Yes, with regular maintenance.
Yes. The system undergoes periodic checks of tokens, group proprietary internal mechanism handled automatically by the system. This ensures smooth and stable operations without surprises.
proprietary internal mechanism handled automatically by the system.
GoRabbit uses no open ports, no exposed APIs, no third-party cloud storage for tokens, and outbound-only network traffic. It operates isolated, proprietary internal mechanism handled automatically by the system.
Development → staging → production.
The DevOps model follows a clean pipeline: development → staging → Slack monitoring → production. No changes are pushed before they are tested in staging. This eliminates the risk of downtime, breakage, posting failures or UI surprises from Facebook.
Full transparency available.
Yes. Customers may access Slack logs, audit trail data, risk analysis and any blocks related to their own account. This provides full transparency and builds trust.
Safe, controlled and responsible system.
Clients should know that GoRabbit never stores passwords, never shares data, never posts aggressively, always follows proprietary internal mechanism handled automatically by the system. The system is built for safe and responsible posting.
Enterprise-grade security without compromise.
GoRabbit is built as an enterprise-secure, proprietary internal mechanism handled automatically by the system.