FAQ LOGIN GET STARTED

Pricing Overview

Simple, transparent pricing for all CENTCOM.io services.

Service Description Price
Storage Cloud storage for notes, attachments, and files $1.00 / GB / month
Telephone Number (US) Dedicated US phone number for calls and SMS $10.00 / month

Notes Features

CENTCOM.io Notes provides a powerful, secure note-taking experience.

  • Rich Text Editor — Full formatting support including headings, lists, links, and more
  • Auto-Save — Notes are automatically saved as you type
  • File Attachments — Attach images, PDFs, and documents to any note
  • Folder Organization — Organize notes into folders and subfolders
  • Tags — Add tags for quick filtering and search
  • Search — Full-text search across all notes and attachments
  • Sharing — Share notes with team members or external collaborators
  • Import / Export — Portable JSON format for data freedom

CENTCOM.io Notes Import / Export Format

CENTCOM.io uses a JSON-based format designed for maximum interoperability. This format supports rich content, attachments, tags, and folder organization.

Format Version

Current version: 1.0

Export Options

CENTCOM.io supports two export formats:

  • 1. JSON + ZIP Archive — Recommended for large attachments. Exports a .zip file containing notes.json and an attachments/ folder with original files.
  • 2. Single JSON File — For portability. Attachments are base64-encoded inline (larger file size).

Export Structure (ZIP Archive)

The recommended ZIP export contains:

centcom-export-2026-01-02.zip
├── notes.json
└── attachments/
    ├── 550e8400.../example_filename.pdf
    └── 661f9511.../image.png

JSON Format

The notes.json file structure:

{
  "version": "1.0",
  "exported_at": "2026-01-02T20:50:00Z",
  "app": "centcom.io",
  "export_type": "archive",  // or "inline" for base64
  "account": {
    "email": "user@example.com",
    "name": "John Doe"
  },
  "notes": [
    {
      "uuid": "550e8400-e29b-41d4-a716-446655440000",
      "title": "Meeting Notes",
      "content_text": "Plain text version of the note...",
      "content_html": "<p>Rich HTML version...</p>",
      "created_at": "2026-01-01T10:00:00Z",
      "updated_at": "2026-01-02T15:30:00Z",
      "folder": "Work",
      "tags": ["meetings", "important"],
      "attachments": [
        {
          "filename": "example_filename.pdf",
          "mime_type": "application/pdf",
          "size_bytes": 12345,
          "path": "attachments/550e8400.../example_filename.pdf",  // ZIP archive
          "data": "base64-encoded..."  // OR inline (mutually exclusive)
        }
      ]
    }
  ]
}

Field Definitions

Field Type Description
version string Format version for compatibility checking
exported_at string (ISO 8601) UTC timestamp of export
uuid string (UUID v4) Unique identifier for deduplication on re-import
title string Note title (may be empty)
content_text string Plain text version of note content
content_html string HTML version with formatting preserved
folder string | null Folder path (e.g., "Work" or "Work/Projects")
tags array List of tag strings
attachments array List of attachment objects (see below)
attachments[].path string Relative path to file in ZIP archive (archive export)
attachments[].data string Base64-encoded file content (inline export)

Inline Attachment References

When users drag/drop files onto the note editor, an inline reference marker is inserted into the note content:

// Active attachment reference (green text in editor)
[[[ 📎 ATTACHED: example_filename.pdf ]]]

// Deleted attachment reference (gray text + strikethrough)
// Applied via rich text formatting, not wrapped HTML
[[[ 📎 ATTACHED: example_filename.pdf ]]]  ← with color:#999 + strike formatting

These markers appear in content_html and content_text. The actual file data is stored separately in the attachments array. When importing, you may:

  • Parse these markers to identify which attachments are referenced inline
  • Preserve them as-is for display compatibility
  • Convert them to your app's native attachment format

Import Behavior

When importing notes:

  • Notes with matching uuid will be updated (not duplicated)
  • Missing folders will be created automatically
  • Both content_text and content_html are accepted; HTML takes precedence if both provided
  • Attachments with path are read from the ZIP archive
  • Attachments with data are decoded from base64
  • All attachments are stored as separate files on disk (not inline)