你的数据在 Runnax 里怎样处理

这里写的是我们现在实际怎么做；做法有变化时会更新这一页。这一页是现状说明，不是隐私政策，也不能代替隐私政策。

我们保存什么

  • 账号：邮箱、显示名，以及你所在的组织和角色；通过合作方网站（例如 Auvolar）登录时，还保存合作方传来的用户编号（不含姓名）。
  • 项目：你上传的场地图、方案、照度要求、项目里的备注，以及每次计算的输入、结果和报告。
  • 灯具库：你上传的 IES 文件、型号资料，以及每次修改的版本。
  • 试用用量：每次计算占用、扣除和退回的记录，以及计算用时。
  • 操作记录（审计记录）：登录、查看、保存、计算、下载等操作，以及被拒绝的请求；其中可能包含当时的 IP 地址。

存在哪里、谁能看到

  • 数据存放在 AWS 美国西部区域；上传的文件存放在私有存储中，并加密保存。
  • 在你的组织里，能看到哪些项目取决于你的角色：普通成员只能看到自己建的项目；只读成员只能看到共享给他的项目；组织的所有者和管理员可以看到本组织的全部项目。其他组织看不到。
  • Runnax 的运维人员为了维护系统和处理你的支持请求，可能会访问这些数据。
  • 网页服务器会记录标准访问日志（IP 地址、时间、访问的页面和浏览器类型），用于安全和问题排查；这些日志每天轮换，保留约 14 天。

我们怎么使用

  • 照明计算在 Runnax 自己的服务器上完成，不会把你的文件交给第三方计算服务。
  • AI 功能目前没有开启，你的数据不会发送给任何 AI 服务。
  • 你的项目内容（场地图、方案、灯具文件和计算结果）不用于改进 Runnax 引擎，也不用于发布基准数据。
  • 登录邮件通过 AWS 的邮件服务发送。我们不收集支付信息。
  • 浏览器里保存登录状态、当前组织、界面主题偏好和登录前选择的页面语言；页面没有第三方统计或广告脚本。
  • 注册来源标记：从带营销链接参数（utm_source、utm_medium、utm_campaign、utm_content，各不超过 64 个字符）的链接第一次打开登录页时，浏览器里保存这几个参数 30 天；自助注册建立组织时，把它们记在该组织上和注册记录里，只用来统计各渠道的注册和使用情况。不保存联系人编号、来源网址或其他参数；通过合作方进入的组织不记录。
  • 自助注册建立的组织有试用额度（页面上显示）；通过合作方进入的组织按合作方的安排使用，不领取这份试用额度。
  • 我们用操作记录做安全和问题排查，也做内部的使用诊断和安全统计（例如各个步骤的使用和出错情况、被拒绝的访问次数）。这些统计只在 Runnax 内部使用，不交给第三方。

保存多久（四类分开说明）

  • 运行数据（项目、结果、报告、上传的文件、灯具库）：目前不会自动删除，页面上也还没有删除功能。报告 PDF 只在服务器内存里短暂缓存；资料包在你下载时现场生成，不另外保存。
  • 每日备份：数据库每天备份一次，每份备份保存 30 天后自动删除。
  • 发布回退备份：每次系统更新前，我们会在服务器上另存一份回退用的备份（含数据库）。这类备份目前没有自动清理。
  • 审计记录：上面说的操作记录（可能包含 IP 地址）另外保存，用途见“我们怎么使用”；只有 Runnax 运维人员能查看，页面上不向其他用户显示；目前没有自动删除。

有问题

  • 想了解我们保存了你的哪些数据，或者有其他数据方面的问题，请写信到 kyan@runnax.com。我们会说明能做什么、不能做什么。
  • 这个邮箱使用 Google Workspace，邮件经 Google 的服务收发和保存。

How Runnax handles your data

This page describes what we actually do today; we will update it if that changes. It is a description of current practice, not a privacy policy, and does not replace one.

What we keep

  • Account: your email address, display name, and the organizations and roles you belong to; when you sign in through a partner site (for example Auvolar), also the user identifier the partner sends us (not your name).
  • Projects: the site images you upload, your plans and lighting requirements, the notes in a project, and the input, result and report of every calculation.
  • Luminaire library: the IES files and model details you upload, including every revision.
  • Trial usage: records of each calculation held, counted and given back, and how long it ran.
  • Activity records (audit records): sign-ins, views, saves, calculations, downloads and refused requests; they may include the IP address used at the time.

Where it is and who can see it

  • Data is stored in AWS’s US West region; uploaded files are kept in private storage and encrypted.
  • Within your organization, which projects you can see depends on your role: members see only the projects they created; view-only members see only the projects shared with them; the organization’s owners and administrators can see all of its projects. Other organizations cannot see them.
  • Runnax operations staff may access the data to maintain the system and to handle your support requests.
  • The web server keeps standard access logs (IP address, time, page requested and browser type) for security and troubleshooting; these logs are rotated daily and kept for about 14 days.

How we use it

  • Lighting calculations run on Runnax’s own servers; your files are not handed to third-party calculation services.
  • AI features are currently off; your data is not sent to any AI service.
  • Your project content (site images, plans, luminaire files and calculation results) is not used to improve Runnax Engine or to publish benchmarks.
  • Sign-in emails are sent through AWS’s email service. We do not collect payment information.
  • Your browser stores your sign-in session, the current organization, your theme choice and the page language you picked before signing in; the pages have no third-party analytics or advertising scripts.
  • Sign-up source tag: when the sign-in page is first opened from a link that carries marketing-link parameters (utm_source, utm_medium, utm_campaign, utm_content, each up to 64 characters), your browser keeps those parameters for 30 days; when a self sign-up creates an organization, they are recorded on that organization and in the sign-up record, and used only to count sign-ups and usage per channel. No contact id, referring address or other parameter is kept; organizations entering through a partner are not tagged.
  • Organizations created by self sign-up receive a trial allowance, shown inside the workspace; organizations that use the workspace through a partner are covered by that partner's arrangement and do not receive this trial allowance.
  • We use the activity records for security and troubleshooting, and for internal usage diagnostics and security statistics (for example how each step is used and where it fails, and how many requests are refused). These statistics stay within Runnax and are not given to third parties.

How long we keep it (four kinds, separately)

  • Working data (projects, results, reports, uploaded files, the luminaire library): currently not deleted automatically, and the pages do not yet have a delete function. Report PDFs are cached briefly in server memory only; packages are generated when you download them and are not stored.
  • Daily backups: the database is backed up once a day, and each backup is deleted automatically after 30 days.
  • Release rollback backups: before each system update we keep a separate rollback backup on the server (including the database). These are currently not cleaned up automatically.
  • Audit records: the activity records above (which may include IP addresses) are kept separately for the uses described under “How we use it”; only Runnax operations staff can view them, and the pages do not show them to other users; they are currently not deleted automatically.

Questions

  • To ask what data we hold about you, or anything else about your data, email kyan@runnax.com. We will explain what we can and cannot do.
  • This mailbox uses Google Workspace: email to it is sent, received and stored by Google’s service.