隐私说明
最后更新:2026 年 10 月 29 日 · ToBe 是一个学生做的个人项目,还在测试阶段
一句话
ToBe 只存让它能用的最少数据;开发者看不出谁在用、也不知道哪份数据是谁的;你随时能导出或删掉自己的全部数据;用 AI 功能前会先问你一次。
谁在管你的数据、怎么联系
ToBe(z1le.com)由 Zile Fan 个人开发和运营 —— 一位在英国读书的学生,不是公司,也不是任何学校的官方服务。按英国 GDPR,他是你数据的「数据控制者」。 有任何隐私问题、想行使下面写的权利:发邮件到 hello@z1le.com(不用有账号),或者登录后点右上角你的头像 →「反馈」。
我们存什么
- 登录用的邮箱指纹:你的邮箱经过一道带密钥的单向加密(HMAC),存的是一串还原不回去的字符,不存邮箱原文。注册时也不会把你的邮箱交给开发者。
- 密码:如果你设了密码,存的是加盐的 PBKDF2 哈希(10 万轮),不存原文。
- 你在各个应用里自己填的东西:人生树(目标、待办、习惯)、习惯打卡、专注记录、在 ToBe 里建的日程、「提高」里的成绩、思维导图、每日总结、饮食和健身、新生网站上的勾选和分数、应用商店里加了哪些应用。挂在一个随机编号下面,编号和你的邮箱之间没有可以查的对应关系。人生树会留历史版本,方便你恢复。
- 和 AI 的对话:「成为」里你写的话和 AI 的回答,存在你的账号里。导出数据时一起带上,删除账号时一起删掉;每一轮对话也都能单独删。
- 财务:银行对账单 PDF 只在你自己的设备上读,文件本身不上传;读出来的交易列表、分类和预算会存进你的账号,方便换设备也能看。
- 学校邮件转发(只有你自己设置了转发才有):每个人有一个专属收信地址,你把学校邮件转发过来,ToBe 从里面找截止日期、活动、改教室。每封存寄件人、标题、正文(最多 8000 字)和附件的文件名(附件本身不存),只留最近 150 封。这些邮件里可能有老师、同学的名字和邮箱 —— 只给你自己看,不拿去做别的。网页上能删,删除账号时一起删。
- 反馈:在 ToBe 里发的反馈是挂在你账号下的一段对话(文字、图片、录音都可以),这样开发者才能回复你。开发者看到的是「User 3」这样的编号,看不到你的邮箱;你选了「公开」才看得到你自己填的称呼。删除账号时一起删。
- 新生网站的反馈(不登录也能发):存你写的内容、时间、在哪一段、选的专业和语言;你留了联系方式才有联系方式。为了防刷,会把你的 IP 地址算成一个还原不回去的指纹,只用来限制一小时内能发几次,一小时后自动删掉。最多留最近 500 条。
- 新生网站的教授 / 编辑名单(z1le.com/handover,只有被加进去的人才有):存邮箱原文、可以不填的名字、能改哪个专业哪几年、谁什么时候加的;还有每次保存内容的记录(谁、什么时候、改了哪些块)和还没批的改动。谁看得到:站长看全部;那个专业的教授看本专业的;编辑只看自己的。名字填了的话会公开显示在新生页「这个专业由谁维护」里,邮箱从不公开。加进去时会给那个邮箱发一封说明权限的邮件。删了就没了:教授 / 站长把人删掉,名单上的邮箱立刻删除、权限立刻失效(改动记录里的那几行最多留最近 500 条,会被新的挤掉;想马上抹掉就发邮件给我们)。
- 私信:你和朋友之间的消息存在服务器上,只有对话的两个人能在 ToBe 里看到。对方只看得到你填的称呼,看不到你的邮箱或账号;好友码随时能换。删除账号时你的好友码作废,你的消息列表一起删掉(对方那边已经收到的消息还在他那里)。
- 网页报错:网页出错时,浏览器会把错误信息、出错的位置、ToBe 版本号、浏览器标识(User-Agent,安卓手机的里面可能带机型)、屏幕尺寸发回来,用来修 bug。不挂账号,看不出是谁;只留最近 100 条。设置里选「什么都不给」就连这个也不发。
- 你自愿告诉我的使用情况:设置 → 账号里「告诉我你用了哪些功能」有三档 —— 什么都不给 / 只给使用情况 / 公开(还没选的时候,只有上面那种匿名的网页报错会发回来)。选了「只给使用情况」,会记:每个应用打开了几次、用了几天;新人指引走到第几步;网页报错有几个;用的是手机、平板还是电脑;还有两个「有 / 没有」:从你选这一档的那天算起,第 7 天、第 14 天有没有打开过(只记这两天有没有,不记别的日期;为了算这两天,会存你选这一档的那一天),只用来汇总出「多少人还在用」。只有次数,没有内容 —— 不记你在应用里写了什么、点了什么,也不记你的位置。开发者只看全部人加起来的汇总,不知道哪份是谁的。随时能改成「什么都不给」,改了就把已经记的删掉。
- 你自愿公开的信息:只有你在 设置 → 账号 里选了「公开」、自己填了称呼或联系方式,才会存这两样;开发者也能看到你自己的使用情况,出了问题能直接找你。随时能改回「只给使用情况」或「什么都不给」,改了就删。
我们不做什么
- 不做广告、不做追踪、不卖数据;除了下面「用到的服务」里写的,不和任何人分享你的数据。
- 不用第三方统计工具。
谁能看到
开发者在后台能看到:一共有多少人在用、每个应用有多少人用过这类数字;选了「只给使用情况」的人加起来的汇总;自愿公开的人的称呼和他们自己的使用情况;发给他的反馈(只看到编号)和新生网站的反馈;匿名的网页报错。 实话实说:网站的主人技术上能打开数据库里的匿名数据(比如某个编号下的成绩),但看不出它属于谁 —— 除非你在里面写了能认出自己的内容,或者你选择了公开。我们不会这样去翻。
演示的分享链接:你把演示的分享链接发给谁,谁就能不登录看(只读)—— 能看到页面、照片和你的称呼,看不到成员名单和邮箱。新开的分享链接才这样;旧链接仍要登录。想收回就在分享窗里重新生成,旧链接立刻作废。
为什么可以处理这些数据(法律依据)
- 为了给你提供 ToBe(履行合同):账号、你在应用里填的东西、反馈对话、私信。
- 你的同意:「成为」里把对话发给 AI、使用情况统计、公开身份、连接谷歌日历 / TickTick / 别的日历 / Claude、学校邮件转发。随时能在设置里撤回;撤回不影响之前已经做过的处理。
- 正当利益(让网站安全、能修 bug):匿名的网页报错、防刷用的 IP 指纹。
存多久
- 账号和里面的全部数据:存到你删除账号为止;删除是立刻删光,没有等待期。现在不会因为你很久不用就自动删。
- 登录 cookie:60 天;邮箱验证码:10 分钟。
- 网页报错:最近 100 条;新生网站反馈:最近 500 条;防刷的 IP 指纹:1 小时;学校邮件:最近 150 封;Claude 做过的改动记录:30 天。
- 「文件」(网盘)里你传的文件:存在 Cloudflare R2,存到你自己彻底删掉(删除后先在回收站放 30 天)或者删除账号为止;每人最多 300 MB(和下面「提高」的文件一起算),只有你自己看得到。
- 「提高 → 作业」里你传的文件(brief、往届范例、自己的图纸照片):存到你自己删掉那个文件、那份作业,或者删除账号为止;每人最多 300 MB,只有你自己看得到。
- 数据存在 Cloudflare;另外每天自动备份一份到开发者自己的电脑上(防止 Cloudflare 出问题时数据全丢),只有开发者能接触,最多保留 30 天 —— 你删掉的东西、或者删除账号以后,备份里的那份最晚 30 天后也会消失。登录会话和验证码不备份。
Cookie
只有一个登录必需的 cookie(tobe_s,60 天),用来记住你登录了。它是网站能用所必需的,所以不用另外征求同意,也不弹 cookie 框;没有别的 cookie。
另外浏览器本地会记一些界面偏好(语言、上次打开的页面之类),不会发给服务器。
用到的服务
- Cloudflare:网站托管、数据存储,也负责收你转发来的学校邮件。
- AI 模型:用在「成为」和「演示」的「AI 归章节」两处。「AI 归章节」:只在你点那个按钮时,把那份演示中转站里还没放进页面的照片小图(长边 256 像素)和每页的标题、正文、备注发给 Cloudflare Workers AI,让它建议每张放哪一页;不存、不用来训练,回来的只是建议,你勾了才挪。「成为」:发什么:只有那段对话里你打的字、你人生树上节点的标题(不含备注)、今天的日期和语言;不发邮箱、日历、财务、录音。发给谁:Cloudflare Workers AI —— 模型跑在 Cloudflare 自己的服务器上,和托管网站是同一家。什么时候发:只在你第一次打开「成为」并点了「同意」之后;设置 → 账号 → 数据与隐私 里随时能撤回,撤回后对话功能停用,已经存的对话还在,你自己删。开发者不看你的对话内容。
- Anthropic(Claude):只在你自己连了「连接 Claude」之后,见下面那一段。
- Resend(或 Cloudflare 自己的发信服务):发邮箱验证码 —— 用邮箱注册、用验证码登录时,把验证码发到你填的邮箱。
- Google:你选「用谷歌账号继续」时,用来确认你的邮箱,并拿你的谷歌头像显示在右上角(只存头像的网址)。如果你主动连接谷歌日历,我们会保存一个授权令牌,用来读取和修改你主日历里的日程(只在你打开 ToBe 时现拉,缓存 5 分钟),不碰别的谷歌数据;设置里随时能断开,断开时令牌会作废并删除。
- TickTick(滴答清单):只有你在 设置 → 账号 里主动连接时才用。我们存一个授权令牌,用来读取和修改你 TickTick 里的清单和待办;断开就删。
- 苹果 iCloud / 其他 CalDAV 日历 / 订阅链接:只有你在设置里主动连接时才用。我们存你填的账号和 App 专用密码(加密后才存)或订阅链接,用来读取和修改那个日历里的日程;断开就删。
- Open Food Facts:只在你在「饮食」里扫条码或输条码时,由你的浏览器直接把条码号发给 world.openfoodfacts.org 查营养成分,不发别的,也不经过我们。
- Open-Meteo:只在你往主页加了「天气」组件时,由你的浏览器直接把你输入的城市名 / 城市的经纬度发给它拿天气,不用你的设备定位,也不经过我们。
连接 Claude(MCP 连接器)
只有你自己在 claude.ai(或 Claude 的电脑版 / 手机版 / Claude Code)里添加 ToBe 这个连接器、登录 ToBe、并在 ToBe 的授权页上点了「允许」之后才会有。
- Claude 能读:你的人生树(中心主题、目标、项目、待办、习惯、清单,它们的标题、说明、截止日、优先级、做完没)、「成为」里定的那句愿景、习惯打卡的次数;你参与的「演示」的页目录(标题、正文、备注)和中转站里的照片小图(只在你让它整理中转站时)。
- Claude 能改(授权页上「允许修改」勾着才行):往树上加行动、把待办勾掉、给习惯打卡、把演示中转站里的照片挪进某一页的中转站(你能编辑的那些演示)。不能删除任何东西,也不能改已有的标题。Claude 做的每一次改动都记在你账号里(30 天),树也照常留历史版本。
- Claude 碰不到:你的邮箱、密码,你连的谷歌日历 / 别的日历里的日程,邮件、财务、饮食、健身、转录和录音、私信、账号设置。
- 交给谁:Claude 读到的内容会交给 Anthropic(做 Claude 的公司)处理,按 Anthropic 的隐私政策 和你在 Claude 那边的设置。ToBe 只在 Claude 来问的时候回答,不会自己主动发。
- 我们存什么:连了哪个应用、什么时候连的、最后用过、只读还是能改(设置 → 账号 → 数据与隐私 →「连接 Claude」里能看到);登录凭证只存一次性的指纹,不存原文;1 小时过期,60 天没用要重新登录。
- 断开:随时在 设置 → 账号 → 数据与隐私 →「连接 Claude」里点「断开」,立刻失效;删除账号也会一起断开。
谷歌用户数据怎么用(Limited Use)
ToBe 从谷歌 API 拿到的数据(你的邮箱、头像网址、谷歌日历里的日程),只用来在 ToBe 里给你本人显示和编辑你的日程: 不拿来做广告,不卖,不转给任何人,不用来训练任何 AI 模型;除非你自己要求(比如导出数据)、为了安全或法律要求,开发者也不会去看。 ToBe 对谷歌 API 数据的使用和转移,遵守 Google API Services User Data Policy(谷歌 API 服务用户数据政策),包括其中的 Limited Use(有限使用)要求。
你的权利
- 看 / 导出:设置 → 账号 → 数据与隐私 → 导出我的数据,得到一个包含你全部数据的文件。
- 改:你填的东西都能在 ToBe 里直接改。
- 删除:设置 → 账号 → 数据与隐私 → 删除账号,立刻删掉你的账号和全部数据,删了就回不来。
- 撤回同意:设置 → 账号 →「告诉我你用了哪些功能」改成「什么都不给」;AI 对话、各种连接也都在设置里撤回 / 断开。
- 自己做不到的、想问的、想反对某种处理:发邮件到 hello@z1le.com,一个月内回复你。
- 你也有权向英国信息专员办公室(ICO,ico.org.uk)投诉;不过希望你先告诉我们,让我们有机会改。
Privacy notice (English)
Last updated: 29 October 2026 · ToBe is a personal project made by a student and is still in testing
In one sentence
ToBe stores only the minimum it needs to work; the developer can’t tell who is using it or whose data is whose; you can export or delete all your data at any time; and ToBe asks you once before using any AI feature.
Who is responsible, and how to reach us
ToBe (z1le.com) is made and run by Zile Fan, an individual student in the UK — not a company and not an official service of any university. Under UK GDPR he is the “data controller” for your data. For any privacy question or to use the rights below, email hello@z1le.com (no account needed), or sign in and tap your profile picture in the top-right corner → “Feedback”.
What we store
- An email fingerprint for signing in: your email goes through a keyed one-way hash (HMAC); we store a string that can’t be turned back into your address, never the email itself. Signing up does not hand your email to the developer either.
- Password: if you set one, we store a salted PBKDF2 hash (100,000 rounds), never the password.
- What you enter in the apps: your life tree (goals, to-dos, habits), habit check-ins, focus sessions, events you create in ToBe, marks in Improve, mind maps, daily journal, food and fitness, ticks and marks on the Freshers site, and which apps you added. It sits under a random ID with no lookup back to your email. Your life tree keeps past versions so you can restore them.
- Your conversations with the AI: in Become, what you write and what the AI replies are saved in your account — included when you export, deleted with your account, and you can delete any single conversation.
- Finance: bank statement PDFs are read on your own device and never uploaded; the parsed transactions, categories and budgets are saved to your account so you can see them on any device.
- Forwarded university email (only if you set up forwarding yourself): everyone gets a private address; forward university emails to it and ToBe looks for deadlines, events and room changes. For each email we store the sender, subject, body (up to 8,000 characters) and attachment file names (not the attachments themselves), keeping only the latest 150. These emails may contain names and addresses of staff or classmates — they are shown only to you and used for nothing else. You can delete them on the page, and they go when you delete your account.
- Feedback: feedback sent inside ToBe is a conversation attached to your account (text, pictures or voice), so the developer can reply. He sees a number like “User 3”, not your email; he only sees a name if you chose “Public” and typed one. Deleted with your account.
- Freshers site feedback (can be sent without signing in): we store what you wrote, the time, which section, the subject you picked and the language; a contact only if you leave one. To stop spam, your IP address is turned into a one-way fingerprint used only to limit how many you can send in an hour, and deleted automatically after an hour. We keep the latest 500.
- Freshers site lead academics and editors (z1le.com/handover — only people who have been added): we store the email address itself, an optional name, which course and years they can edit, and who added them and when; plus a log of each content save (who, when, which blocks changed) and changes waiting for approval. Who can see it: the site owner sees everything; a course’s lead academic sees that course; editors see only their own entry. A name, if given, is shown publicly on the freshers’ pages under who keeps that course up to date; email addresses are never shown publicly. When someone is added, that address gets one email explaining the access. Removing deletes it: when a lead academic or the owner removes someone, their email is deleted from the list and their access ends immediately (edit-log lines keep only the latest 500 and roll off; email us to have them erased sooner).
- Direct messages: messages between you and a friend are stored on the server and visible in ToBe only to the two of you. The other person sees only the name you set, never your email or account, and you can change your friend code any time. Deleting your account voids your friend code and deletes your message list (messages the other person already received stay with them).
- Page error reports: when a page breaks, your browser sends back the error message, where it happened, the ToBe version, your browser’s User-Agent (on Android this can include the phone model) and screen size, so bugs can be fixed. Not linked to your account and can’t show who you are; only the latest 100 are kept. Choose “Nothing” in Settings and even these aren’t sent.
- Usage you choose to share: Settings → Account → “Tell me which features you use” has three levels — Nothing / Usage only / Public (until you choose, only the anonymous error reports above are sent). “Usage only” records how many times each app was opened and on how many days, how far the new-user guide got, how many page errors happened, phone / tablet / computer, and two yes / no flags: counting from the day you chose this level, whether you opened ToBe on day 7 and on day 14 (only those two days, no other dates — to work this out we keep the day you chose this level), used only to total up “how many people are still using it”. Counts only, never content — not what you write or tap, and not your location. The developer sees only totals across everyone, not whose is whose. Switch to “Nothing” any time and what was recorded is deleted.
- What you choose to make public: only if you choose “Public” in Settings → Account and type a name or contact yourself do we store those two things; the developer can then also see your own usage and reach you if something goes wrong. Switch back any time and they are deleted.
What we never do
- No advertising, no tracking, no selling data, and no sharing it with anyone beyond the services listed below.
- No third-party analytics.
Who can see what
In the back office the developer can see: how many people use ToBe and how many have used each app; combined totals from people who chose “Usage only”; the name and own usage of anyone who chose to go public; feedback sent to him (shown by number) and Freshers site feedback; and anonymous page error reports. To be honest: the site owner can technically open anonymous data in the database (for example the marks under some ID), but can’t tell whose it is — unless you wrote something that identifies you in it, or you chose to go public. We don’t go digging like that.
Presentation share links: anyone you send a presentation’s share link to can view it without signing in (read-only) — they see the pages, photos and your display name, but not the member list or anyone’s email. This applies only to share links created from now on; older links still need sign-in. To take a link back, make a new one in the Share window and the old one stops working at once.
Why we’re allowed to process it (lawful basis)
- To provide ToBe to you (contract): your account, what you enter in the apps, feedback conversations and direct messages.
- Your consent: sending Become conversations to the AI, usage statistics, going public, connecting Google Calendar / TickTick / other calendars / Claude, and university email forwarding. You can withdraw in Settings at any time; this doesn’t affect processing already done.
- Legitimate interests (keeping the site secure and fixing bugs): anonymous page error reports and the anti-spam IP fingerprint.
How long we keep it
- Your account and everything in it: until you delete your account; deletion is immediate, with no waiting period. Accounts are not currently deleted automatically for being unused.
- Sign-in cookie: 60 days; email codes: 10 minutes.
- Page error reports: latest 100; Freshers site feedback: latest 500; anti-spam IP fingerprint: 1 hour; forwarded university email: latest 150; log of changes made by Claude: 30 days.
- Files you upload to Files (your file space): stored on Cloudflare R2 until you delete them for good (deleted files wait in the bin for 30 days first) or delete your account; up to 300 MB each (shared with the Improve files below), visible only to you.
- Files you upload in Improve → Assignments (briefs, past examples, photos of your own drawings): kept until you delete that file or assignment, or your account; up to 300 MB per person, visible only to you.
- Data is stored with Cloudflare. A daily backup is also copied automatically to the developer’s own computer (so nothing is lost if Cloudflare has a problem); only the developer can access it and it is kept for at most 30 days — anything you delete, or your whole account once deleted, is gone from the backup within 30 days. Sign-in sessions and codes are not backed up.
Cookies
There is one cookie, needed to sign in (tobe_s, 60 days), which remembers that you are signed in. It is strictly necessary for the site to work, so it doesn’t need separate consent and there’s no cookie banner; there are no other cookies.
Your browser also keeps some interface preferences locally (language, the last page you opened and so on); these are not sent to the server.
Services we use
- Cloudflare: hosting and data storage; it also receives the university emails you forward.
- AI model: used in Become and in the presentation “AI sort into sections” button. AI sort: only when you click it, the small thumbnails (256 px on the long side) of that presentation’s inbox photos not yet on a page, plus each page’s title, text and notes, are sent to Cloudflare Workers AI to suggest a page for each; nothing is stored or used for training, and nothing moves until you tick it. Become: What is sent: only what you type in that conversation, the titles of the nodes on your life tree (not their notes), today’s date and your language — never your email, calendar, finances or recordings. To whom: Cloudflare Workers AI — the model runs on Cloudflare’s own servers, the same company that hosts ToBe. When: only after you tap “Agree” the first time you open Become; withdraw any time in Settings → Account → Your data & privacy (the chat then stops working; saved conversations stay until you delete them). The developer does not read your conversations.
- Anthropic (Claude): only if you connect Claude yourself — see below.
- Resend (or Cloudflare’s own email service): sends email codes — when you sign up with email or sign in with a code — to the address you typed.
- Google: when you choose “Continue with Google”, to confirm your email and show your Google profile photo in the corner (we keep only the photo’s URL). If you choose to connect Google Calendar, we keep an access token to read and edit events in your primary calendar (fetched only when you open ToBe, cached for 5 minutes); no other Google data is touched; disconnect any time in Settings and the token is revoked and deleted.
- TickTick: only if you connect it yourself in Settings → Account. We keep an access token to read and edit your TickTick lists and to-dos; disconnecting deletes it.
- Apple iCloud / other CalDAV calendars / subscription links: only if you connect them in Settings. We keep the account name and app-specific password (encrypted) or the link, only to read and edit that calendar; disconnecting deletes them.
- Open Food Facts: only when you scan or type a barcode in Food — your browser sends the barcode number straight to world.openfoodfacts.org to look up nutrition; nothing else is sent, and it doesn’t go through us.
- Open-Meteo: only if you add a weather widget to Home — your browser sends it the city you typed (or that city’s coordinates) to get the weather; no device location, and it doesn’t go through us.
Connecting Claude (MCP connector)
Only if you add the ToBe connector in Claude (claude.ai, the desktop or mobile app, or Claude Code), sign in to ToBe and press Allow on ToBe’s consent page.
- Claude can read: your life tree (centre, goals, projects, to-dos, habits and lists, with their titles, notes, due dates, priority and whether they are done), the vision sentence from Become, your habit check-in counts, and — only when you ask it to sort an inbox — the page outline (titles, text, notes) and inbox photo thumbnails of presentations you are in.
- Claude can change (only if “Let it make changes” was ticked): add actions to your tree, tick off to-dos, check in to habits, and move presentation inbox photos into a page’s inbox (presentations you can edit). It can never delete anything or rename what is there. Every change it makes is logged in your account for 30 days, and your tree keeps its version history.
- Claude can’t reach: your email or password, events in your connected Google or other calendars, email, finance, food, fitness, transcripts and recordings, messages or account settings.
- Who processes it: what Claude reads is processed by Anthropic (the company behind Claude) under the Anthropic Privacy Policy and your Claude settings. ToBe only answers when Claude asks; it never sends anything on its own.
- What we store: which app is connected, when, when it was last used and whether it can make changes (see Settings → Account → Your data & privacy → Connect Claude); sign-in tokens only as one-way fingerprints, expiring after an hour, with a new sign-in needed after 60 days unused.
- Disconnecting: any time in Settings → Account → Your data & privacy → Connect Claude → Disconnect; it stops working immediately. Deleting your account disconnects it too.
Google user data (Limited Use)
Data ToBe receives from Google APIs (your email address, profile photo URL and Google Calendar events) is used only to show and edit your own schedule inside ToBe, for you. It is not used for advertising, not sold, not transferred to anyone else, and not used to train any AI model; the developer does not read it unless you ask (for example, a data export), or for security or legal reasons. ToBe’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Your rights
- See / export: Settings → Account → Your data & privacy → Export my data gives you one file with all your data.
- Correct: everything you entered can be edited directly in ToBe.
- Delete: Settings → Account → Your data & privacy → Delete my account deletes your account and all its data straight away. It can’t be undone.
- Withdraw consent: set “Tell me which features you use” to “Nothing” in Settings → Account; the AI chat and every connection can also be withdrawn or disconnected in Settings.
- Anything you can’t do yourself, questions, or objecting to some processing: email hello@z1le.com — we reply within one month.
- You also have the right to complain to the UK Information Commissioner’s Office (ICO, ico.org.uk); we’d appreciate the chance to put things right first.