Privacy Policy

Onehub is operated by Kelin Studio Pte. Ltd., based in Singapore (“Onehub”, “we”, “us”). This policy explains what personal data we handle and why.

1. Two kinds of data

• Your account with us. If you sign up for Onehub or are invited to an organisation, we decide how your account data is used, and this policy applies in full.
• Data our customers collect. Businesses use Onehub to run forms, orders, bookings, tickets and invoices. If you gave your details to one of them, that business decides how your data is used and its privacy policy applies. We store and process the data only on its instructions. To see, correct or delete it, contact that business; we will help it respond.

2. Information we collect

• Account data: the email, name and avatar you provide, or that Google provides when you choose to sign in with Google (section 11).
• Organisation data: organisations, memberships, roles and the records you create.
• Technical data: IP address, browser and session details, used for security, rate limiting and the audit log.
• Form submissions: what a person types into a customer’s form, and, only if they accept optional cookies, how they arrived (for example a campaign link).
• Field app data: if you use the Onehub Field app, your location while a route is active, the photos, signatures and notes you record for a visit, and a notification token (section 13).

3. How we use information

To provide and secure the Service: signing you in, enforcing who may see what in an organisation, keeping an audit log of security events, sending the emails the Service needs, and preventing abuse. We do not sell personal data.

4. Connected advertising and accounting accounts

An organisation’s owner or admin can connect its accounts on Meta (Facebook and Instagram ads), Google Ads, Google Analytics, TikTok Ads, Xero or QuickBooks. The person connecting signs in on that platform and approves exactly what Onehub may access. For advertising accounts that is:

• the names, IDs, currency and time zone of the ad accounts or properties the person can reach, so they can pick the right one;
• campaign names and statuses, and daily performance figures: spend, impressions, reach, clicks, leads, purchases and purchase value;
• an access token, stored encrypted and only readable by our servers.

We use this only to show that organisation its own ad reports in Onehub and, when one of its admins asks, to create campaigns (always paused) or pause and resume them. Data from one organisation’s accounts is never shown to another organisation. We do not sell it, share it with other advertisers, or use it for our own advertising. We do not read the personal profile of the person who connects beyond what the platform needs to confirm the sign-in.

5. Cookies

We use strictly necessary cookies to keep you signed in. These cannot be switched off while you use the Service. Analytics runs without cookies until you accept optional cookies in the consent banner; rejecting keeps it that way. We set no advertising cookies.

6. Service providers

• Supabase: database, sign-in and file storage.
• Vercel and Cloudflare: hosting and network delivery.
• Stripe: card payments and subscriptions.
• Resend: transactional email.
• Upstash: rate limiting.
• PostHog and Google Analytics: product and website usage, as described in section 5.
• Google Maps Platform: address lookup and route planning.
• Cloudflare Turnstile: bot protection on sign-in forms, when enabled.
• Expo: push notifications and app updates for the Onehub Field app.
• Anthropic (Claude) and OpenAI: the AI features, as described in section 12.

Platforms an organisation chooses to connect (section 4) are not our providers: the organisation has its own account and agreement with each of them. These providers process data on our behalf and may store it outside Singapore. We require them to protect it to a standard comparable to the Personal Data Protection Act 2012.

7. Your rights

You can see and update your data, export a copy, and permanently delete your account at any time from your account settings. You may also ask us for access to or correction of your personal data, or withdraw consent, by writing to the address below. Depending on where you live, other rights may apply.

8. Retention and security

We keep data for as long as your account is active. Each organisation’s data is isolated at the database layer. When you delete your account, your personal data and any organisations you solely own are removed.

9. Deleting data from a connected account

To stop Onehub using a Meta, Google, TikTok, Xero or QuickBooks account and have the data it brought in deleted:

• In Onehub, an owner or admin opens Admin ▸ Integrations, picks the platform and disconnects the account. Onehub stops all access through it straight away and deletes the stored access token. Campaigns and results already brought in stay in the organisation’s reports until they are deleted.
• For an advertising account, the owner or admin can then choose Delete history on the disconnected account. This deletes the campaigns Onehub brought in from it and all their daily results straight away. Campaigns the organisation published from a Onehub media plan stay with that plan.
• On the platform itself you can also withdraw Onehub’s access at any time. For Meta, go to Facebook Settings › Business Integrations, select Onehub and remove it. For Google, go to myaccount.google.com/connections, select Onehub.world and remove its access.
• To have any other stored account details or data from a connected account deleted, email us at the address below from the organisation’s owner account, naming the organisation and the platform. We confirm by email and delete the data within 30 days.

10. Requests from public authorities

If a government body, regulator or law-enforcement agency asks us for personal data, including data from a connected account:

• We check that the request is lawful and properly made before answering it.
• We challenge or refuse requests we consider unlawful or too broad.
• We disclose only the minimum data needed to answer a lawful request.
• We keep a record of each request, our response, and the legal basis and people involved.

Where the law allows, we tell the organisation the data belongs to before we disclose it.

11. Information we receive from Google

Onehub (shown by Google as “Onehub.world”) uses Google in two separate ways. What we receive depends on which one you use, and Google shows you the exact permissions before you agree.

Signing in with Google.If you choose “Continue with Google”, Google gives us your name, email address, profile picture and a permanent ID for your Google account. We use them only to create your Onehub account and sign you in, to show your name and picture to the people in your organisation, and to keep your account email correct if Google tells us your address has changed. We never receive your Google password, and this sign-in gives us no access to your Gmail, Drive, calendar or contacts.

Connecting Google Ads or Google Analytics.An organisation’s owner or admin can connect these accounts (section 4). With that permission:

• Google Ads: we read the ad accounts the person can reach (name, ID, currency, time zone, and client accounts under a manager account), campaign names, IDs and statuses, and daily figures: cost, impressions, clicks, conversions and conversion value. When an admin of that organisation asks, we create a campaign and its budget (always paused), pause or enable a campaign, or remove one. We do not read or change ads, keywords, billing or payment details.
• Google Analytics (read-only): we read the list of accounts and properties so the person can pick one, and daily figures by campaign, source and medium: sessions, engaged sessions, key events and revenue. We cannot change anything in Google Analytics.

How we use it. Only to provide these features to that organisation: its own reports inside Onehub and the campaign actions its admins take. We do not sell information received from Google, do not use it for advertising of any kind (including retargeting or personalised ads), and do not use it to develop or train generalised artificial-intelligence or machine-learning models. We do not pass it to anyone else, except to the service providers in section 6 that host Onehub for us, when the law requires it (section 10), or as part of a merger or sale of our business, with notice to you. No person at Onehub reads it unless the organisation asks us for help, it is needed to investigate abuse or a security problem, or the law requires it.

How we store and protect it.Google access tokens are stored encrypted and can be read only by our servers; they are never shown again, not even to the organisation’s admins. Reports are kept in that organisation’s own isolated part of the database and are sent over encrypted connections.

Keeping and deleting it. We keep it for as long as the account stays connected and the organisation keeps its reports. Disconnecting deletes the access token straight away, and the steps for deleting what was brought in are in section 9. Sign-in details from Google are deleted when you delete your Onehub account (section 7).

Onehub’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

12. AI features

Some parts of Onehub use AI from Anthropic (Claude) or OpenAI:

• Cubby, the AI agent, on its own page and in the side panel beside other pages, which answers a member’s questions about the organisation’s records and drafts changes for the member to approve;
• the setup agent, which asks a new organisation’s owner about the business and suggests how to set Onehub up for it.

When these features are used, we send the provider what it needs to answer: the member’s questions, the member’s name and role, the organisation’s name and settings, the records the agent looks up for that member, the answers given to the setup agent, and the public text of a website the owner asks the setup agent to read. The agent can only look up what the member could already see in Onehub. We use what comes back only to answer that member. Chats are kept in the organisation’s own part of the database.

We use both providers through their APIs for businesses, not their consumer chat apps. Under each provider’s API terms, what we send is not used to train their models and is kept only for a limited period, for example to monitor for abuse.

An owner or admin can switch the AI features off for the whole organisation in Admin ▸ Modules. Nothing is then sent to either provider for that organisation.

Connecting ChatGPT or Claude. If an organisation switches it on in Admin ▸ Integrations, its owners and admins can connect their own ChatGPT (OpenAI) or Claude (Anthropic) account to Onehub. That app then asks Onehub for records on the member’s behalf, and we send it only what that member could see in Onehub, in the one organisation they chose when connecting; with their permission it can also make changes, which are recorded as the member’s. Unlike the features above, this goes to the member’s own account with that provider, under the member’s (or their employer’s) agreement with OpenAI or Anthropic and that account’s settings on how chats are used and kept. We do not receive the member’s chats. We keep a log of each request the app makes (which tool, what it asked for, when, and the outcome), which the organisation’s admins can see. A member can remove their own connection in Settings ▸ Sign-in & security, and an admin any connection, or switch the feature off, in Admin ▸ Integrations.

13. The Onehub Field app

Onehub Field is the mobile app for installers and drivers. You can use it only if an organisation gives you the Installer role; it has no sign-up of its own. Your organisation decides why this data is collected, and we process it on its instructions (section 1).

• Location.While a route assigned to you is active, the app sends your phone’s precise location to your organisation about once a minute, also when the app is in the background or the phone is locked. It stops when the route ends and collects no location when no route is active. Your organisation uses it to see progress, plan the day and check that a visit was recorded at the customer’s address. While you are on the way to a customer, that customer’s tracking page shows your name as your organisation recorded it, the vehicle’s plate and its position on a map. Positions are deleted after 30 days.
• Camera and photos. With your permission, used only for the photos you attach to a visit as proof of delivery.
• Visit records.The customer’s signature, the payment you record as collected (amount and method, never card details), notes and the reason a visit could not be completed.
• Notifications. A push notification token, so your organisation can tell you about route changes.

The app has no advertising and no third-party analytics, and we do not use this data to track you across other apps or websites. You can turn location, camera and photo access off at any time in your phone’s settings; the app then asks again when it needs them.

14. Changes and contact

We may update this policy and will tell you about material changes through the Service. Questions or requests: Kelin Studio Pte. Ltd., mike.xu@kelin.studio.