01
Scope and contact
This policy covers Alerta Chart’s website, mobile application and Community. For privacy requests, contact the Alerta Chart team at [email protected]. Do not send passwords, API keys or unnecessary identity documents with your request.
02
How information reaches us
You provide information when creating an account, changing settings, saving work, publishing or contacting support. Sign-in and purchase providers supply the identifiers and status needed to connect a login or entitlement to your account.
Use of the service also generates technical and interaction records, such as request times, IP and device/browser information, error details and content views. Public information supplied by another member may mention you; contact us if it is inaccurate or infringes your rights.
03
Account and service information
We process account identifiers, email, sign-in provider information and profile details you provide; subscription status and purchase references; saved watchlists, settings and alerts; notification tokens; and support correspondence. Sign-in and payment providers process information for their own services under their policies. Payment credentials entered with a store or payment provider are handled by that provider.
04
Charts, saved work and device storage
Chart preferences, drawings, watchlists and script-related work may be stored on your device or synchronized through account features where available. Local-only work is different from a published Community post; opening a chart does not by itself publish your analysis.
Clearing browser or app storage can remove local work and sign-in information. Signing out is not the same as erasing every local file or cloud record. Use the relevant workspace, publication and account controls for each purpose.
05
Community data and visibility
Community profiles can show a username, display name, avatar, biography, links and badges. Public posts, charts, images, comments and their visible interactions can be seen by users and visitors and may appear in search engines. Do not put private information in these fields.
We also store drafts, revisions, likes, bookmarks, follows, subscriptions to authors, reports, moderation records and script access requests. Drafts, bookmarks, reports and verification application details are not presented as public posts. Invited scripts are limited by platform access settings; authorized recipients can read and copy their source. Email and sign-in details are not intentionally displayed as public profile fields.
06
Reports, verification and access records
Reports and verification requests can contain explanations, evidence links and review decisions. Script invitations record requests, recipients, grants, expiry or revocation where applicable. These records support safety, access decisions and handling of disputes.
We do not display a reporter’s email or verification evidence as part of a public post. Review may require access by authorized team members and relevant providers or authorities where lawful; confidentiality cannot be promised against legal disclosure requirements.
07
Purposes and grounds for processing
Account, purchase and saved-workspace data enable the service you request. Community data enables publication, discovery, interactions, access management and moderation. Technical logs, network/device information and service identifiers help operate the platform, prevent abuse and diagnose faults.
Depending on the activity and applicable law, processing relies on providing the service or performing a contract, legal obligations, legitimate interests such as security subject to your rights, or consent where required. Accepting publication terms is not blanket consent to data processing or marketing.
08
Service providers and transfers
Data is processed by hosting, database, media storage and delivery, authentication, payment, analytics and notification providers as needed for their functions. Community images use object storage and delivery infrastructure; notification providers route alerts. Google Analytics is used on the website. These disclosures differ from publishing content to the Community.
Provider infrastructure may process data outside your country. Applicable transfer requirements and safeguards depend on the service and jurisdiction; contact us for details about recipients and transfers. We do not sell personal data.
09
International processing and disclosures
The service can involve providers and infrastructure in more than one country. The place you use the app does not by itself determine where every record is stored. Contact us for information about the recipients and transfer arrangements relevant to your data.
Cross-border processing must have the basis and safeguards required by applicable law. Legal requests, prevention of abuse or a business transfer may also require limited disclosure, subject to necessity, appropriate protection and any required notice. This policy is not blanket consent to overseas transfers.
11
Notifications and service communications
When you enable push notifications, a device or browser token and delivery preferences allow notifications to reach that installation. Alert content may appear on a lock screen or other device surface depending on your settings. Revoke permissions in the browser or operating system and manage alerts in the app.
Account, purchase and security messages serve a different purpose from promotional communications. Publication approval is not marketing permission. Where consent is required for marketing, it must be separate and withdrawable.
12
Retention, removal and account deletion
Data is retained for the purpose it serves, the life of the account or publication, and applicable legal or security needs. Withdrawing a post removes its public availability but may leave revisions and moderation records. Account deletion removes linked records according to the service’s deletion process; media cleanup, backups and records retained for legal or dispute purposes may take longer. We do not promise that every copy disappears immediately.
Content copied by other users, search engines or authorized script recipients is outside our direct control. To request erasure of retained personal data, contact us. Cancel store subscriptions separately before or after deleting the account to avoid further renewal.
13
Your choices and rights
You can edit available profile fields, remove your publications, change follows and notification settings, and request account deletion. Depending on applicable law, you may request access, correction, erasure, restriction, portability or object to processing, withdraw consent where relevant, and complain to the competent data protection authority. Contact [email protected]; we may need proportionate information to verify your request. Some data is necessary to provide the requested service.
14
Making a privacy request
Write to [email protected] from your account email where possible, explain the right you want to exercise and identify the relevant records. We may ask for limited information to prevent disclosure or deletion for the wrong person; do not send an identity document unless specifically needed.
We assess requests under applicable law, explain any lawful limits and respond within the required period. Deletion can be restricted by legal retention duties, the rights of others or an ongoing claim. Where relevant, you may also ask about transfers, correction of automated assessments and notification of corrections to recipients.
15
Security, children and updates
We use access controls and encrypted connections, but no online service can guarantee absolute security. The service is not directed at children under 13; local age and guardian-consent requirements may be higher. Contact us if a child has supplied personal data. This policy may change as features evolve; the date above identifies the current text, and material changes will be communicated as appropriate.