/
PRIVACYPOLICY
66 lines (45 loc) · 5.64 KB
/
PRIVACYPOLICY
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
Amanda's Privacy Policy
Last edited 11/19/2023 at 23:44 UTC-7
This privacy policy may be updated at any time for any reason to continue to meet the needs of Amanda. New policy updates will take
effect immediately after statement updates. Updates regarding the privacy policy will be announced in Amanda's support
server (https://amanda.moe/to/server). If you do not agree with this statement, request data deletion and do not use Amanda
(see one paragraph below.)
Amanda collects and stores data sent to her from Discord permanently and/or temporarily unless a valid request in which
the requester has ownership over data requests said data to be deleted. Whether a User has ownership over data or not
is determined by if a User is making a request regarding their own User/Member data or if they are the owner of a Guild
or are making a request on the data owner's behalf with written consent if the data owner is alive and capable of providing such consent.
Users making requests regarding data must DM papiophidian (User ID: 320067006521147393) on Discord.
Requests regarding data can take up to two weeks to provide a User with or take action against said data.
Data owners reserve the right to do with their data as they please. Data owners reserve the right to file a complaint with a supervisory authority.
WHAT IS STORED:
Data which is collected and stored by Amanda from Discord will be referred to as "cache". Data falling into a category
outside of what is sent via Discord will be referred to as "local data".
Amanda's cache includes but is not limited to Users that use her, are included in select slash command calls,
or that participate in a voice channel a music queue she is hosting is active in, what Guilds she's apart of, and Guild Member voice states.
Local data includes but is not limited to Amanda related permission levels and Users which occupy said permission levels,
a User's economy related data, a User's couple data, a Users playlists which are local to Amanda and their
occupant's data, a User's third party connections, and a User's Amanda premium status.
WHY THIS DATA IS STORED:
All cache and local data is stored on first party owned machines in countries which respect data privacy laws which can be saved on machines that Amanda's code doesn't run on.
The cache serves as a data store for data sent to Amanda from Discord in a semi-persistent state.
The primary purpose is to prevent fetching necessary resources from Discord, incurring a hit to a rate limit (do x action every y interval).
Rate limits are unavoidable and trying to circumvent them can lead to negative actions against Amanda such as being banned.
An example is displaying usernames of creators on the full playlists list. The users have been fetched at one point or will be and stored for later for when the command is eventually run again. Finally, cached data is used by first party and
third party services (see "REGARDING THIRD PARTY SERVICES" for more info) to measure growth over time and provide
current statistics regarding the state of Amanda.
Local data is stored when users interact with Amanda and make use of services in which Amanda provides. These services
include but are not limited to creating and managing playlists through Amanda or participating in Amanda's economy related activities.
REGARDING THIRD PARTY SERVICES:
Amanda sends data to a couple of third party services, including current statistics and track playback.
When Amanda sends current statistic data, the data is grouped together in a way that doesn't allow individual users to be tracked or profiled.
An example is the [Chewey Bot Stats api](https://amanda.moe/to/stats) which shows how many and how often users interact with or invite Amanda.
Some services Amanda integrates with do track user habits, but these services are opt-in.
One such service which tracks user habits is [last.fm](https://last.fm) which Amanda uses to "scrobble" tracks users listen to.
These services require the user to link Amanda to their accounts to activate the functionality and the connections can be terminated at any point in time.
REGARDING COOKIES:
Amanda's website makes use of a cookie for the web dashboard. This cookie is strictly necessary and only consist of a token that cooresponds to a user ID, what paths on the website your browser should send the cookie on (currently has a value of "/" which means all paths), and when the cookie expires, which is currently always 1 year after submitting the token on the login page. This cookie verifies your identity with the server.
An example of the cookie the format above describes which the server always sends is: "token=speciallogintoken; path=/; expires=Sun, 18 Feb 2024 07:19:31 GMT"
Specific values vary such as the token and expires parameters. The token provided is for demonstration purposes only and is not real.
What the server does to verify your identity in all cases is to get the user ID cooresponding to the cookie token and see if the user is in a voice channel.
If the user is on the landing page of the dashboard, then the server takes the extra step of providing the user a means of viewing the dashboard of a voice channel should the user be in a voice channel, otherwise, it directs the user to join a voice channel to be able to be directed to the dashboard of said voice channel.
If the user is on the voice channel dashboard page, then your browser also uses that cookie to identify your connection to the WebSocket API for the WebSocket server to see if the user is in the voice channel your browser is attempting to access so that the server can link that connection to the user account tied to the cookie. This is necessary for routing events to verified subscribers related to Amanda's queue.