Quick Start Guide
Get up and running with GoMask.ai in just a few minutes! This guide will walk you through creating your first data masking routine.
Prerequisites
Before you begin, make sure you have:
- ā A GoMask.ai account (sign up here)
- ā Access to a database you want to mask
- ā Basic understanding of your data structure
Step 1: Access the Dashboard
- Log in to your GoMask.ai account at datafactory.gomask.ai
- You'll see the main dashboard with an overview of your routines and recent activity

Step 2: Create Your First Connector
Connectors tell GoMask.ai how to access your data sources.
- Navigate to Connectors in the sidebar
- Click "Add New Connector"
- Choose your database type (PostgreSQL, MySQL, SQL Server, Oracle)
- Fill in the connection details:
{
"name": "Production Database",
"type": "postgresql",
"host": "your-db-host.com",
"port": 5432,
"database": "your_database",
"username": "your_username",
"password": "your_password"
}
- Click "Test Connection" to verify connectivity
- Save your connector
:::tip Use read-only credentials when possible to ensure maximum security. :::
Step 3: Create a Masking Routine
Now let's create your first masking routine:
- Go to Routines in the sidebar
- Click "Create New Routine"
- Choose "Masking Routine" as the type
Basic Configuration
Fill in the routine details:
- Name: "Customer Data Masking"
- Description: "Mask customer PII for development environment"
- Source Connector: Select the connector you just created
- Destination: Choose where masked data should go
Table Selection
- GoMask.ai will automatically scan your database structure
- Select the tables you want to include in the masking routine
- For this example, let's select a
customerstable
AI-Powered Column Analysis
GoMask.ai will automatically analyse your columns and suggest masking rules:
| Column | Detected Type | Suggested Masking |
|---|---|---|
customer_id | Primary Key | Keep Original |
first_name | First Name | Synthetic Names |
last_name | Last Name | Synthetic Names |
email | Email Address | Synthetic Emails |
phone | Phone Number | Format Preserving |
ssn | SSN | Tokenisation |
credit_score | Numeric | Range Preserving |
Review and Customise Rules
You can customise any of the suggested rules:
- Click on any column to modify its masking rule
- Choose from various masking techniques:
- Synthetic Generation: Create realistic fake data
- Tokenisation: Replace with consistent tokens
- Encryption: Reversible encryption
- Shuffling: Randomise within the dataset
- Custom Functions: Use your own masking logic
Example: Customising Email Masking
// Custom email masking function
function maskEmail(originalEmail) {
const [username, domain] = originalEmail.split('@');
const maskedUsername = generateRandomString(username.length);
return `${maskedUsername}@example.com`;
}
Step 4: Run Your First Masking Job
-
Review your routine configuration
-
Click "Save & Execute"
-
Choose execution options:
- Full Scan: Process all data
- Sample Run: Process a subset for testing
- Scheduled: Set up recurring execution
-
Monitor the progress in real-time:
š” Initialising routine...
š¢ Connected to source database
š” Analyzing data structure...
š¢ Applied masking rules to 15,847 records
š” Writing to destination...
š¢ Masking complete! Processed 15,847 records in 2m 34s
Step 5: Validate Your Results
After the routine completes:
-
Review the execution summary:
- Records processed: 15,847
- Success rate: 100%
- Execution time: 2m 34s
- Data integrity checks: ā Passed
-
Sample the masked data:
-- Original data SELECT first_name, last_name, email FROM customers LIMIT 5; -- Masked data first_name | last_name | email -----------|-----------|------------------ Sarah | Johnson | [email protected] Michael | Chen | [email protected] -
Verify data relationships:
- Foreign key constraints maintained
- Data types preserved
- Statistical distributions similar
Step 6: Set Up Monitoring (Optional)
Enable monitoring to track your routine's performance:
-
Go to Settings ā Notifications
-
Configure alerts for:
- Execution failures
- Performance degradation
- Data quality issues
-
Set up webhooks for integration with your monitoring tools
Next Steps
Congratulations! You've successfully created and executed your first masking routine. Here's what to explore next:
š§ Advanced Features
š„ Team Collaboration
š Integrations
š Compliance
Common Next Actions
Automate Your Routine
Set up your routine to run automatically:
# Using the GoMask.ai CLI
gomask routine schedule \
--routine-id "your-routine-id" \
--cron "0 2 * * *" \
--timezone "UTC"
Create Additional Routines
- Development Environment: Daily refresh with latest data
- Testing Environment: Weekly full refresh
- Analytics Environment: Monthly aggregated data
Integrate with Your Workflow
Add GoMask.ai to your existing data pipeline:
# GitHub Actions example
- name: Refresh Test Data
uses: gomask-ai/github-action@v1
with:
routine-id: ${{ secrets.ROUTINE_ID }}
api-key: ${{ secrets.GOMASK_API_KEY }}
Troubleshooting
Having issues? Check these common solutions:
| Issue | Solution |
|---|---|
| Connection failed | Verify credentials and network access |
| Slow performance | Check data volume and optimise queries |
| Data quality issues | Review masking rules and constraints |
For more help, visit our troubleshooting guide or contact [email protected].
š You're now ready to protect your sensitive data with GoMask.ai!
Questions? Check out our video tutorials or contact us at [email protected].