Privacy Policy · Rerinku

This policy explains how Rerinku (“we”, “us”) collects, uses, keeps and shares your personal information when you use the Rerinku software, the Rerinku Cloud service and this website.

Rerinku is local-first: camera video, recordings, snapshots, camera usernames and passwords, AI detection results and the face library are stored only on the device where you run Rerinku. We do not collect, upload or analyse them. What follows is the information that actually passes through or is stored on our servers.

Operator: [TBD: full legal name and registered address] Contact: [email protected]

Scope

Rerinku software: Rerinku Onboard (the server you deploy yourself), the Rerinku Android app, the command-line tool and the device SDK.
Rerinku Cloud: accounts, Quick Connect (remote access), the push notification relay and subscriptions.
This website: rerinku.com and its pages.

What we collect

Account information

When you create a Rerinku Cloud account we collect:

Your email address, to sign you in, send verification and password reset emails, and send essential account notices.
Your password, stored only as a bcrypt hash that cannot be turned back into the password.
When you signed up.

When you sign in with Google or X, we receive only your account identifier on that platform and your verified email address, and use them to match you to your Rerinku account. We do not read your contacts, posts, followers or anything else. X requires the “read posts” and “read users” permissions to be requested alongside email access before it will return account details; we use only the identifier and the email address.

After you sign in, your browser keeps a sign-in token. Our server stores only a hash of it, and it expires after 7 days by default.

Quick Connect (remote access)

When you turn on Quick Connect in Onboard, we store:

the server’s name, when it was created, whether it is online and when it was last seen;
a connection log: connect, disconnect, claim, revoke and similar events with their times. Claim, revoke and relay-credential events also record the requesting IP address, for security auditing and troubleshooting.

During remote access:

Web requests from your browser reach our gateway over HTTPS. The gateway decrypts them and forwards them to your Onboard through an encrypted tunnel. This is technically necessary to forward them; apart from the access logs described under “Server logs” below, we do not store the content of these requests.
Live video is carried over WebRTC with end-to-end encryption (DTLS-SRTP). Even when it is relayed through our TURN servers, we cannot decrypt it.

Push notifications

When Onboard sends a notification to your phone through Rerinku Cloud, it hands us the notification text (for example “Person detected at the front door”) and your phone’s push token, which we forward to the Apple Push Notification service (APNs) or Firebase Cloud Messaging (FCM). We only forward them; we do not store notification text or push tokens.

Onboard installation reports

To see which versions are in use and spot problems early, Onboard reports to Rerinku Cloud every 10 minutes by default:

a random installation identifier and the software version;
the operating system, kernel version, CPU architecture and core count, memory size, whether it runs in a container, and the board model.

Reports do not include any camera, recording, user or network information. If the installation uses Quick Connect, the report is linked to that server. You can turn reporting off by setting CLOUD_REPORT=false in the Onboard configuration.

Subscriptions and payment

Paid subscriptions are handled by Stripe. Your card details go straight to Stripe; we never see or store your full card number. We store only your Stripe customer ID, plan, subscription status and renewal date, and read your invoices from Stripe when you open the billing page.

Server logs

For security and troubleshooting our servers keep access logs: IP address, time, request path and browser user agent. Logs are deleted after [TBD: 30] days. To prevent brute-force attacks we also count requests per IP address in memory over a one-minute window; these counts are never written to storage.

This website

This website uses no analytics, advertising or tracking cookies, and no third-party analytics service.
Your browser’s local storage keeps your light/dark theme choice. After you sign in to Rerinku Cloud, the sign-in token is kept in session storage and cleared when you close the tab.
Signing in with Google or X sets a strictly necessary cookie, valid for 10 minutes, that confirms the sign-in was started from your browser and prevents forgery.
Web fonts are loaded from Google Fonts, so your browser sends Google your IP address and other request information.

What we don’t collect

Camera video, recordings, snapshots or audio.
Camera usernames, passwords or network addresses.
AI detection events, the face library or face photos.
Usage analytics. The Rerinku software and Android app contain no analytics, crash-reporting or advertising SDKs.

Data kept on your devices

The software keeps the following on your own devices, and we cannot access it:

Onboard: the device list, camera credentials (encrypted), recordings, AI detection results, the face library and the audit log. If you configure remote storage (your own S3 or WebDAV), recordings are synced to the location you choose. When AI detection is on, Onboard downloads model files from Hugging Face or the mirror you select; those requests go directly from your device.
Android app: the addresses of paired Onboard servers, sign-in tokens and the push token.
Command-line tool and device SDK: run locally and send us no usage data.

Android app permissions

Network: connect to your Onboard and receive video.
Notifications: receive camera event alerts.
Camera: used only to scan Onboard’s pairing QR code. It stops as soon as the code is read, and no images are kept.
Keep awake, vibrate: keep the screen on while you watch video, and give haptic feedback.
Storage (Android 9 and earlier only): save snapshots you take.

How we use information

To provide and run the service: sign-in, remote access, push notifications and subscriptions.
To keep accounts secure: verify email addresses, reset passwords, and prevent abuse and attacks.
To improve the product: understand version and platform distribution, and diagnose faults.
To process payments and invoices.
To meet our legal obligations.

We do not sell your personal information to anyone, and we do not use it for advertising.

We share information only with the following providers, and only as far as needed to run the service:

Provider	Purpose	Information involved
Stripe	Subscription payments and invoices	Email address, payment details
Resend	Verification and password reset emails	Email address, email content
Google	Google sign-in, Android push (FCM), web fonts	Account identifier and email, notification text and push token, IP address
X	X sign-in	Account identifier and email
Apple	iOS push (APNs)	Notification text and push token
[TBD: hosting provider]	Hosting the Rerinku Cloud servers	The server-side information described above

We may also disclose information where the law requires it, where a court or authority lawfully requests it, or where necessary to protect the safety or property of us, our users or the public.

How long we keep it

Account information: for as long as the account exists.
Sign-in tokens: expire and are deleted after 7 days by default.
Verification and password reset links: valid for 30 minutes; the records are deleted within 24 hours.
Quick Connect servers and connection logs: for as long as the server exists; deleted when you disconnect or remove the server in Onboard.
Onboard installation reports: [TBD: 12 months] after the last report.
Subscription and payment records: as long as tax and accounting law requires.
Server access logs: [TBD: 30] days.

Your rights

You can:

Access and correct: view your account, servers and connection logs in the Rerinku Cloud console, and change your password and server names.
Delete your account: email [email protected]. Once we have verified it is you, we delete your account together with its servers and connection logs within [TBD: 15] business days.
Turn off installation reports: set CLOUD_REPORT=false in the Onboard configuration.
Withdraw authorisation: remove Rerinku’s access in your Google or X account settings.
Complain: if you think we have handled your personal information improperly, contact us, or complain to the data protection authority where you live.

Security

Passwords are stored as bcrypt hashes; sign-in tokens, verification links and other tokens are stored only as hashes.
All network traffic uses HTTPS or encrypted tunnels, and live video is end-to-end encrypted.
Only a small number of authorised administrators can access server data, and only for operations.

No system is perfectly secure. If a breach affects your personal information, we will notify you promptly as the law requires and take steps to remedy it.

International transfers

The Rerinku Cloud servers are located in [TBD: country or region]. The providers listed above may process your information in other countries, including the United States. We require them to protect it to a standard comparable to this policy.

Children

Rerinku Cloud is not intended for anyone under 16. If you are under 16, please do not create an account. If we learn we have collected a child’s personal information by mistake, we will delete it promptly.

Changes to this policy

We may update this policy and will show the new revision date on this page. For significant changes we will notify you by email or with a prominent notice in the service.

This policy is available in Chinese, English and Japanese. If the versions differ, the Chinese version prevails.

Contact us

For questions or requests about this policy, email [email protected].