fix: replace bucket terminology with device across docs

docs/tagodeploy/getting-started/index.md

@@ -59,7 +59,7 @@ define their own constraints for:
 - Maximum device connections
 - Data storage allocation
 - Dashboard quantities
-- Tag and bucket limits
+- Tag limit
 
 ![Image 4](/docs_imagem/tagoio/external-5170193e.png)
 

docs/tagoio/analysis/index.md

@@ -29,7 +29,7 @@ If you prefer to host code yourself, you can run External Analyses from your own
 
 TagoIO supports three runtimes for Analysis. Each runtime has different approaches to dependency management and development workflows.
 
-All runtimes support the same TagoIO SDK functionality for working with devices, buckets, and other platform features. The main differences are in language features and how you manage external dependencies.
+All runtimes support the same TagoIO SDK functionality for working with devices and other platform features. The main differences are in language features and how you manage external dependencies.
 
 ### Deno Runtime
 

docs/tagoio/devices/data-management/device-data-management.md

@@ -94,15 +94,15 @@ TagoIO supports two types of devices: [Mutable](/docs/tagoio/devices/) and [Immu
 
 1. **Immutable Devices**: If your CSV includes data for the **time** field, the time must fall within your [chunk period and retention configuration](/docs/tagoio/devices/data-management/data-retention-feature.md). If you attempt to import data outside the retention period, you will encounter an error. To resolve this, ensure the date and time information fits within your retention period.
 
-2. **Mutable Devices**: These devices can store up to 50 000 records. Your import will fail if this limit is exceeded. You can check the number of data records in your bucket in the Device module.
+2. **Mutable Devices**: These devices can store up to 50 000 records. Your import will fail if this limit is exceeded. You can check the number of data records in your device in the Device module.
 
 ## Exporting
 
 The **Export** button, located in the top right corner of the **Data** tab, allows for variable data export in various formats. Further details on exporting data for specific device types can be found under: [Data Export](/docs/tagoio/devices/data-management/data-export.md).
 
 ## Backing up your data
 
-To back up your device data, click the **More** button located in the top right corner, then select **Backup to Files** under the **Data** tab. This will export all your bucket data to your [Files](/docs/tagoio/files), creating a secure copy of your sensor data. This feature is particularly useful for safeguarding your data or capturing snapshots at specific points in time.
+To back up your device data, click the **More** button located in the top right corner, then select **Backup to Files** under the **Data** tab. This will export all your device data to your [Files](/docs/tagoio/files), creating a secure copy of your sensor data. This feature is particularly useful for safeguarding your data or capturing snapshots at specific points in time.
 
 The tool automatically backs up all your device data. If you need to apply filters before backing up, use the Data Export function to refine your data, and then save it locally or in your Files. For [Immutable devices](/docs/tagoio/devices/), clicking the **Backup to Files** button will redirect you to the **Chunk Management** tab, where you can select specific chunks of data to back up to your Files.
 

docs/tagoio/integrations/networks/everynet-lorawan.md

@@ -26,10 +26,7 @@ TagoIO application.
    - Click the _Create Authorization_ button.
    - Provide a meaningful name for the authorization (for example:
      `Everynet-Integration`).
-   - Select the token type: `Ingress`.
-   - Select the bucket: you may use the default data bucket or create a new
-     bucket specifically for Everynet.
-   - Select the permission: `Write`.
+   - Select the token format: `Standard`.
    - Click _Save_. The authorization will be created and the token will appear.
      Copy the token and keep it safe because it will not be shown again.
 

docs/tagoio/integrations/networks/mqtt/mqtt-process-data-publish-it-and-subscribe-to-a-topic.md

@@ -89,7 +89,7 @@ async function mqttPushExample(context, scope) {
   // Publishing to MQTT
   const mqtt = new Services().mqtt;
   await mqtt.publish({
-    bucket: DEVICE_ID,
+    device: DEVICE_ID,
     message: JSON.stringify(myDataObject),
     topic: "sensor/output",
     options,

docs/tagoio/integrations/networks/mqtt/mqtt-publishing-and-subscribing.md

@@ -53,7 +53,7 @@ there.
 
 <!-- Image temporarily disabled: Action example - /cdn.elev.io/file/uploads/pmfKQdI17QsonYtKqFR0lo14i0mduRrZCtXE2bzClic/V6qqrtoqow2xmYBCAXSAPiLPUuftZotTvMGTz_dq0W8/1588011165303-pog.png -->
 
-The payload can be sent directly to your [bucket](/docs/tagoio/devices/),
+The payload can be sent directly to your [device](/docs/tagoio/devices/),
 trigger an Analysis, or be delivered via SMS or E‑mail.
 
 If you send the payload in JSON format, the TagoIO backend automatically adds a

docs/tagoio/integrations/networks/mqtt/mqtt-retain-on-tagoio-broker.md

@@ -66,7 +66,7 @@ async function mqttPushExample(context, scope) {
   // Publishing to MQTT
   const MQTT = new Services({ token: context.token }).MQTT;
   await MQTT.publish({
-    bucket: myData.device, // for immutable/mutable devices
+    device: myData.device, // for immutable/mutable devices
     message: JSON.stringify(myDataObject),
     topic: "tago/my_topic",
     options,

docs/tagoio/integrations/networks/mqtt/mqtt.md

@@ -36,7 +36,7 @@ topic and receive the published payloads.
 TagoIO’s MQTT broker is responsible for pushing data to clients whenever new
 information is published on the specific topics they are subscribed to. Unlike a
 full‑featured MQTT implementation, it focuses mainly on ingesting sensor data
-into our data buckets, so some standard features such as the native **Retain**
+into our devices, so some standard features such as the native **Retain**
 flag are not supported. A workaround that achieves similar functionality can be
 found in the article
 [MQTT Retain on TagoIO Broker](/docs/tagoio/integrations/networks/mqtt/mqtt-retain-on-tagoio-broker.md).
@@ -71,7 +71,7 @@ Encryption across the network can be handled with SSL independently of the MQTT
 protocol itself. Additional security can also be added through
 application‑encrypted data that is sent and received. At TagoIO you can send
 your data encrypted directly to [Analysis](/docs/tagoio/analysis/index.md), decrypt it
-there, and then insert the data into your [Bucket](/docs/tagoio/devices/index.md). This
+there, and then insert the data into your [device](/docs/tagoio/devices/index.md). This
 procedure can increase security if your data is sensitive or if you simply want
 an extra layer of protection.
 
@@ -81,10 +81,10 @@ When you first send data through MQTT to your device, you’ll be able to
 visualize the connection and message through the
 [Live Inspector](/docs/tagoio/devices/live-inspector.md) on your device. Those
 messages indicate that the connection is working, but nothing is being stored in
-your bucket yet.
+your device yet.
 
 From this point, you need to create an [Action](/docs/tagoio/actions/index.md) with
-trigger **MQTT** and type **Insert to Device Bucket**. Once configured, you
+trigger **MQTT** and type **Insert to Device**. Once configured, you
 should see the data being stored in the Live Inspector.
 
 If you don’t send the data using the

docs/tagoio/my-account/backups.md

@@ -70,9 +70,9 @@ Find the backup in the list and click the **download icon** (⬇️) in the **Ac
 backup-<profile-id>/
 ├── files/
 │   ├── <uploaded files and documents>
-│   └── buckets/
-│       └── <bucket-id>/
-│           └── <bucket files>
+│   └── devices/
+│       └── <device-id>/
+│           └── <device files>
 ├── resources/
 │   ├── access_management.json
 │   ├── actions.json
@@ -92,7 +92,7 @@ backup-<profile-id>/
         └── <version files in JSON>
 ```
 
-- **files/** - Uploaded files and documents, organized by bucket.
+- **files/** - Uploaded files and documents, organized by device.
 - **resources/** - Profile resource configurations exported as JSON.
 - **versioning/** - Historical versions of resources such as dashboards.
 

docs/tagoio/profiles/index.md

@@ -40,7 +40,7 @@ Add others to your profiles by adding their e‑mails in the team section. To in
 
 ## Generating Account Tokens
 
-[Account tokens](/docs/tagoio/profiles/account-token.md) are used to authenticate requests in the TagoIO API. You can use our API to make integrations and create devices, buckets, dashboards, send data, and more. To create an account token, follow these steps:
+[Account tokens](/docs/tagoio/profiles/account-token.md) are used to authenticate requests in the TagoIO API. You can use our API to make integrations and create devices, dashboards, send data, and more. To create an account token, follow these steps:
 
 1. Click on the **Tokens** tab.
 2. Add a name, permission, expiration, and click **Generate Token**.

docs/tagoio/tutorials/abs-telemetry.md

@@ -46,6 +46,6 @@ Add a **[device](https://tago.io/devices)** in your account at TagoIO. Go to _De
 
 Click on **'Create Device'**, and you will have confirmation that the device was created.
 
-Turn your device on, and wait for the data to arrive and hit your data **[bucket](/docs/tagoio/devices/)**, and it will be ready to be shown in the dashboards. You can start to build your **[Dashboard](/docs/tagoio/dashboards/)** by adding gauges, tables and more.
+Turn your device on, and wait for the data to arrive and hit your **[device](/docs/tagoio/devices/)**, and it will be ready to be shown in the dashboards. You can start to build your **[Dashboard](/docs/tagoio/dashboards/)** by adding gauges, tables and more.
 
 Enjoy your ABS devices with TagoIO!

docs/tagoio/tutorials/adeunis-with-lorawan.md

@@ -50,9 +50,9 @@ Each provider link points to the corresponding TagoIO tutorial for configuring
 Adeunis devices with that network.
 
 After you have completed the setup above, you will be ready to move forward.\
-Now, just turn your Adeunis device on and wait for the data to hit your **data
-bucket**. Every time the device sends data, the parser will be executed, the
-extracted data sent to the bucket, and it will be ready to be shown in the
+Now, just turn your Adeunis device on and wait for the data to hit your
+**device**. Every time the device sends data, the parser will be executed, the
+extracted data sent to the device, and it will be ready to be shown in the
 dashboards.
 
 You can start building your [dashboards](/docs/tagoio/dashboards/) immediately.\

docs/tagoio/tutorials/adeunis-with-sigfox.md

@@ -35,9 +35,9 @@ To add an Adeunis device in TagoIO:
 
 ### Integrate your Adeunis with TagoIO
 
-1. Turn on your Adeunis device and wait for the data to reach your bucket.
+1. Turn on your Adeunis device and wait for the data to reach your TagoIO Device.
 2. Each time the device sends data, the parser will be executed automatically,
-   extracting the measured variables and sending them to the bucket.
+   extracting the measured variables and sending them to the device.
 3. The extracted data is then available in widgets, dashboards, and can be
    processed further.
 

docs/tagoio/tutorials/beagle-bone-black.md

@@ -24,7 +24,7 @@ The circuit is straightforward: a single digital input is connected to a normall
 1. In the left sidebar, open **Dashboards** and click the plus icon (`+`).
 2. Name the dashboard (e.g., `BBB Dashboard`) and click **Save**.
 3. Add a widget: click the top‑right plus icon, choose **Display**, and configure it to show the variable `switch`.
-4. Select your bucket (`dev01`), device (`dev01`), and click **Select as new option** then **Save**.
+4. Select your device (`dev01`) and click **Select as new option** then **Save**.
 5. The widget will update in real time once data starts flowing from the BBB.
 
 ### Sending e‑mail Action

docs/tagoio/tutorials/mqtt-with-sensor-tag.md

@@ -70,13 +70,13 @@ The tested SensorTag hardware contains the following 10 sensors:
    - **Subscribe Topic:** leave as is (not used)
    - **Publish rate:** `5000` (you may adjust later)
 6. Turn the switch on to start pushing data to TagoIO.
-7. If the configuration is correct and you have a network connection, sensor data will begin arriving in your account. You can view it in the Live Inspector tab of the device details. Note that this data is not yet stored in a bucket; you need to create an MQTT Action to save it.
+7. If the configuration is correct and you have a network connection, sensor data will begin arriving in your account. You can view it in the Live Inspector tab of the device details. Note that this data is not yet stored in your device; you need to create an MQTT Action to save it.
 
 ### Creating an MQTT Action to save data
 
 1. Go to **Actions** and click **Create new**.
 2. Set the trigger type to **MQTT Topic**.
-3. Choose the action type **Insert data to device bucket**.
+3. Choose the action type **Insert data to device**.
 4. Select your SensorTag device, set the topic to `data`, and save the action.
 
-Once the action is in place, all incoming MQTT messages on the `data` topic will be stored in the device’s bucket for further analysis or visualization.
+Once the action is in place, all incoming MQTT messages on the `data` topic will be stored in the device for further analysis or visualization.

docs/tagoio/tutorials/queclink-gps.md

@@ -36,7 +36,7 @@ Add a device in your account at TagoIO. Go to [Devices](https://admin.tago.io/de
 - GV55\*
   _contact us for updates_
 
-Once the device is created, you will receive a confirmation. Turn your GPS on and wait for data to arrive in your bucket: [Buckets](/docs/tagoio/devices/). The data will be ready to display in dashboards.
+Once the device is created, you will receive a confirmation. Turn your GPS on and wait for data to arrive in your device: [Devices](/docs/tagoio/devices/). The data will be ready to display in dashboards.
 
 ### Building Dashboards
 

docs/tagoio/tutorials/radiobridge-devices.md

@@ -56,8 +56,8 @@ building your own application.\
 When completed, click on **Create Device**.
 
 Turn your Radio Bridge device on, and wait for the data to arrive in your
-bucket. Every time the device sends data it will be available in the bucket and
-shown in the dashboard: [bucket](/docs/tagoio/devices/).\
+device. Every time the device sends data it will be available in the device and
+shown in the dashboard: [device](/docs/tagoio/devices/).\
 You can start editing the installed dashboard.
 
 Also, you can create

docs/tagoio/tutorials/sensit-with-sigfox.md

@@ -47,12 +47,12 @@ TagoIO — Select the device type (use the network filter to find Sigfox devices
 
 After adding the device, click on the newly created dashboard in the left menu
 and associate it with your Sens'it device. Turn the device on; data will arrive
-automatically into the bucket and be displayed in widgets.
+automatically into the device and be displayed in widgets.
 
-## Data Buckets
+## Device Data
 
 Every time the device sends data, the parser is executed, the extracted data is
-sent to a bucket, and it becomes ready for display in dashboards or further
+sent to the device, and it becomes ready for display in dashboards or further
 analysis.
 
 ## Custom Parsing (v2)

docs/tagoio/tutorials/thinxtra-xkit-for-sigfox.md

@@ -69,9 +69,9 @@ device that you just added.
 > Check with your Xkit distributor about how to register the Xkit in the Sigfox
 > Portal.
 
-Now, just turn your Xkit board on, and wait for the data to hit your data
-bucket. Every time the Xkit sends data, an action will be triggered and the
-script will parse the data sending it to the bucket, ready to be displayed by
+Now, just turn your Xkit board on, and wait for the data to hit your
+device. Every time the Xkit sends data, an action will be triggered and the
+script will parse the data sending it to the device, ready to be displayed by
 the widgets.
 
 You can start editing your dashboard as needed.

docs/tagoio/tutorials/touchtag-lorawan-everynet.md

@@ -32,7 +32,7 @@ To add your TouchTAG device to TagoIO:
 - When configuring devices, ensure you select the correct connector ("LoRaWAN Everynet") and the correct device type ("TouchTag") so the parsing rules are applied.
 - After creating your device, generate an **Authorization** for it (one per application).
   [Generate Authorization](/docs/tagoio/integrations/general/authorization.md)
-- Turn your TouchTAG device on and wait for data to arrive. Each time the device sends data, the parser is executed, extracted data is sent to the bucket, and it becomes available in dashboards.
+- Turn your TouchTAG device on and wait for data to arrive. Each time the device sends data, the parser is executed, extracted data is sent to the device, and it becomes available in dashboards.
 - You can create **notifications** and more advanced **scripts** as needed.
 
 ![TouchTag Dashboard](/docs_imagem/tagoio/TouchTag_Dashboard_Tago-0VU.png)

docs/tagoio/widgets/input-widgets/keypad-widget/creating-keypad-widgets.md

@@ -58,7 +58,7 @@ Notes:
 - **data**: This field should contain an array of variables used in the keypad widget. By default, the widget only uses the first variable, so this array should typically contain a single object.
 - **display.buttons**: This field is required and defines all custom buttons inside the keypad widget. Each button’s position corresponds to its index in the array (0‑based). For example, the image below shows how each index maps to a physical key on the keypad:
   ![Image 1](/docs_imagem/tagoio/1571244512451-CBw.png)
-- **display.bypass_bucket**: If set to `true`, the data sent by this widget will never reach the bucket. It will still be available inside the analysis scope.
+- **display.bypass_bucket**: If set to `true`, the data sent by this widget will never be stored in the device. It will still be available inside the analysis scope.
 - **display.click_color**: The color shown for each digit when a user clicks on it. Accepts any browser‑recognizable color format (name, hex, rgb, hsl, etc.).
 - **display.help**: Usual help text for the widget.
 - **display.main_color**: Main color for the digits inside of the keypad.

docs/tagoio/widgets/input-widgets/keypad-widget/keypad-data-manipulation.md

@@ -51,7 +51,7 @@ When you select an analysis, the scope that you will receive contains a JSON arr
 ```json
 [
   {
-    "bucket": "5da07e1269c7ae001b2faefe",
+    "device": "5da07e1269c7ae001b2faefe",
     "origin": "5da07e1269c7ae001b2faeff",
     "id": "5da07e1269c7ae001b2faefs",
     "variable": "my_variable",
@@ -88,7 +88,7 @@ If you select this option, the data sent by the widget will have an additional o
 
 ```json
 {
-  "bucket": "5da07e1269c7ae001b2faefe",
+  "device": "5da07e1269c7ae001b2faefe",
   "origin": "5da07e1269c7ae001b2faeff",
   "id": "5da07e1269c7ae001b2faefs",
   "variable": "run_user",