Security is our top most priority
(Hence we have a dedicated page to explain security measures in Jamku)
No System is 100% secure. Even Yahoo, LinkedIn, Facebook had instances of security breaches in past. So, does that mean that nothing is safe? NO. It means nothing is impregnable. It’s a cat and mouse game. We implement best security measures as per industry standards and keep on updating and monitoring these measures. With this introduction, let’s see how Jamku is secured.
How is my Data Stored?
This is the most common question we get, so here’s how your data is stored.
All the data relating to your office is stored in Buckets (Bucket is a metaphor to avoid using the technical jargons). All these buckets are locked until the user logs into the software. The below diagram shows how the data is structured and stored.
When a user logs in to jamku, system checks which all buckets the user is authorised for. If the system finds a single office bucket, it will unlock the bucket and allow the user to interact with the data inside the bucket based on the permissions assigned to the user.
In case, the system finds that the user is authorised to access more than one bucket, then it prompts the user which bucket it wants to login into. Thus, ensuring no unauthorised access to the bucket is possible.
What happens if the server goes down?
We aim for 99% uptime but server downtime is inevitable because the server will go down for some reason. Here are some of the safeguards that we have in place.
The server sits on top of the KVM architecture which makes it resilient to hardware failures. Every hardware has a redundancy. Eg – in case of a hard disk failure the RAID configuration will kick in and activate the failover SSD.
We have implemented Uptime Robot to monitor the server uptime. If the server goes down, it immediately notifies the entire development team of Jamku. We then figure out the issue and get the server up and running.
In an unfortunate event of total failure, we shall restore the backup from our Plan A. If Plan A fails we have a Plan B backup restoration. In case of Plan B failure, the data is restored from Plan C. This may result in data loss of up to 3 hours.
We believe in transparency, hence our uptime monitoring is publicly available for curious minds 🙂 Go to Uptime Monitoring
Why 99% and not 100%?
Server software needs to be updated on a regular basis to maintain the best in class security and performance. When the server software is updated, Jamku becomes temporarily