Exiting WEMAZU

🚪 Learn how to export your data, configurations, and project settings. Understand what happens to your data when you close your account.

This guide explains how to export your WEMAZU data, what gets deleted when you close your account, and what data may be temporarily retained.

Table of Contents

  1. Exporting Your Data
  2. What Data Can Be Exported
  3. Account Closure
  4. What Gets Deleted
  5. What May Be Retained
  6. Deployed Applications
  7. Data Export Process

Exporting Your Data

Why Export?

Before closing your account or migrating away from WEMAZU, you may want to:

  • ✅ Keep a backup of your configuration
  • ✅ Migrate to another platform
  • ✅ Maintain an audit trail
  • ✅ Comply with data retention requirements

How to Export

Current Status:

  • ✅ Export Logs: Export logs directly from the dashboard (download as JSON)
  • ✅ API Access: You can export data via API endpoints
  • ✅ Database Access: Administrators can export directly from database

Manual Export Steps:

  1. Use API endpoints to fetch your data
  2. Save responses as JSON files
  3. Export deployment history
  4. Export project configurations
  5. Export domain configurations

API Endpoints for Export:

# Export projects
GET /api/projects

# Export domains
GET /api/projects/{project_id}/domains

# Export deployments
GET /api/projects/{project_id}/deployments

# Export logs
GET /api/logs?project_id={project_id}&limit=10000

What Data Can Be Exported

Project Data

Exportable Fields:

  • ✅ Project ID
  • ✅ Project name
  • ✅ GitHub owner/repo
  • ✅ Webhook secret
  • ✅ Created/updated timestamps
  • ✅ Status

Example Export:

{
  "id": "abc123...",
  "name": "My Web App",
  "github_owner": "atypisch",
  "github_repo": "testdeploy",
  "webhook_secret": "secret123...",
  "status": "active",
  "created_at": "2025-01-01T10:00:00Z",
  "updated_at": "2025-01-25T10:00:00Z"
}

Domain Data

Exportable Fields:

  • ✅ Domain ID
  • ✅ Domain name
  • ✅ Server ID
  • ✅ Deploy path
  • ✅ Status
  • ✅ Branch configurations
  • ✅ Created/updated timestamps

Example Export:

{
  "id": "def456...",
  "domain": "example.com",
  "server_id": "server123...",
  "deploy_path": "/var/www/html",
  "status": "active",
  "branches": [
    {
      "branch": "main",
      "auto_deploy": true,
      "deploy_path": "/var/www/production"
    }
  ],
  "created_at": "2025-01-01T10:00:00Z"
}

Deployment History

Exportable Fields:

  • ✅ Deployment ID
  • ✅ Project ID
  • ✅ Domain ID
  • ✅ Branch
  • ✅ Commit SHA
  • ✅ Status
  • ✅ Build timestamps
  • ✅ Output (for SSH deployments)
  • ✅ Error messages (if failed)
  • ✅ Created/updated timestamps

Example Export:

{
  "id": "ghi789...",
  "project_id": "abc123...",
  "domain_id": "def456...",
  "branch": "main",
  "commit_sha": "abc123def456...",
  "status": "success",
  "build_started_at": "2025-01-25T10:00:00Z",
  "build_completed_at": "2025-01-25T10:01:00Z",
  "output": "git pull output...",
  "created_at": "2025-01-25T10:00:00Z"
}

Log Data

Exportable Fields:

  • ✅ Log ID
  • ✅ Level (info, warning, error, debug)
  • ✅ Message
  • ✅ Context (JSON)
  • ✅ Project ID
  • ✅ Deployment ID
  • ✅ Created timestamp

Example Export:

{
  "id": "log123...",
  "level": "info",
  "message": "Deployment started",
  "action": "deployment.create",
  "project_id": "abc123...",
  "deployment_id": "ghi789...",
  "context": {
    "branch": "main",
    "commit_sha": "abc123..."
  },
  "created_at": "2025-01-25T10:00:00Z"
}

Server Data

Exportable Fields:

  • ✅ Server ID
  • ✅ Server name
  • ✅ Server type (ftp, sftp, vps)
  • ✅ Host
  • ✅ Port
  • ⚠️ Password: Not exported (for security)
  • ✅ Created/updated timestamps

Example Export:

{
  "id": "server123...",
  "name": "Production Server",
  "type": "vps",
  "host": "your-server-ip",
  "port": 22,
  "created_at": "2025-01-01T10:00:00Z"
}

⚠️ Security Note: Server passwords and GitHub tokens are NOT exported for security reasons. You must re-enter these in your new platform.

Account Closure

How to Close Your Account

Current Process:

  1. Delete Projects: Delete all your projects (this cascades to domains, deployments)
  2. Remove GitHub Token: Go to Settings → GitHub Connection → Disconnect
  3. Contact Support: Request account closure (if needed)

Account Closure Feature:

  • ✅ Account closure feature in Settings
  • ✅ One-click account deletion
  • ✅ Automatic cleanup of all data (projects, domains, deployments, GitHub tokens, servers)

What Happens During Closure

Immediate Actions:

  1. ✅ All projects are deleted (cascade to domains, deployments)
  2. ✅ GitHub token is removed
  3. ✅ User data is soft-deleted (marked as deleted, not physically removed)

Cascade Deletions:

  • Projects → Domains → Domain Branches
  • Projects → Deployments
  • Projects → Environments
  • Projects → Logs (user-specific logs)

Deletion Process:

  • User data is soft-deleted (marked as deleted, not physically removed)
  • All projects for the user are deleted
  • GitHub tokens are removed
  • All related data (domains, deployments, environments) are automatically deleted

What Gets Deleted

Immediately Deleted

User Data:

  • ✅ Projects (and all related data)
  • ✅ Domains
  • ✅ Domain branches
  • ✅ Deployments
  • ✅ Environments
  • ✅ GitHub token
  • ✅ Server configurations (if user-owned)

Data Deleted:

  • ✅ All projects (for your user)
  • ✅ All domains (for your projects)
  • ✅ All domain branch configurations (for your domains)
  • ✅ All deployments (for your projects)
  • ✅ All environments (for your projects)
  • ✅ All GitHub tokens (for your user)
  • ✅ User-specific log records

Cascade Deletions

When a Project is Deleted:

  • All domains for that project are automatically deleted
  • All domain branch configurations are automatically deleted
  • All deployments for that project are automatically deleted
  • All environments for that project are automatically deleted

When a Domain is Deleted:

  • All domain branch configurations for that domain are automatically deleted

What May Be Retained

Temporarily Retained Data

Logs:

  • ⚠️ System Logs: System-wide logs may be retained for debugging
  • ⚠️ Audit Logs: Audit logs may be retained for compliance
  • ⚠️ Error Logs: Error logs may be retained for system improvement

Retention Period:

  • Typically 30-90 days
  • May be longer for compliance requirements
  • Check WEMAZU's data retention policy

What Gets Retained:

  • System logs (not user-specific) may be retained for debugging
  • Audit logs may be retained for compliance purposes

Backup Data

Database Backups:

  • ⚠️ Backup Retention: Database backups may contain your data
  • ⚠️ Backup Period: Typically 30-90 days
  • ⚠️ Backup Location: Stored securely, encrypted

File Backups:

  • ⚠️ Log Files: Log files may be backed up
  • ⚠️ Configuration Files: Configuration backups may exist

Recovery:

  • Backups are for disaster recovery
  • Not used for data restoration after account closure
  • Deleted according to retention policy

Anonymized Data

Analytics:

  • ⚠️ Usage Statistics: Anonymized usage statistics may be retained
  • ⚠️ Performance Metrics: Aggregated performance data
  • ⚠️ No Personal Data: No personally identifiable information

Purpose:

  • System improvement
  • Performance optimization
  • Feature development

Deployed Applications

What Happens to Deployed Code?

Important: Closing your WEMAZU account does NOT delete your deployed applications.

What Stays:

  • ✅ Deployed Files: All files on your servers remain
  • ✅ Git Repositories: Git repositories on servers remain (for SSH deployments)
  • ✅ Databases: Application databases remain
  • ✅ Configuration: Server configuration remains

What You Need to Do:

  1. ✅ Backup Your Applications: Backup your deployed code before closing account
  2. ✅ Export Configuration: Export environment variables, configuration files
  3. ✅ Update Deployment Process: Set up alternative deployment method
  4. ✅ Clean Up (Optional): Manually remove files from servers if desired

Server Access

After Account Closure:

  • ✅ You still have access to your servers (via SSH, FTP, etc.)
  • ✅ WEMAZU no longer has access (GitHub token removed)
  • ✅ You can continue deploying manually
  • ✅ You can set up alternative deployment tools

Server Credentials:

  • ✅ Your server credentials are not affected
  • ✅ You can continue using your servers
  • ⚠️ WEMAZU's server configurations are deleted (but servers remain)

Data Export Process

Step-by-Step Export

1. Export Projects

# Get all projects
curl -H "Authorization: Bearer YOUR_TOKEN" \
  https://wemazu.example.com/api/projects > projects.json

2. Export Domains for Each Project

# For each project, export domains
PROJECT_ID="abc123..."
curl -H "Authorization: Bearer YOUR_TOKEN" \
  "https://wemazu.example.com/api/projects/${PROJECT_ID}/domains" > domains-${PROJECT_ID}.json

3. Export Deployments

# Export deployments for each project
curl -H "Authorization: Bearer YOUR_TOKEN" \
  "https://wemazu.example.com/api/projects/${PROJECT_ID}/deployments?limit=10000" > deployments-${PROJECT_ID}.json

4. Export Logs

# Export logs for each project
curl -H "Authorization: Bearer YOUR_TOKEN" \
  "https://wemazu.example.com/api/logs?project_id=${PROJECT_ID}&limit=10000" > logs-${PROJECT_ID}.json

5. Export Server Configurations

# Export servers (passwords not included)
curl -H "Authorization: Bearer YOUR_TOKEN" \
  https://wemazu.example.com/api/servers > servers.json

Complete Export Script

Example Script (Pseudo-code):

#!/bin/bash
TOKEN="your_token_here"
BASE_URL="https://wemazu.example.com/api"

# Export projects
curl -H "Authorization: Bearer $TOKEN" \
  "${BASE_URL}/projects" > projects.json

# For each project, export related data
for project_id in $(cat projects.json | jq -r '.[].id'); do
  # Export domains
  curl -H "Authorization: Bearer $TOKEN" \
    "${BASE_URL}/projects/${project_id}/domains" > "domains-${project_id}.json"
  
  # Export deployments
  curl -H "Authorization: Bearer $TOKEN" \
    "${BASE_URL}/projects/${project_id}/deployments?limit=10000" > "deployments-${project_id}.json"
  
  # Export logs
  curl -H "Authorization: Bearer $TOKEN" \
    "${BASE_URL}/logs?project_id=${project_id}&limit=10000" > "logs-${project_id}.json"
done

# Export servers
curl -H "Authorization: Bearer $TOKEN" \
  "${BASE_URL}/servers" > servers.json

echo "Export complete!"

Export Format

Recommended Format:

  • JSON: Use JSON for structured data
  • CSV: Use CSV for tabular data (if needed)
  • Archive: Compress all exports into a single archive

Example Archive Structure:

wemazu-export-2025-01-25/
├── projects.json
├── servers.json
├── project-abc123/
│   ├── domains.json
│   ├── deployments.json
│   └── logs.json
└── project-def456/
    ├── domains.json
    ├── deployments.json
    └── logs.json

Data Deletion Request

How to Request Deletion

Current Process:

  1. Delete Projects: Delete all projects via dashboard
  2. Remove GitHub Token: Disconnect GitHub in Settings
  3. Contact Support: Request complete data deletion

Future Process (Planned):

  • Self-service data deletion
  • GDPR-compliant deletion process
  • Deletion confirmation

GDPR Right to Erasure

Your Rights:

  • ✅ Request deletion of your personal data
  • ✅ Request deletion of all your data
  • ✅ Receive confirmation of deletion

WEMAZU's Obligations:

  • ✅ Delete data within 30 days (GDPR requirement)
  • ✅ Confirm deletion
  • ✅ Delete from backups (within retention period)

Request Process:

  1. Contact WEMAZU support
  2. Verify your identity
  3. Request data deletion
  4. Receive confirmation
  5. Data deleted within 30 days

Summary

What You Can Export

  • ✅ Projects
  • ✅ Domains
  • ✅ Deployments
  • ✅ Logs
  • ✅ Server configurations (without passwords)

What Gets Deleted

  • ✅ All projects and related data
  • ✅ GitHub tokens
  • ✅ User-specific logs
  • ✅ Server configurations

What May Be Retained

  • ⚠️ System logs (30-90 days)
  • ⚠️ Database backups (30-90 days)
  • ⚠️ Anonymized analytics

Deployed Applications

  • ✅ NOT deleted - Your deployed code remains on servers
  • ✅ You retain server access
  • ✅ You can continue deploying manually

Next Steps: