Account Settings
Manage your personal account settings, profile, and security preferences.
Profile Information
Update Your Name
- Navigate to Profile from the user menu
- In the Profile Information section, update your name
- Click Save
Update Your Email
- Go to Profile
- In the Profile Information section, enter your new email
- Click Save, then confirm it's you when asked
- Verify your new email address via the confirmation email
Note: Your old email will remain active until you verify the new one. Once you do, we send a notice to the old address, so a change you didn't make can't go unnoticed.
Profile Photo
Upload a profile photo to personalize your account:
- Go to Profile
- Click Select A New Photo
- Choose an image from your computer
- Click Save
Supported formats: JPG, PNG, GIF (max 2MB)
Security Settings
Confirm it's you
Before a change that adds a way into your account or your team's resources, or weakens how your account is protected, we ask you to confirm it's you, even if you're already signed in. That covers:
- adding or removing a passkey, creating or editing an API token, and authorizing the CLI
- turning two-factor authentication on or off, and viewing or regenerating your recovery codes
- setting a password, changing your email address, and verifying or removing your personal WhatsApp number
- setting, changing or removing your support PIN
- creating an S3 access key or widening what one reaches, creating a container registry key, an SFTP user or an SSH key
- inviting a team member or changing a member's role
- connecting the Storage Share mobile app, saving your team's webhook address or regenerating its secret, and rotating a database password
- signing out a browser session, changing your session security settings, removing a linked Google or GitHub sign-in, and deleting your account
A session left signed in on a shared or lost device can't be used to add a way in.
Confirm with whichever of these your account has:
- Your password
- A passkey you've already added
- A code from your authenticator app, if two-factor authentication is on
- A 6-digit code we email you, if you sign in with Google or GitHub and haven't set a password
A confirmation lasts 15 minutes, so several changes in a row only ask once. After five wrong attempts, confirming is paused for 15 minutes.
Security emails
We email your account's address whenever a way into your account or your team's resources is added, widened or removed, so a change you didn't make can't go unnoticed: a passkey, an API token or the CLI, an S3 access key, a registry key, SFTP access, an SSH key, a team invitation, an app password for a Storage Share, a new webhook address or secret, a database password rotation, two-factor authentication turned on or off, new recovery codes, a password change, a linked Google or GitHub sign-in, and a change of email address (sent to the old address). Each email says when and from which IP address and browser it happened, and what to do if it wasn't you. You can't turn these emails off.
Change Password
Update your password regularly for security:
- Navigate to Profile
- Go to the Update Password section
- Enter your current password
- Enter your new password
- Confirm your new password
- Click Save
After five wrong current passwords, changing it is paused for 15 minutes. We email you whenever your password changes, and your other browser sessions are signed out.
Password Requirements:
- Minimum 8 characters
- At least one uppercase letter
- At least one lowercase letter
- At least one number
- At least one special character recommended
Two-Factor Authentication (2FA)
Add an extra layer of security to your account:
Enable 2FA
- Go to Profile
- Find the Two Factor Authentication section
- Click Enable
- Scan the QR code with your authenticator app:
- Google Authenticator
- Authy
- 1Password
- LastPass Authenticator
- Enter the 6-digit code from your app
- Click Confirm
- Save your recovery codes in a safe place
We email you when two-factor authentication is turned on or off, and when new recovery codes are created.
Recovery Codes
Recovery codes let you access your account if you lose your phone:
- Each code can be used once
- Store them securely (password manager recommended)
- Generate new codes if you use them all
- Keep them offline for maximum security
Disable 2FA
- Go to Profile
- Find the Two Factor Authentication section
- Click Disable
- Confirm it's you
WhatsApp verification and two-factor authentication
You can verify your personal phone number during first-project setup, or later under Profile > Sign-in and security > WhatsApp. This is optional and separate from your project's billing phone number.
Enter your number with its country code. If WhatsApp verification is available for that number, choose Send verification code, then enter the six-digit code from WhatsApp. Your number is verified only after the code is accepted. You can continue setting up your project without verifying a phone.
After verification, you can separately enable WhatsApp two-factor authentication within five minutes in the same browser. If you verified your number earlier, request and enter a fresh WhatsApp code first; an old verification alone cannot enable two-factor. You must also confirm it's you. If the fresh verification expires while the page is open, verify again. Save the recovery codes shown when you enable two-factor; we show them only once. These codes are separate from authenticator-app recovery codes, and each works once. Generating a new set invalidates the previous set.
If WhatsApp two-factor is enabled and you do not have a confirmed authenticator app, signing in with your password, Google or GitHub requires a WhatsApp code or one of its recovery codes. There is no email fallback for this step. A confirmed authenticator app takes priority, and signing in directly with a passkey still needs no additional code.
Keep your recovery codes available in case WhatsApp delivery is unavailable. After five wrong recovery codes within a 15-minute window, we pause recovery attempts from that IP address until the window ends and notify you by email. We send at most one of these notices per account in 15 minutes, even if guesses come from several IP addresses. This limit applies to your account and the requesting IP together: wrong guesses from a different IP do not use up your own recovery attempts.
To change or remove your number, first disable WhatsApp two-factor and confirm it's you. Your current verified number stays active while you check or request a code for another number; a replacement becomes active only after its code is accepted. Verifying or changing your number signs out your other browsers, even before two-factor is enabled. This also happens when you verify the same number again. The browser making the change stays signed in. We email you when your verified phone or WhatsApp security settings change.
If you cannot use WhatsApp or your recovery codes, a passkey already on your account can still sign you in directly. Otherwise, contact Support and follow our existing sender-verification and account-recovery process. A phone number or failed delivery does not prove account ownership, and support does not provide an email fallback for this sign-in step.
Passkeys
Passkeys (WebAuthn) let you sign in without a password, using your device's biometrics or a security key:
- Go to Profile
- Find the Passkeys section
- Give the passkey a recognizable name (e.g., "MacBook Touch ID", "YubiKey")
- Click Add Passkey, confirm it's you, and follow your browser or device prompt
You can register several passkeys and remove any you no longer use. We email you whenever a passkey is added or removed.
A passkey as the second step after your password
A passkey also works as the second step when you sign in with your password, or with Google or GitHub. If your account has a passkey, no authenticator app and WhatsApp two-factor is off, a correct password is not enough: before you're signed in, we ask for one of your passkeys. Signing in with a passkey on its own needs no second step.
If your passkey is out of reach (a lost device, or a security key you left at home), choose Email me a code instead on that page. We send a 6-digit code to the email address on your account, and say in the email when and from where it was asked for. The code works once, in the browser that asked for it, for 10 minutes, and allows five tries. You can ask for another after a minute, and we send an account up to ten an hour. After five wrong codes, the emailed code is paused for 15 minutes and we email you to say so. Your passkeys keep working.
An emailed code is weaker than a passkey or an authenticator app: anyone who can read your email can use it, and someone who tricks you into reading it out gets in. Never read it out to anyone: we will never ask for it. Keep your email account secure, and add an authenticator app as well. It avoids relying on your email inbox, and its recovery codes cover you when you lose the device that holds your passkey. Never share authenticator or WhatsApp codes either; a passkey provides stronger protection against phishing. If your account has an authenticator app, signing in asks for its code (or a recovery code) as before, and does not offer the emailed code.
If your account has neither two-factor authentication nor a passkey, the console shows a reminder to add one, and the Sign-in and security tab of your profile says so too. Choose Remind me in a week to hide the reminder for seven days; it comes back after that until you add a passkey or turn on two-factor authentication. A passkey needs no phone: it uses Touch ID, Windows Hello or a security key.
Connected Accounts (Google & GitHub)
Sign in with your Google or GitHub account instead of a password:
- Use Sign in with Google or Sign in with GitHub on the login and registration pages
- Signing in with a Google or GitHub account that uses your account's email address links it to your account. Google has to confirm it verified that address. We email you whenever a sign-in is linked
- See your linked sign-ins under Profile > Sign-in and security > Google and GitHub, and remove any you no longer use. Removing one asks you to confirm it's you. You can't remove the only way you can sign in: set a password or add a passkey first
- If an account link ever gets out of sync, it repairs itself automatically the next time you sign in
Browser Sessions
Manage active sessions across all your devices:
View Active Sessions
See where you're logged in:
- Device type (Desktop, Mobile, Tablet)
- IP address
- Last active time
- Current session marked
Log Out Other Sessions
If you suspect unauthorized access:
- Go to Profile
- Find the Browser Sessions section
- Click Log Out Other Browser Sessions
- Enter your password, or confirm it's you if your account has no password
- Click Log Out Other Browser Sessions
This logs you out from all other devices but keeps your current session active. To sign out a single device instead, click Sign out next to it and confirm it's you.
Session Security
Control how long you stay signed in when you step away:
- Go to Profile > Session Security
- Choose your idle timeout: 24 hours (the default) or 3 hours
- Pick the shorter 3-hour window on shared or less-trusted devices for tighter security
Saving a change asks you to confirm it's you. Your session clock resets with every action, so you're only signed out after genuine inactivity. Leave it on the default and your sessions behave exactly as before.
Customer number and support PIN
Every project has a customer number, such as DD-4827-1934. Your invoices show one too: the number of the project that pays them, which is the project itself unless it is billed through another organization. You also set a support PIN. For email, phone and other unverified requests, and for later API or email replies, we ask for both before changing anything or sharing account data. A ticket opened through the Support Tickets API is verified automatically when it is created, like a console ticket.
Find your customer number
- Profile > Sign-in and security > Your customer numbers lists the number of every project you belong to, each with a copy button.
- Billing shows the number of the project you're working in, at the top of the page.
- Project settings shows it under the project's owner.
Each project has its own number. Give us the one for the project your request is about.
Set a support PIN
- Go to Profile > Sign-in and security
- In the Support PIN section, enter a PIN of 8 to 12 digits, then enter it again
- Click Set PIN, then confirm it's you when asked
Pick a PIN you'll remember. We keep only a scrambled copy of it, so nobody can read it back to you, and we can't either. A PIN that is one digit repeated (00000000), a straight run of digits (12345678, 87654321) or a block of digits said again (12341234) is refused.
The PIN is yours, not a project's: it goes with the customer number of any project you belong to. To change it, enter a new one and click Change PIN. To remove it, click Remove PIN. We email you whenever your PIN is set, changed or removed, so a change you didn't make can't go unnoticed.
When we ask for them
- You open a ticket from the console: we already know it's you, so we ask for nothing.
- A script or an agent opens a ticket with an API token: the ticket is verified automatically when opened, like a console ticket. We still mark it as opened with an API token and email you the token name. A later API or email reply still follows the normal verification checks. See the Support Tickets API.
- A script or an agent replies to a ticket with an API token: the reply is marked as sent with an API token. Before we act on the reply or share account data because of it, we ask for your customer number, your support PIN and the email address of your account.
- You write by email, phone or any other way: before we change anything or share any account data, we ask for your customer number, your support PIN and the email address of your account. If they don't match, we don't act on the request, and we ask you to open a ticket from the console instead.
- You haven't set a PIN: we can't act on a request that comes by email or phone, or on a later API or email reply that needs verification. Open a ticket from the console.
A ticket you start by email shows in your console and, under its project, in the Support Tickets API once it belongs to your account. It does straight away when it comes from the email address of your account and our mail checks confirm the message really comes from that address's domain. When it comes from another address, it does after we have confirmed it's you on that ticket with your customer number, email address and PIN: we then attach it to your account, under the project whose customer number you gave. To add to the ticket by email, answer one of our emails or keep its ticket number in the subject. That works from the address you first wrote from and, once the ticket belongs to your account, from the address of your account too. A message that does neither opens a ticket of its own.
A colleague included in the To or Cc of your original email can reply on the same ticket if both messages pass our email authentication checks, their reply preserves the signed thread reference from our email, and they keep your original address in To or Cc. Keeping only the ticket number is not enough for a colleague's reply. Their message is recorded under their own email address; this does not verify their identity, grant account access or subscribe them to future ticket emails. Recipients added only in later messages do not qualify.
We email you when our support team confirms it's you with your PIN, and when repeated wrong PINs with your customer number lock verification for an hour, so a request that wasn't yours can't go unnoticed. Each check, and each one that failed, also appears in your project's Activity Log as an action by DanubeData Support, with the request it was made for.
We never ask for your password. If someone asks for it in our name, don't share it.
Your role decides what we do
Confirming it's you doesn't widen what you can do. We do for you only what your role in the project the request is about lets you do yourself, and nothing in a project you're not a member of. We can't delete anything for an Editor (reinstalling a VPS or restoring a snapshot over a live resource counts as deleting) or change billing for them: ask an Administrator or the project owner. We give VPS root and app admin passwords only to the project owner and Administrators.
API Tokens
Manage API tokens for programmatic access:
Create an API Token
- Open Security from the account menu, then the API tokens tab
- Click Create token
- Enter a descriptive name (e.g., "CI/CD Pipeline", "Mobile App")
- Choose the token's project access:
- This project only (default): the token can only touch resources in your current project
- All your projects: account-wide access across every project you belong to
- Select permissions, grouped by resource. The list offers only what your role allows: an Editor, for example, is not offered most of the deletes or the VPS and app passwords (see Roles and Tokens):
- Read: View resources
- Write: Create, change and act on resources
- Delete: Remove resources
- Credentials and Diagnostics: read passwords, and read what resources print to their logs (see API Authentication)
- Click Create token, then confirm it's you when asked
- Copy your token immediately - it won't be shown again!
We email you whenever an API token is created, including the one the CLI gets when you authorize it.
New tokens default to This project only, and the list's Project column shows what each token reaches. A project-locked token is refused with a clear message if used against any other project. Existing tokens keep their account-wide access unless you recreate them.
Token Security
- Treat tokens like passwords
- Never commit tokens to version control
- Use environment variables
- Rotate tokens regularly
- Delete unused tokens
Revoke a Token
- Open the token on Security, API tokens
- Click Delete
- Confirm deletion
The token becomes invalid immediately.
Notification Preferences
Choose which notifications you receive, and whether they arrive by email, in-app (the Notification Center), or both. Preferences save per category:
- Account Activity: Password changes and profile updates
- Security: New sign-in alerts and suspicious-activity alerts (see below)
- Billing: Invoices, receipts, payment failures, budget alerts
- Service Alerts: Maintenance and incidents
- Marketing: Product updates, tips, newsletters
Update them:
- Go to Profile > Notification Preferences
- Toggle each category on or off, per channel
- Click Save
Sign-In Alerts
Get notified whenever your account signs in from a new device. Turn the email and in-app alerts on or off independently under Notification Preferences.
Suspicious Activity Alerts
If we block a burst of failed sign-in attempts on your account, we alert you by email and in-app. Each alert names the IP address the attempts came from and confirms your account was not accessed. Repeated attempts from the same source are grouped, so a sustained attack won't flood your inbox. Control these with the Suspicious Activity toggle in Notification Preferences.
Unsubscribe from Marketing
Click the unsubscribe link at the bottom of any marketing email.
Note: You'll still receive critical account and billing emails.
Privacy & Data
Data Export
Request a copy of your data:
- Contact support via the dashboard
- Request a data export
- Receive a download link within 48 hours
Exported data includes:
- Account information
- Resource configurations
- Billing history
- Support tickets
Account Deletion
Warning: This action is permanent and irreversible!
Before deleting your account:
- Delete all resources
- Download any needed data
- Export invoices for records
To delete your account:
- Go to Profile > Delete Account
- If anything still blocks deletion (for example, active resources or an unpaid balance), you'll see exactly what to resolve first
- Type your email address, then confirm it's you when asked
Once the checks pass, your account and the projects you own are deleted at once, and we email you at the address on your account to confirm it. We may ask for brief feedback on why you're leaving.
If an identity check is still open on one of your projects, deleting your account ends it and permanently deletes the documents uploaded for it.
What we keep. Invoices and payment records, for as long as the law requires (typically 7 years). The reason options you select stay with us. Within 30 days we erase any written feedback, your name, your email address and the account and project identifiers attached to your request.
If something goes wrong. If we can't finish deleting your account, the page says so: your request is saved, we are alerted, and we finish it and email you when it is done. You don't need to do anything. We also stop the product tips and reminders we send to your account as soon as you ask.
Account Limits
View your current resource limits:
- Open Account limits in the console sidebar, or go to console.danubedata.ro/account-limits
- See your tier, the instance sizes you can choose, and your usage against each instance limit:
- VPS Instances
- Database Instances
- Cache Instances
- Serverless Containers
- Storage Share (Nextcloud) Instances
Request Limit Increases
Need higher limits?
- Open Account limits in the console sidebar, or go to console.danubedata.ro/account-limits
- Click Request an increase
- Explain what you need the resources for (at least 50 characters)
- Raise the limits you need
- Click Send request
Requests are typically reviewed within 24-48 hours.
Billing Information
Manage billing separately for each project:
- Payment methods
- Billing address
- Tax information
- Invoices
See Billing & Payments for details.
Account Security Best Practices
Strong Authentication
- Use a strong, unique password
- Enable two-factor authentication
- Use a password manager
- Don't share your password
Session Management
- Log out from shared devices
- Review active sessions regularly
- Log out unused sessions
- Use secure networks
API Security
- Use API tokens instead of passwords
- Give minimum necessary permissions
- Rotate tokens regularly
- Monitor API usage
- Revoke suspicious tokens
Account Monitoring
- Review account activity regularly
- Check login notifications
- Monitor resource changes
- Review billing for unusual charges
- Keep contact email current
Troubleshooting
Can't Log In
Forgot password?
- Click Forgot Password on login page
- Enter your email
- Check your email for reset link
- Create a new password
Lost 2FA device?
- Click Use Recovery Code on 2FA page
- Enter one of your recovery codes
- Disable 2FA and re-enable with new device
Account locked?
- Too many failed login attempts lock accounts for 15 minutes
- Contact support if you need immediate access
Email Not Received
Check:
- Spam/junk folder
- Email filters
- Email address is correct
- Wait a few minutes (delays can happen)
Still nothing? Contact support.
Can't Enable 2FA
- Ensure your device clock is synchronized
- Try a different authenticator app
- Clear browser cache
- Try a different browser
- Contact support if issues persist
Support
Need help with your account?
- Support tickets: Through the dashboard — the fastest route
- Email: support@danubedata.ro. We'll ask for your customer number and support PIN before we change anything or share account data.