StudioDash Security & Privacy

StudioDash connects to developer and business services that may contain revenue, analytics, advertising, website and application information. Protecting access to those services is therefore an important part of how StudioDash is designed.

The approach is straightforward: request appropriate access, protect credentials, avoid exposing sensitive values unnecessarily and keep you in control of the services connected to your StudioDash workspace.

• Protect access to connected services.
• Avoid displaying sensitive credentials unnecessarily.
• Use appropriate provider permissions.
• Keep the status of your connections visible.

StudioDash does not require every supported integration. You choose the services that are relevant to your apps and studio.

Different providers use different ways of authorising access. StudioDash works with the supported authentication method for each integration and is designed to request only the access needed to provide its supported features.

• Connect only the services you want to use.
• Use provider-supported authentication methods.
• Keep provider permissions under your control.
• Remove or change access when your requirements change.

Some integrations require credentials, keys or other authorisation information before StudioDash can access their reporting data. These values can provide access to commercially sensitive services and need to be treated differently from ordinary application settings.

StudioDash is designed to use the secure storage capabilities provided by Apple platforms for sensitive credentials rather than displaying or treating them as ordinary dashboard data.

• Sensitive credentials are kept separate from normal dashboard information.
• Credentials are not displayed as part of everyday analytics or reports.
• Connection status can be checked without revealing the underlying credential.
• You remain responsible for managing access and permissions with the original provider.

Where a provider allows different permission levels, StudioDash is designed around using the access required for the information and features you choose to use.

Giving an analytics application access to an account should not automatically mean giving it permission to perform unrelated administrative tasks. Provider account management, billing and specialist configuration remain with the original service.

StudioDash keeps useful information locally so dashboards can load quickly, historical reporting remains available and changing a reporting period does not require the same information to be downloaded repeatedly.

This local history is also what allows StudioDash to build a more useful picture of performance over time rather than treating every provider update as an isolated snapshot.

• Local data improves dashboard performance.
• Previously collected information supports historical reporting.
• Changing views does not require unnecessary provider requests.
• Local StudioDash data can be managed separately from your provider accounts.

StudioDash can keep supported provider information updated in the background on Mac. Background synchronisation uses the connections you have already configured rather than requiring credentials to be entered each time an update occurs.

The main StudioDash dashboard does not need to remain your active workspace for supported background updates, while provider health and synchronisation information help you understand whether those connections are working normally.

StudioDash is primarily designed to collect, organise and help you understand information from the services you connect. It is not intended to replace the account administration provided by those services.

Billing, user management, account permissions and specialist provider configuration should continue to be managed through the appropriate provider.

StudioDash is designed to help you understand your own apps and business. Revenue figures, analytics and other private operational information are not intended to become public simply because they have been brought together in StudioDash.

The interface is designed to provide useful status and analytics information without unnecessarily exposing the credentials behind your connected accounts.

When a provider needs attention, knowing that something has gone wrong is useful. Displaying the secret used to access that provider is not.

StudioDash is designed to provide useful provider health and diagnostic information while avoiding unnecessary exposure of sensitive credential values.

Connecting a service to StudioDash does not transfer ownership or administration of that account. Your relationship remains with the original provider and its own security controls continue to apply.

You should continue to follow the security recommendations of each provider, including reviewing account access, protecting credentials and removing access that is no longer required.

Private Beta participants may choose to test StudioDash with real apps and supported business services. Only accounts you are authorised to use should be connected.

Testing with real services helps validate StudioDash against genuine developer workflows, but participation does not require you to make private credentials, revenue figures or other confidential business information public.

StudioDash will continue to document how information is handled as features and optional services develop. Features that involve additional data processing or cloud services should clearly explain what information is involved before you choose to use them.

For information about how BarkinMad Studios handles personal information, refer to the BarkinMad Studios Privacy Policy.