Skip to main content

Where files are stored

A file imported through the desktop app is added to the library from where it is on that computer, and that call uploads nothing. By default the app also syncs desktop files to the cloud while the owner’s storage has room. The workspace owner can turn that off. A file then leaves the computer only when the user syncs it, uses a cloud feature on it or adds it to a public link in the app, or when a cloud read through the app is called with upload_to_cloud: true. A file uploaded or imported through the hosted interfaces is in the cloud from the start. A public link is the only way a file can be reached without an account, and public pages are hidden from search engines.

Workspaces

An API key or a connection works in one workspace at a time, out of the workspaces the user allowed and still belongs to. Nothing in one workspace can be reached from another. A member can see the workspace, and the owner also controls its settings. Webhook endpoints belong to the account and receive events from every workspace it owns.

Credentials

  • An API key is shown once and stored as a SHA-256 hash. It acts in the workspaces the user gave it and can be revoked at any time.
  • An OAuth connection is made by the user in the browser and acts in the workspaces the user allows it, on the consent screen or later in Settings, Agents. The user can disconnect it in the app.
  • A script session token from get_api_session lasts 30 minutes.
  • The desktop app’s local server listens on the loopback interface only, refuses requests that come from a web page, and requires a bearer token issued to each connected client. A web page cannot drive the app through it.

Content is data, not instructions

Content inside files, documents, pulled posts, media, web pages and comments is data the tools return. It isn’t treated as instructions. The operating manual and the skill bodies are served to the connected agent and are not public pages.

Outbound requests

A URL passed to import_media or registered as a webhook is checked against private and loopback addresses on every fetch and every delivery. Webhook deliveries are signed. See Webhooks.

Feedback

submit_feedback sends a private message to the team that builds Eversince, with the previous call and the last error attached. There are no replies through it. The privacy policy and terms are on the website.