Good questions. Clear answers.

No. New accounts use email and password. Legacy internal usernames remain for compatibility, but you do not need to remember one.

Supported sources include RTSP and supported HTTP MJPEG, MP4 and playlist inputs, plus documented supported transports. Exact codec, authentication and device behaviour matter. Run a decoded-video test for your exact model. We do not promise every camera or proprietary phone app.

No. Discovery, profile resolution and video decoding are separate checks. Verify the exact device/firmware and stream. CamBackup does not claim ONVIF product certification.

Yes, a compatible local feed can use the outbound LAN gateway on supported Linux ARM64 or AMD64 hardware. Camera credentials remain on the local gateway.

No. It currently has no offline recorder or spool and cannot backfill frames never received by the cloud. Use a separately tested local recorder if offline continuity is essential.

Not automatically. There is an integration framework, but each proprietary app/device needs a model-specific adapter, permission and real hardware validation.

There is no promised permanent free cloud recording plan. Any explicitly configured account trial is temporary and recording entitlement is checked by the server. Proposed paid rates are shown on Pricing; checkout is not advertised as available until activated.

Power and Business. An account needs at least one active confirmed subscription on one of those tiers. Staff roles, account trials and similarly named legacy plans do not grant developer access. Normal interactive app use remains available on other plans.

Power and Business on the exact camera being shared. A higher-tier plan on another camera does not make every camera eligible for public sharing.

New developer-token requests, MCP and automation triggers fail when the account no longer qualifies. Public playback checks the exact camera’s eligibility. You can still list/revoke credentials, disable shares and view owned saved footage under its normal retention rules.

They are proposed launch prices until the payment catalogue is activated. The app only activates a paid mapping after canonical provider confirmation. A pending or failed payment is not an active plan. Contact us to confirm availability before relying on a purchase.

No. Retention is a ceiling and storage/output limits also apply. Actual scene bitrate, audio and saved media affect capacity. Check the plan allowance and observed usage together.

Yes, fixed opaque source-area masks apply before new cloud acquisition output is stored or distributed. Stop acquisition before editing and verify fresh output. Old footage and local gateway source previews are not retroactively masked.

Yes, capture-policy audio controls apply to new output within the source/plan capability. Muting the browser player does not remove a stored audio track; verify a new exported file.

No. Optional automatic analysis samples bounded owned recorded segments. It can miss people and is not continuous identity verification or proof of intent. Human review and appropriate privacy decisions remain necessary.

Yes, eligible accounts can use an expiring camera-scoped key or a suitably scoped personal token. Stable external IDs prevent duplicate retries. Duration 0 creates a bookmark; 1–3600 requests future capture, not pre-roll.

No. Camera availability, entitlement and worker completion still matter. Check confirmed segments and the resulting timeline. An existing recording window is not extended by a trigger.

Public widgets intentionally allow anyone holding the active share link to watch without signing in. Viewers can copy it. Never embed account credentials. Disable or rotate the share to stop future access through the old link.

Yes. Authorised media is served through CamBackup endpoints, including byte ranges. Never publish a private playback capability just because its domain is CamBackup.

Yes. When enrolled, the account must pass its second factor after those primary sign-in methods too. Password reset does not disable MFA. Save recovery codes independently.

Not currently. Use a client with private Bearer headers or the documented stdio bridge. Google account login is not an MCP OAuth authorization server.

It provides an installable experience on supported browsers and optional push. It does not cache private footage for offline playback, and it does not record while disconnected.

No zero-loss guarantee is made. Durable jobs and worker recovery help resume eligible work, but interrupted source/network/power can leave gaps. Verify actual recovered segments.

Use the support guides or Contact page. Send the camera model, time/timezone, safe error text and steps tried. Never send passwords, OTPs, recovery codes, camera URLs with credentials, or private playback links in a public message.