Beranda to.co
Mulai

Privacy

This website

Requests to this site are served from an edge network, which processes your IP address to deliver the page, to protect the service, and, when you have not chosen a language, to pick the version of the site for your country and language from the country it indicates or, failing that, your browser’s language setting.

Signing in with Google from this site

If you aren’t signed in, a few seconds after a page loads this site opens a small frame from my.to.co that offers to sign you in with your Google account (Google One Tap). The frame loads Google’s sign-in script, so Google can see that you visited, and if you are signed in to Google it shows your account. Nothing is shared with us unless you choose to continue; then Google shares your name, email address and Google account ID with us, as with Google sign-in on my.to.co. If you close the offer, Google stores a small cookie (g_state) on my.to.co so it isn’t shown again for a while.

Cookies

This site sets two strictly necessary cookies of its own, and analytics cookies only if you accept them. Change your choice at any time with Cookie settings at the foot of every page; rejecting analytics deletes its cookies.

CookiePurposeCategoryDuration
toco_localeRemembers the language you chose with the Language button at the foot of a page. Set only when you choose.Strictly necessary1 year
toco_consentRemembers whether you accepted or rejected analytics cookies, so we do not ask again.Strictly necessary1 year
_ga, _ga_R39R9TCMCQGoogle Analytics: tells one visit from another so we can count visits and see which pages are used.Analytics, only with your consent13 months

Analytics

If you accept analytics cookies, your browser loads Google Analytics from Google and sends it the pages you view, how you arrived, and your browser and device type. Google processes this for us to produce visit statistics. We do not use it for advertising, and we have turned off advertising features and Google signals. If you reject or ignore the banner, Google Analytics is not loaded and no request is sent to Google.

Business pages and visit counts

Pages on to.co addresses count views, and taps on their buttons, without cookies. Each count is added to a daily total for that page, together with the visitor's country, whether the device is a phone, tablet or computer, the name of the website they came from, and whether they came from a to.co QR code. We do not store IP addresses, set cookies or keep a record of any single visit, and nothing is saved on your device, so those pages show no cookie banner. Known crawlers and link previews are left out. The business sees the daily totals for its own page. Spotlight pages on to.co count views, and clicks on the business cards on them, the same way: a daily total for each page and each business, with the visitor's country and nothing else, sent by our own script without cookies. Each business sees the clicks its card received.

The app (my.to.co)

to.co runs its own sign-in. Signing in to my.to.co sets essential cookies from to.co only, sent only to my.to.co and never used for tracking or advertising: a session cookie that keeps you signed in for up to 30 days after you last use the app, a security cookie that protects your account from forged requests, and, when you sign in with Google or Xero, a cookie that lasts 10 minutes and ties that sign-in to your browser. We keep your email address and, for each signed-in browser, its type (for example, Firefox on macOS), its country, how you signed in and when, so you can review and end your sessions on the Sign-in and security page. We do not store IP addresses with sessions. Sign-in emails are sent through Resend. The sign-in page uses Cloudflare Turnstile to check for automated abuse, which processes details of your browser and network. When Google sign-in is available, the sign-in page loads Google's sign-in button, so Google can see that you visited it and, if you are signed in to Google, may offer to sign you in. If you close that offer, Google's sign-in script stores a small cookie (g_state) on my.to.co so the offer is not shown again for a while. If you continue with Google, Google shares your name, email address and Google account ID with us. If you sign in with Xero, Xero shares your name, email address and Xero user ID with us; signing in gives no access to your books. Billing is handled by Stripe; we do not store your card details. If you connect an AI assistant to the to.co MCP server, we keep a record of that connection: the app's name, what you allowed it to do, and when it was made and last used. You can disconnect it at any time on the Sign-in and security page; the record stays as a security record.

Identity checks

If you choose to verify that you run a business, Stripe, our identity partner, checks a photo of your driving license, passport or national ID card and a short live selfie. Stripe tells us whether the check passed, the first and last name and the date of birth on the document, and the document's type and issuing country. We do not receive the photos, the document number or your address. For a company registered in the UK, France, Germany, Norway, Czechia or New Zealand, we compare your name and date of birth with the people the official company register lists as running the company. Where the register shows only part of a date of birth, such as the month and year, we compare only that part; where it shows none, as in New Zealand, we compare the name alone. We use your date of birth for this comparison only and do not keep it. Otherwise, or when they do not match, a person at to.co reviews the check. Once a check is decided, we ask Stripe to delete the photos and data it holds for it. We keep the name, the result and a record of what was compared (the register we asked, the names and roles of the people it lists, and whether each name and date matched, never a date of birth) until your account is deleted. Verifying is optional; a page is published without it. If a check is not confirmed, you can start a new one.

Address checks

If you add a trading address to a business page, you can prove it by uploading a document such as a utility bill, a business bank statement, a lease or a UK driving license. Cloudflare, which hosts to.co, reads it for us with its Workers AI service: the type of document, who issued it, its date, and the name and address on it. We compare those with the address you gave. If that automated check can't decide, a person at to.co may look at the document. We delete the file as soon as there is a decision, whether the document is accepted or not. We keep what was read from it (the type, issuer, date, name and address) and the result, as a record of the check, until the address, the business or your account is deleted. Proving an address is optional, but a trading address is shown on a page only once it is verified.

Business records

Identity pages publish business facts, not personal profiles. The account that claimed a company can change its name, description, website, public email, phone numbers, menu, ordering and reservation links, category, search keywords and VAT number at any time, and the opening hours, phone numbers and social profiles of each trading address, and the page is published again with the change. Contact preferences are kept for to.co and not published. It can also upload a logo (PNG, JPEG, WebP or a script-free SVG) and a browser icon (PNG, JPEG, WebP or ICO), up to 2 MB each. These are public: we store them and serve them from media.to.co. Removing or replacing one takes it off the page, but the earlier file is not deleted and stays reachable at its old address.

Finding your business on Google Maps

When you add a business, my.to.co may ask whether it is on Google Maps. If you choose to search, our server sends Google (Google LLC, in the USA) the search text you type, usually the business's name and town, and then the id of the listing you pick. Your browser does not contact Google and no Google script loads in my.to.co, so Google does not receive your IP address from us. The listing fills in the form for you to check: its name and address for a business without a registration number, and its phone, category and opening hours as boxes you can untick. Only what you keep is saved, as your own entries, the same as if you had typed them. When the business is added, our server asks Google for the listing's address once more: if the address you kept is the listing's, unchanged, we record that it was confirmed by your Google Maps listing, and for a registered company whose listing is somewhere other than its registered office, we add the listing's address as a trading address. We keep the listing's Google id with the business's location until it is changed or the business is deleted. We do not keep the search or Google's answers. If you answer No, nothing is sent to Google. If you chose a listing and connecting Google Business Profile is available for the business, we email its owners about it an hour later.

Tax number checks

If a business saves a VAT number on its page, we check it with the tax authority: an EU number with the European Commission's VIES service, a UK number with HM Revenue & Customs (HMRC). We send them the number only. They tell us whether it is registered and, where they share it, the name and address registered for it. We compare that name with the business's name on to.co; when they differ only slightly, a Workers AI model on Cloudflare judges whether they name the same business. An EU or UK number appears on the page only when it is registered under a matching name, marked as verified with the date of the check. The registered name and address are shown only to the people who run the business, never on the page. A check of a new number replaces the old one, and it is deleted when the number is removed or the business is released.

Messages to a business

A business page can carry a form for sending the business a message. We store what you type in it (your name, an email address or phone number, and your message) and nothing else with it: not your IP address and not your browser. When you send, your IP address and country are used for Cloudflare's Turnstile check and our rate limits, and are not kept with the message. Cloudflare, which hosts to.co, reads each message for us with its Workers AI service to judge whether it is spam and to write a one-line summary for the business. The message is shown in the business’s inbox at my.to.co. Through Resend, our email provider, the business is only emailed that a message has arrived, without your words or your contact details. If the business is on the Free plan, you first confirm your email address with a code or link we send you; that creates a to.co account for the address, as signing in by email would, without signing you in. The business can reply to you, can delete your message at any time, and may copy it to its own systems (see the next section). We delete a message 12 months after it arrives (24 months for a business on the Grow plan), or 30 days after it arrives if it is held as spam. We never write or send a reply for the business: any reply you get is the business's own words, and where it comes through to.co we only deliver it, unchanged.

API keys and webhooks for a business

A business on the Pro or Grow plan can give its own software an API key. A key reads the business's record, the messages sent to it and its posts, and on the Grow plan can change its services, phone numbers and opening hours, write posts, draft documents and work on supplier applications. A business on the Grow plan can also set up webhooks: when something happens, such as a new message or a change to its record, we send the details to an HTTPS address the business chose. A new-message webhook carries the sender's name, contact details and message. Once a message reaches the business's own systems, the business decides how it is kept and used; we do not control that. We keep a copy of each webhook event, and a log of each delivery (the time, the HTTP status and how long it took, never the reply), for 30 days, so the business can see what was sent and send it again; deleting a message deletes our copies of the events about it sooner. We store only a hash of each API key, and keep a count of API requests by key and day for 13 months to measure the business's monthly allowance.

People on an account

An account can have more than one person, each with their own sign-in and a role: Owner, Finance, Editor or Viewer. When an Owner invites you, we email you the invitation through Resend. While it waits (at most 7 days), we keep your email address with it, encrypted, so the account's Owners can see who was invited. Once it is accepted, declined, canceled or expires, we delete that copy and keep only a hash of the address (a scrambled form that lets us recognize the address again but does not show it), with the role offered and the dates, as the record of who was given access. Once you join, the account's Owners can see your name, email address, role, the companies you work on and whether you have a passkey, and every Owner is emailed when someone is invited, joins, changes role, leaves or is removed. Anyone on the account can see, in a company's history, the email address of the person who made each change. Removing someone, or leaving, ends their access to the account at once; what they did stays in the history, and their own sign-in and other accounts are not affected. Invitation and access records are kept for up to 7 years and are deleted with the account. When you sign in without an account or a pending invitation, we create an account for you. You are its Owner. It stores your name, email address and country. We delete it after 90 days if you have not added a business, invited another member or started a subscription. Your sign-in remains active. You can give a job title and phone number in Your details. If a business you work on picks you as a contact on its trading profile (for sales, billing, purchasing or accounts payable), the people on its account who can change those contacts see your name, email address, job title and phone number, and so do the connected trading partners the business shows that contact to. These contacts show your current saved details. When you leave a business’s team, its trading partners can no longer see your contact in that business’s trading profile. People with permission to manage that profile can still see your details until the contact is deleted.

Website badges

A business can put an ABIZ status badge on its own website, linking to its to.co page. When you open a page that shows one, your browser loads the badge from mark.to.co and tells us the website it is on (the site's address, not the page). We use that only to choose which badge to draw. The badge uses no cookies, and we do not record who you are or which page you were on: we count only how many badges we draw and with which status. Cloudflare, which hosts to.co, handles the request as it does any web request. If a business asks us to send the badge code to its web developer, we email that person once through Resend, with the business's optional note, and keep only a hash of their address to limit how many such emails it receives.

Matching suppliers in a connected accounting system

When a business connects its accounting system, we compare its customers and suppliers with businesses on to.co, so it can confirm which are its trading partners. To match a supplier, we may read the invoices it has sent the business, using the access the business grants when it connects. We use automated tools, including AI, to find who issued an invoice, and keep only details printed on it. Neither we nor our AI provider use the invoices to train AI models. We do not store the invoices or what we read from them: only which business on to.co the supplier matched, and records of how each read went, kept for up to a year. An invoice can name people, such as a sole trader or a contact; their details are read in the same way and not kept. Nothing is matched as a trading partner until the business confirms it. The invoice files read for matching are not kept; copies of the records read from the system are described in the next section.

Copies kept from a connected accounting system

When a business connects its accounting system, we keep copies of some of what we read from it, so that its trading partners can see the documents it shares with them even when the system is slow or unavailable, and so that we can match its contacts to businesses on to.co without asking the system each time. We keep each contact's name and, encrypted, the details we use to match it (tax and company numbers, website, the domain of its email address, country, town and postcode), and, encrypted, the trading documents we read (invoices, bills, credit notes, quotes, orders, sales receipts and payments). We do not keep a contact's email address, phone number or bank details, or the accounting system's own PDFs. We keep each copy for 13 months after we last read it. When the business disconnects the system we delete every copy from it at once, and it can delete them in the app at any time without disconnecting. We keep these copies to provide the service the business asked for. A contact or a document can name people, such as a sole trader or a contact person; their details are kept and deleted in the same way. The accounting system stays the business's own record of its accounts.

Notices from Stripe and Resend

Stripe (payments and subscriptions) and Resend (the email we send) tell us by webhook when something happens, such as a payment, a subscription change or an email delivered or bounced. When their signature checks out, we keep what the notice said for 7 days, encrypted, so our staff can find out what went wrong. It can include a name, an email address and an amount. Only to.co staff can open it, each opening is recorded, and it is deleted after 7 days. We keep a record that the notice arrived, with its type and its ID but not its contents, for 90 days.

Companies that process data for us

When to.co processes personal data for a business, such as messages sent to it, data used through the API, MCP and webhooks, and what it publishes, a few companies help us do it. They are listed on our subprocessors page, with changes coming up and past changes. We normally give at least 30 days' notice before adding or replacing one; an urgent change is announced as soon as we can, with the reason. Our data processing agreement sets out how we handle that data for the business.

Bahasa

Pilih dari bahasa yang didukung penuh oleh situs dan aplikasi.