Privacy Policy

Last updated 17 September 2026.

Seidr Labs is operated by a single engineer in South Africa. This page describes what the software published here accesses, and what it does not.

This website

Simply reading the public pages does not create an advertising profile: there are no advertising trackers and no third-party analytics profiles. Standard server logs may still record technical request data needed to operate and protect the site.

If you send a contact form, Seidr Labs stores the name you provide, your email address, the subject and message, a one-way hash derived from the network address, and your browser's user-agent string. The message details are used to answer the enquiry; the technical fields help prevent abuse. A notification containing the enquiry is also sent to the owner's private Telegram chat.

Seidr Beacon company accounts

When you create or sign in to a Beacon company account, Beacon stores your verified work email, company profile, short-lived verification challenges, expiring sign-in sessions and an audit trail of account actions. Verification codes expire after ten minutes. New company accounts include one active tracker; requests for additional paid tracker capacity are stored with the company account so Seidr Labs can respond. Tracker capacity is never unlocked merely by submitting a request.

Beacon's company-specific privacy notice separately explains the location, message, route and emergency data handled for enrolled phones, the company's working hours and its retention period.

Backup tooling and Google Drive

Seidr Labs runs internal backup tooling for its own systems. That tooling uses Google Drive as one destination among several, through the standard Google authorisation screen.

• It is authorised by the operator against the operator's own Google account. It is not offered to the public and has no other users.
• It requests the drive.file permission, which grants access only to the files the application itself creates. It cannot read, modify or delete the rest of a Google Drive.
• The files it creates are encrypted backup archives of Seidr Labs' own systems.
• No data from Google Drive is read for any other purpose, shared with anyone, sold, or used for advertising, profiling or training.

Retention and deletion

Website enquiry records are removed automatically after 12 months unless a different period is configured for a documented operational reason. Copies in pre-deployment backups and Telegram are not removed by that automated database purge and must age out or be removed separately. You can use the contact page to ask what is held about your enquiry or request deletion.

Backup archives are kept only as long as they are useful for recovery, and older copies are removed on a schedule. Authorisation can be withdrawn at any time from the operator's Google account security settings, which immediately ends the application's access.

Contact

Questions about this policy can be sent through the contact page.