Personal Information Collection List

1. About this list

This is a practical summary of information handled by the current Seculink App, provided by ALLSPEC SECURITY, INC. Read it with the Privacy Policy, which explains legal bases, disclosures, international processing and regional rights.

A category is handled when the relevant feature is used or a necessary background service operates. The presence of a category here does not mean every provider receives it. A permission declaration or an installed library is not, by itself, proof that a particular feature collects data.

2. Account and sign-in

Account identifier, account email and verification status, saved-account and active-session details, installation identifier, App/device metadata, session credentials and account-deletion request references and secure tracking credentials.

Why it is used

Sign-in, account switching, session security, authorized requests, account deletion and progress recovery.

Where it is handled

Phone secure storage and private account data; our backend and hosted identity infrastructure on AWS. The App does not receive the hosted sign-in password.

Retention

While needed for the account/session, deletion processing and tracking, and applicable security or legal purposes. Signing out removes the local session, not the whole account. Deletion tracking can remain available after sign-out.

Your controls

Review active sign-ins, revoke supported sessions, sign out, request deletion through Me → Delete Account, or track a saved deletion request.

3. Homes, members and sharing

Home names/IDs, roles, invitations, member details, email-based user lookup, allowed devices and access expiry.

Why it is used

Show and manage Homes, invitations and authorized shared access.

Where it is handled

Our backend, account-specific phone cache and authorized users according to permissions.

Retention

While needed for Home membership and service operation, subject to deletion and applicable legal retention. Cache lifetime is not a cloud-retention promise.

Your controls

Manage membership and device permissions where your role allows; request correction or deletion.

4. Connected-device information

Device identifiers and names, model/capability details, grouping, status, properties, commands, event metadata and times.

Why it is used

Bind, organize, display and control devices and retrieve supported events.

Where it is handled

Phone, our backend/AWS IoT infrastructure and the relevant device; Agora signaling where used for media control.

Retention

While needed for the device/service and relevant security or legal purposes. Device records and event-media files can have different lifetimes.

Your controls

Change supported settings, review sharing, clear downloaded business data or make a privacy request.

5. QR scanning and device binding

Camera frames or one selected photo for local recognition; a supported device identifier and binding credential for a confirmed binding request.

Why it is used

Recognize a device code and, only after confirmation, request adding the device to the selected Home.

Where it is handled

Recognition on your phone. The confirmed device identifier, credential and Home information go to our binding service. The scanning feature does not upload the frames or selected photo.

Retention

Recognition and credential information are transient in the App flow. The service retains the resulting device association and relevant security records according to its purposes.

Your controls

Use the system picker instead of the camera where supported; cancel before confirming binding; manage camera permission.

6. Live audio/video and two-way talk

Camera streams, supported camera audio, phone microphone audio during talk, media-session identifiers, routing and connection diagnostics.

Why it is used

Display live video, play camera sound and transmit your voice to the selected camera.

Where it is handled

Phone, camera and communication infrastructure including Agora, with our backend authorizing the session.

Retention

Media is handled for the communication session. Separately enabled local or cloud recording and provider diagnostic records have their own retention.

Your controls

Close live view, control sound, stop talk, and manage microphone permission.

7. Memory-card playback

Requested recording data, camera stream, file/time/index information and playback controls.

Why it is used

Find and play recordings available from supported camera memory cards.

Where it is handled

Camera/card, phone and the communication/signaling services needed for playback.

Retention

The source recording follows device/card recording and overwrite settings. Playback is distinct from retaining a new cloud recording.

Your controls

Select playback, stop it and manage storage through supported device controls. Clearing phone cache does not erase the card.

8. Cloud recordings and event images

Stored camera recordings, audio where included, event JPEG images and related device, time, duration, status and expiry information; temporary viewing credentials.

Why it is used

Browse and display authorized recordings and event images.

Where it is handled

Our cloud storage/delivery infrastructure and phone playback/image components; relevant infrastructure providers including AWS.

Retention

Content follows the applicable device/service retention and expiry. Temporary viewing-link expiry does not indicate content deletion.

Your controls

Control authorized access, stop viewing, and contact us about access or deletion of cloud content.

9. Local snapshots and recordings

Photos and supported MP4 recordings you capture from camera streams, related thumbnails and local file information. Camera audio may be included when sound is enabled.

Why it is used

Let you retain and view captures in the App album.

Where it is handled

Account-specific private storage on your phone. Local capture does not automatically upload a new cloud copy.

Retention

Until you delete the item or App data is removed. Signing out is not an instruction to delete local album files.

Your controls

View and delete local items. The current App does not support exporting album items to your phone’s Photos library or sharing them from the album.

10. Preview images and business cache

Historical frames saved as camera covers; temporarily decoded event images; downloaded Home, device and preference data.

Why it is used

Improve navigation, show previous camera images and reduce repeat loading.

Where it is handled

Account-specific phone cache or memory. Preview frames originate from streams already delivered to the App.

Retention

Preview-cover age limit: seven days, enforced when cleanup runs, with count/size limits. Other caches follow feature limits, invalidation and removal rules.

Your controls

Clear downloaded local business data and remove App data where needed. A preview is not proof of current camera status, and cache clearing does not delete source recordings.

11. Push notifications

FCM token on Android or APNs token on iOS, installation/platform information and notification content such as event or Home details.

Why it is used

Route device alerts, invitations and supported service messages to your phone.

Where it is handled

Our notification service and Google Firebase Cloud Messaging or Apple Push Notification service, as relevant to the platform.

Retention

While needed for delivery/registration and applicable provider or service purposes. Sign-out attempts to remove the current installation registration.

Your controls

Manage notification and lock-screen settings. Permission to show alerts and technical token processing are different parts of push delivery.

12. Optional System Logs and support reports

Reviewed technical events and diagnostic fields; report metadata such as App/build/OS/model and time coverage; any description you enter. The file sink is designed to exclude raw media and secrets.

Why it is used

Help troubleshoot service and device-communication issues.

Where it is handled

Local private log files; a report goes to your chosen recipient/provider only if you choose to send or share it. Support email records are separate.

Retention

Local files: approximately 50 MB combined cap; inactive files older than seven days are removed when cleanup runs. Temporary export files use separate cleanup limits. Sent reports follow recipient/support retention.

Your controls

Logging is off on a new installation. Enable/disable it, review export coverage, delete local logs, and choose whether to send, share or save a report.

13. Preferences, network and service records

Language, appearance and ordering preferences; IP address visible to services, connection/request times, status and proportionate security/error records.

Why it is used

Apply your settings, maintain connectivity, authorize access, diagnose failures and protect the Services.

Where it is handled

Phone, our services and relevant infrastructure/communication providers.

Retention

For as long as needed for the relevant preference, reliability, security and legal purposes. Local-cache freshness is not server retention.

Your controls

Change preferences, reset supported cloud preferences, clear local business data or exercise applicable privacy rights.

14. Permissions and features outside the current scope

The current App requests camera access for QR scanning, microphone access for talk, selected-photo access for QR recognition and notification permission for supported alerts. It needs network access for connected features.

Current user features do not request contacts, SMS, call logs or precise phone location. The App has no advertising SDK, named-face enrollment feature, AI-training donation program or in-App subscription checkout. This list does not authorize those uses if they are introduced later.

SDKs and operating systems can handle technical service data needed for their functions. Our provider summary describes the principal services; the production provider configuration and your feature use determine the relevant handling.

15. Questions, access and deletion

Request permanent account deletion in the App through Me → Delete Account, review the impact and verify your identity. Deletion covers your account across all apps sharing the same account pool. Your owned Homes are deleted, their devices unbound and other members lose access; other owners’ Homes only lose your membership. Accounts in other pools are unaffected. Once accepted, deletion cannot be cancelled or undone.

The App securely saves tracking information before signing you out. Acceptance means processing, not completion. Check progress through Saved deletion requests on the sign-in screen or in Me. Completion covers the account and associated service-data cleanup described in the Privacy Policy; retained records, backups and local copies have separate handling. Local album items, exports and camera memory-card files are separate, and store subscriptions and refunds must be managed separately. Subscription cancellation is not required before deletion.

If you used Apple or Google sign-in, optional connection-removal instructions are available in the App. You do not have to remove a connection first. Completion does not delete your Apple or Google account or confirm that its app connection was revoked.

Email tony@gsswest.ai for privacy enquiries, access/correction/deletion requests, tracking help or questions about retention. If you cannot use the App, use the subject “Seculink account deletion” and identify the account email or request reference. Do not send a password, token, deletion receipt token or device binding credential. Email starts a request for review and handling; it does not confirm completed deletion.