Table of Contents
The choice between cloud and local storage for a video intercom is not a feature preference. It is a decision about who controls the footage, who can be compelled to release it, what happens when the internet goes down, and what the system costs over five years rather than on day one.
Most video intercom systems on the market support one or both storage paths. Cloud storage sends recordings to a remote server managed by the manufacturer or a third-party provider. Local storage writes footage to a microSD card inside the indoor monitor or outdoor station. The two approaches differ on four dimensions that matter to property managers, developers, and building owners: recurring cost, privacy and legal exposure, operational resilience, and compliance with data retention rules.
Quick Comparison: Cloud vs Local SD Card Storage
| Dimension | Cloud Storage | Local SD Card Storage |
|---|---|---|
| Upfront cost | Low or bundled with device | Low (SD card: ~€10–€30 / $10–$35) |
| Recurring cost | Monthly or annual subscription | None for basic recording |
| Typical retention | 3–30 days (plan-dependent) | 7–30 days typical, capacity-dependent (32–128GB common; some models up to 512GB) |
| Privacy exposure | Footage transmitted to and stored by provider | Footage stays on-device, never leaves the property unless shared |
| Risk if device is stolen | Footage remains accessible off-site | Footage on that device may be lost |
| Operation without internet | Recording stops or becomes inaccessible | Recording continues; footage remains viewable locally |
| Legal compulsion | Provider may be compelled to release footage | Police must request footage from the owner, not a third party |
| Compliance burden | Shared responsibility with provider | Owner controls retention and access directly |
1. Cost: The Subscription Model Is Not Free, and the SD Card Is Not the Whole Cost
Cloud storage is rarely free for extended retention. Subscription pricing varies by provider and device count, but the pattern is consistent: monthly or annual fees in exchange for remote access and a defined retention window.
Consumer-oriented cloud plans commonly range from €3–€5 per month for basic retention. At the higher end, 30-day recurring cloud storage for four devices has been listed at $144.99 per year**; 7-day retention for one device at **$20.49 per year. These figures scale with device count and retention period.[1][2]
Local SD card storage eliminates the recurring fee for basic recording. A 32GB to 128GB microSD card typically costs €10–€30 (approximately $10–$35), and when the card fills, it overwrites the oldest footage with new recordings. Some systems support cards up to 512GB, extending retention without any subscription.[3]
The nuance: the SD card is not the only local cost. If the card fails—and microSD cards do fail, particularly in outdoor temperature-cycling environments—the footage on that card is lost. Cloud storage, by contrast, survives device theft or damage because the footage is off-site. The cost comparison must include risk of loss, not just the purchase price of the card.
2. Privacy and Legal Exposure: Who Can Access the Footage?
This is the dimension where the two approaches diverge most sharply, and it is the one most often underweighted in procurement decisions.
Local storage keeps footage on the property. The recording is written to a card inside the device; it does not traverse a manufacturer’s server unless the owner chooses to share it through an app. No third party can access the footage without physical access to the device or the card. From a privacy standpoint, this is the simpler posture: the building owner or resident is the data controller, and there is no external processor holding a copy.
Cloud storage introduces a third party into the data chain. Footage is transmitted to and stored by the provider. That provider may be subject to legal compulsion—a subpoena, a law enforcement request, or a data access demand—that the building owner never sees and cannot contest. With local storage, police must request footage from the homeowner or building owner, not from the manufacturer. That changes the legal posture materially.
There is also a cybersecurity dimension. Cloud-stored recordings are held on internet-connected servers; while reputable providers encrypt and restrict access, cloud services represent a larger attack surface than a card that never leaves the premises. Consumer reports and security analyses have repeatedly noted that cloud-connected camera systems can be subject to hacking, even if the risk is statistically small.
3. Operational Resilience: What Happens When the Internet Fails?
A video intercom is a security device. Its value depends on whether it records when something happens—not when the network happens to be stable.
Local SD card recording continues during internet outages. If the connection drops during a storm or an ISP outage, a camera writing to a local card keeps recording and keeps the footage retrievable. Cloud-only systems, by contrast, may stop saving footage or make it inaccessible when the link is down.
Cloud storage has the inverse advantage after device theft or damage. If the outdoor station is stolen or physically destroyed, the footage already uploaded to the cloud remains accessible. Local footage on that device is lost. This is not a minor edge case in high-traffic or vandal-prone entrances.
The resilience question therefore depends on the threat model. Internet outages favor local storage. Device theft or destruction favors cloud storage. Buildings that face both risks are the strongest candidates for a hybrid approach.
4. Compliance and Retention: The Rule That Often Decides the Architecture
For multifamily buildings in jurisdictions governed by GDPR or similar data protection regimes, storage choice is not purely operational—it is a compliance decision.
GDPR’s storage limitation principle requires that personal data—including video footage from an intercom—not be kept longer than necessary for the documented purpose. The building owner, as data controller, must define the retention period and be able to demonstrate that footage is deleted when it is no longer needed.
Local storage makes retention control direct. The owner can set the SD card’s loop recording behavior, physically remove the card, or overwrite it. There is no dependency on a provider’s deletion schedule or account settings.
Cloud storage requires contractual and technical verification. The provider’s retention policy must match the building’s legal obligation. Some providers now offer granular retention controls—including the ability to disable audio retention entirely at the organization level while still allowing real-time audio for door communication—precisely to help multinational organizations comply with differing local statutes. But the owner must verify that the provider’s default retention does not exceed the building’s lawful retention period.
For buildings that must demonstrate compliance to a regulator or auditor, local storage is the simpler evidentiary path: the footage is on the device, the retention is controlled by the owner, and there is no external processor to audit.
The Hybrid Option: Both Paths, Not a Compromise
A growing number of systems support both local SD card recording and optional cloud backup. The local card captures continuous or event-triggered footage during normal operation; the cloud holds a copy that survives device theft or damage. The owner can configure the cloud plan for a shorter retention window (reducing cost) while relying on the local card for day-to-day review.
This is not a “best of both” marketing claim—it is a genuine architectural choice. The question becomes not “cloud or local?” but “which events need off-site survivability, and which can live on-device?”
Decision Framework: Matching Storage to Building Type
The right choice depends on the building’s risk profile and operational constraints, not on a universal preference.
| Building context | Recommended primary storage | Rationale |
|---|---|---|
| Single-family home or small villa | Local SD card | Low cost, no subscription, footage stays private; internet outage does not stop recording |
| Multifamily building with unreliable internet | Local SD card | Recording continuity is the priority; cloud dependency creates a security gap |
| High-traffic or vandal-prone entrance | Hybrid (local + cloud backup) | Local captures the event; cloud survives device theft or destruction |
| GDPR-regulated multifamily building | Local SD card (with documented retention) | Simplest compliance posture; owner controls deletion and access |
| Building managed remotely across multiple sites | Cloud or hybrid | Remote review and centralized retention visibility outweigh local-only simplicity |
| Budget-constrained retrofit | Local SD card | Eliminates recurring fees; SD card cost is minimal |
FARHD’s Position: Local SD Card as the Baseline, Cloud as the Option
FARHD’s 2-wire and IP intercom systems support local microSD card recording as the baseline storage path, with capacity commonly up to 128GB depending on model. This aligns with the procurement reality of many residential projects: the building owner wants recording capability without a recurring cloud fee, and the footage should remain on the property unless the owner chooses otherwise.
For projects where off-site survivability or remote multi-site review is a requirement, the specification conversation should address cloud backup as an optional layer rather than replacing the local recording path. The relevant question is not which storage method is “better” in isolation—it is which failure modes the building must survive, and which storage architecture matches that risk profile.
