Salesforce, Inc. (CRM) Earnings Call Transcript & Summary

October 1, 2025

US Information Technology Software Special Calls 47 min

Earnings Call Speaker Segments

Emmanuel Schweitzer

Executives
#1

Good morning, everyone. This is Emmanuel. I'm your host today. Welcome to the session Trusted Services, getting your data protection strategy in motion. My name is Emmanuel Schweitzer. Yes, I'll introduce myself a little more properly in the jiffy. But I'm excited to walk you through our Trusted Services deck today and see all the services that are available in that part of the Salesforce portfolio just for having 10,000 [indiscernible] view what's available, and we'll focus on everything that's related to data protection. All right. About myself, Emmanuel Schweitzer. I have the privilege of being Australia and French and German. It's probably a lot a distinguished engineer solution engineer with public sector. I'm based in Brisbane, it's actually sending today. I've been with Salesforce for a little more than 6 years going to 7. I've been in Australia for almost 9 years, and European citizen at heart as well. Among my passions are photography and traveling the world to get just a perfect chart. So going from Svalbard all the way very close to an [indiscernible] down to South Africa and anything in between I am also proud over of a son of 9 and a proud husband [indiscernible] Valerie. And yes, always happy to have a chat about any topics professional or personal if we share interest. Thank you for attending. I really appreciate your time. We're all very busy, and I think there's a lot of competition for our attention. So I appreciate your interest in Trusted Services. And as a bit of introduction of the Zoom system, if you don't know it. [Operator Instructions] I will not be able to see the Q chat while I present, but there will be a time towards the end of our presentation when we will gather and go through any questions you may have. And hopefully, I can answer most of these as we go, but I may need to take a few notice, and I'll make sure to note down your details and I'll get back to you as soon as possible. All right. Our general topic today is going to be around how you can protect your data and constitute directions they need strong data covenants. Data used in the public sector without governance would mean data flowing in and out of multiple systems and recoverable data in case of accidental loss or corruption. Of course, having older data, sometimes 10 years back, that is neither relevant or compliant, having different user permissions and access. So most organizations don't have a fully proper dialogue [indiscernible]. And so they would be in petrodaxis issues with lack of compliance, I think of visibility around outputs. Customers are interested in data flowing in and out of systems that you forget about or isn't harmonized and so on and so forth. So it's all about organizing data with government strategy and protecting the data, relevant data for the end user, archive when not in use because sometimes you need to keep it for legal purposes. Obviously, protect it for compliance so that the wrong people don't access it and obviously backed up for any plan B. There could be accidental loss of data. There could be malicious loss of data as well. So it's something that we need to cater to. So trusted data is key for any public sector program. And as we delegate routine task to agents or third parties, it allows people to lead into more high-risk eye judgment decision areas when governance is really important, trusted data must take canter stage when there's so much leeway. And good trusted data is key to the outputs we seek. So it's really important to get that try, something personalized, something relevant, something compliant, and ensuring they are speedy transactions so that we get our customers where we need them faster than before. We'll be able to reduce the work [indiscernible] risk affairs as well. right. Right. So if you have Salesforce customers, you understand that the SaaS shared responsibility model is key and understanding that is key. So everything is built a foundation of trust. And there's a big part of responsibly utilizes with Salesforce. It's all about building our innovative secure solutions and having the infrastructure to support that. is also preparing customers who are loving threats and offering the tooling to deal with that. It's delivering reliable access to data and systems. Now there is a bit where you are responsible as well to implementing the control specific to our business. And this is why we offer so many tools to deal with role-based access control and sharing rates and things like that. You want to control the outcome, assuming excess usage and performance. You need to check better people that log in on to your system or actually the people that pretend to be, and there's nothing fishy about it. And of course, you need to ensure data integrated resilience. You don't want data to be tampered with. You want the consumer data to remain safe and be able to cope with the unpredictable. So this is where Trusted Services come into play. So our Trusted Services range provides trusted data security, compliance, resilience for your Salesforce data. It helps you minimize risk, address ever-changing regulatory requirements, and it hopefully helps avoid permanent data loss. And we've acquired what used to be a third-party own -- they've own company. and they're now part of our Salesforce portfolio. So we've deepened our existing products and provide our customers with native solutions that enable trusted data for trusted relationships with [indiscernible]. So if you want to ensure that you may get pretty data, Shield allows you to keep always on pulse of user activity, having obviously encryption going on. Security center part of the portfolio will have full visibility across multiple orgs for permissions, access, data classification, or if you wanted to ensure that you're handling your data across many sales force sandbox of production orgs, deal with regulations in your region or specific business area, Private Center, Data Mask and Seed will help you throughout the compliance journey. Finally, if you want to make sure that your sensitive data has a proper backup and archiving protocols, then obviously backup and recover Salesforce Archive will help you feel improve your data. And this is really the area where we're going to focus today. All right. Just to give you an overall idea of the key areas we'll focus on today. I kind of laid out the different layers of the Salesforce architecture, we have a shared responsibility model. and comes through to live with our data security compliance and resilience functionality. There's built-in controls confer with profile settings, all arches record level data classification levels, that's your bread and butter, I'm sure, as you use the Salesforce platform. At the same time, we have to consider how to enhance those controls by knowing Windows and sees what when, where and how. And we may look into creating policies for data retention, data masking transaction security and more with those add-on products. So among all those add-ons, we're going to focus on the ones that are highlighted in orange here. which is Database Mask & Seed, Backup & Recover, Archive and Discover. Discover is probably a hidden gem. And I certainly wouldn't want to finish the website. Today, we've having a few words about it. So moving on to the strong governance foundation for your program. Again, we'll have a particularly look at well of a function in shield, which is Data Detect, which I think is really important to send guard your data and that of constituents. Data Mask & Seed as part of the compliance and then data resilience, we'll have a look at a full [indiscernible]. All right. Let's start with Data Detect. So it's all about finding, addressing them and classifying sensitive data. with Data Detect, customers can quickly find a sensitive information in the Salesforce instance that might not, we might not even know exist. So it's typically the data that gets captured by people in the field, typically long text fields where it's not supposed to especially PII. So customers are able to define policies. You'd be able to do that. related to which type of information you consider sensitive. Let's think about Medicare numbers, credit details, but that idea to put that in long text. And you'd be able to scan or for data and identify where that might be stored and eventually act upon that. So if you don't know what data you have and you don't know how you feel about the data, then you don't know how you can protect it. So it's really about getting that clarity and being able to address that. So all about this cap GA. We've added matching-based scans as a part at the deployment. And obviously pilot successful, bison everyone's feedback that will eventually go to general availability as well. So I think that's a part of the [indiscernible] what used to be the Shield portfolio with an functionality that makes sense. So on the data compliance side, again, we're not going through sandboxes and privacy center, it could be a walls web similar on the topic. But I want to talk mostly about that Data Mask & Seed. But for general purpose information, if you don't know those areas, data privacy, it's really important for good data governance and the strategy that's associated to that. So it's critical for the business, maintaining customer trust and comply with regulations. And we have a few. we have more regulation coming up in Australia around protection of customer data. And Being able to address it in a request, they would make around it. So some questions you can ask yourself and your team as, are you currently protective sensitive data? Have you automated compliance yet? Are you capturing customer preferences or managing their consent to keep the data? yes, that's certainly a part of a portfolio that would help. So let's have a look at Data Mask & Seed as a first cap in the rank for that topic. Data Mask & Seed is design to help you accelerate development with realistic secure test data. So obviously, you can choose to have your production data automatically copy it into sandbox falling partially. But obviously, with that comes the challenge of having PII in important databases in an environment where typically, people have extended access rights compared to what we have in production. Typically, the setup, there's only a handful of admins would have added rights on prompt but a lot more people are able to see a lot more data in those intermediate environments. And sometimes, you may not want them to have a peek at some of those data points. So it's all about processing sandboxes quickly, allowing our development team to get started. But what we want to do is to synthesize or anonymize data that's reasonably real and close to the original one, but it's not the real thing. So it's the best of both worlds, if you wanted, or like a Goldilocks movement on the data. It is relevant to the task at hand, which is developing functionality and making sure your user stories are right, but it doesn't compromise the trust imperative that you have with your customers' data. So you'd be able to simplify compliance with any regulation, including upcoming Australian regulation on data privacy. And it's all clicks and not code. We offer built in masking the [indiscernible] and sort of algorithms. You can strip files, you can replace with random characters as stated in the screenshot on the right, replaced with a pattern, you can have a library and so on and so forth. So a lot of that is [indiscernible] at the moment, and we're still working on improving the toolkit. It's also much more rapid than it used to be in the past, and we are achieving north of 3 million records being anonymized or tended to per hour on average. All right. So now the next topic is data resilience, and that's really the big bit we'll be addressing today. So that's back up and recover from capability standpoint, that's archive, and that's Discover. It's all about being able to quickly and easily navigate data disruptions while ensuring innovations doesn't look slower. So you have achieved that our resilience. You are able to restore data from loss of encryption. And usually, they're accidental, but they could certainly be malicious if someone gained unlawful access to the org or if a discount contractor or employee decided to wreak havoc for some reason. So you'd be able to automate the process of having that dealing data, you don't longer need as well and quickly access high fidelity data from the backup and archive. So backup and recovery is obviously backing up and recovering to protect against that a loss of corruption. So it's highly secure, it's easy to tap. It's always available, and it ensures that adversities simplifies compliance. So we'll have a bit of a demo so that you can get a feel of how it works, provides automated backups at points in time. There was also an option to have a much more frequent backup of things that change as they happen. And everything that is important data, including metadata. Metadata in the configuration of your particular. Salesforce instance and how we define that it's working. That's very important as well. All the files that are attached to different records. And you would get proactive notifications of potential data also corruption. We'll see that in quite [indiscernible]. And -- but would [indiscernible] with easy-to-use recovery tools. And look, people usually what we mentioned backup. They are in that mindset that you do backup and then you restore all the dial-in and backup. And hence, you lose everything that changed ever since without recovery functionality, it's slightly different. You can be very surgical about the data you recover, keeping the data as it is current and just reverting some data points to a previous state. Data has been lost or that event has been tempered with or data that's been modified by mistake could be restored, and it could be a very narrow band top of action new performance. All right. So you'd be able to ensure accessibility of data with a home backups that are completely secure, compliant, readily accessible, those backups can be accessed at any time. [indiscernible] a status of pure cloud application and the data is stored on Amazon S3. So there's a possibility to access that separately. We will cover all the information that's important to you to ensure continuity, so I'm into data that have your choice. You don't need to back up everything if you don't need to but you can also include metadata. You can also protect your sandboxes. You manage package data and so on and so forth. So it's very comprehensive. We give you the ability to achieve any RPO requirement. RPO stands for a recovery point objective. The RPO means half our back, will the data be if I do store. And obviously, a shorter, smaller delta distance to that day, the better off. It means that you have more recent data. As I stated, you'll have the option to have something that is almost continuous data protection. But obviously, you can do daily backup, some weekly backups and so on and so forth, and things on demand as well. And your backups are obviously secured and stored in compliance. Because their stores in Australia, there is encryption going on and so on and so forth. So it ticks all the right boxes there. When it comes to restoration, which is, well, you back up, but actually that's a tablet issue, and that gets stilled or modified by mistake, and you need to restore it to its previous state. The restoration capabilities are critical. You need to be fast. You need to be comprehensive, and you will need the [indiscernible] when you will get back to business. So it's really important that the recovery time objective. You know how quickly you can get back to work is the shortest possible. So you will be able to recover the rig data quickly. As I mentioned, you can be quite surgical about it. Here, if you see on the screen shot, you see the comparison between what's currently in your Salesforce Oregon what's in a given back up, and you'll be able to see what's been deleted, what's been modified and so on and so forth. You'll get that comprehension. And hence, you'll be able to select exactly what you want to restore. On top of that, because you don't know what you don't know. How do you know you need to restore if you're not cognizant, but something bad happened. And this is when we're functionally of smart alerts, makes quite a difference. You'd be able to set up a smart alert and get notified about unusual data movement, a loss or change directly to your e-mail and have a double click on it that see if it really meant some actions. And that's all based on your roles or it can be based on statistical analysis and see if movement is a bit of an outlier like so many more records that have been deleted than on the usual day. So you have visual graph, tables and the precision repair tool that we see here on the screen that helps you get a good hang of what needs to be done and just do that. So we can extend the use of your backup. So backups are an exact copy of your production data, and they have value that goes beyond just the ability to recover and restore that. You have extended functionality that will empower you to leverage your backup to meet requirements for analytics, audits and compliance. So you'd be able to stay audit ready. We have searchable archive or historical data, you'll be able to look at any piece of data and act upon it. You can have visibility into what the data look like in the past for audit of reporting, you'd be able to also search historical data as well. So that comes on top of the function that you have in shared where you can see we modified when and maybe 4 of those items where you'd even Shield properly to track those changes. That could be a backup plan. We also have export capabilities, which would empower you to leverage the backup data to feed the analytic. Data stores of our analytic tools are creating a copy of your external warehouse for regulatory purposes, for example. So you can repurpose your backups without using initial Salesforce APIs when you do that. All right. The unified backup data. Management needs that you have 1 pane of glass to manage all your backup and recovery needs. So if you have a single org, obviously, you'd be able to see production data as well as your Sandbox data if you wanted to back up a sandbox data and recover potentially. You'd be able to see you made a data, the real bonus is when you have multiple organs and I know among the audience, some of you have multiple orgs. You can have a dedicated admin team that handles all the backup who restore and it can be in a single pane of glass that admin console for backup and recovery would be connected to all your orgs, prod or nonprod and you'd be able to act upon that from that single pane of glass. So you'd be able to consolidate that. You'll be able to share backup space, compliance management and our policies. So that's 1 console. And obviously, it worked with Salesforce. We have also functionality to enable you to back up data from other SaaS offerings as well. And in the same single console, you can also execute data static request. So that goes with a privacy center type of your functionality to make sure that you're fully compliant with your backup data with a regulation and address a to be forgotten in the backup data as well, if required. On the data itself, as I'd mentioned, you can have multiple policies, you can customize the backup timing, the frequency, the retention, can go all the way up to 99 years. And so you can have monthly backups, weekly backup, daily backups. And as stated earlier, you could have also as you go top up backups as well. All right. So let's talk about how we're different from what's out there in the market as well. I mean they are complementary offers from third parties. So yes, we're able to back up and restore. We even protecting everything that's important in your org to ensure that it's truly resilient, and we protect on data, but the metadata attachments files, sandboxes, sandboxes data, managed package data, et cetera. And you can run backups as frequently as needed, including manually to meet your RPO goals. And you can have a [ 24 ] basic full org RPO, but you can have on-demand backups at more frequent intervals. And as we stated, we have a continuous data protection add-on that would enable you for [indiscernible] data shape that's a really sensitive and highly transactional would enable you to back up your changes just has happened. So you would have an extremely short RPO in that case. All right. On the archive side -- so archive is a bit of a different topic is how do you offload data from your org to lighten the load on and data storage and the old and lighten the cost as well. and the ID when you archive -- well, it's data that's not relevant anymore for operational purposes. So you can define policies whereby you look at certain data points, and then you decide if you want to keep it in the second or storage for compliance or legal reasons or if you want to simply prune it. So those are typically the 2 options that you have. So it's all about calling inactive data, reducing costs as well, improving performance in new org, obviously, being compliant with records acts and things like that. So you can quickly objects taking up too much space. It will give you a bit of stats. You know what's eating space, and you can automate archiving based on policies, which would be on the Europe [indiscernible] criteria, and that eliminates the manual errors if you do archive manually many on and things like that. So it [indiscernible]. You yet retain secure access to your archive data, not necessarily for everyone in your org, but those power user special people that need to look into that historical data that gets for compliance and legal reasons. Not everyone has to see that or should be able to see that. And that doesn't impact compliance. That doesn't impact performance. It's data that's not going to be used for operational purposes in the org. So if you need a record that was archived months ago, it's not a problem. You can have a look at it. And if you really needed to, and it was [indiscernible], but archive in there you could restore it. We have a few clicks, if you really had to. All right. I mentioned Salesforce Discover being a bit of a hidden gem. It really does. Customers can turn that backups into a strategic asset. So you can see the data, but you have to backup as a time series of your data points. It could be extremely powerful from an analytics standpoint. You can ultimately generate -- will stand series data with a few clicks. [Audio Gap] Are you limit, the manual effort people usually go through using ETL or negative tools, and now you can have a peek at historical data and how it changed over time. You can have a look at the data at any point in time. You can see -- you can rapidly prototype and see how it evolved or what's the trend. And if you didn't plan to include a specific object, you can just pull it from your backups by configuration, connected to, let's say, Data Cloud or any data warehouse of your choice and move forward as if you had always plan to do it without any delay. So it's really moving data around to get to the our community. All right. So I think that's enough we're at this stage. And what I suggest for you now is to have a bit of a demo, very simplified demo a bit of a demo of what backup and recover enables. Another reminder, feel free to ask away using the chat QA button, and we'll address that towards the end of the webinar and hopefully come up with questions -- responses to your questions straight away. All right. So let's have a look at the demo. This on the screen is the pane of glass that you would have on your backup and recover admin app. So not everyone, not every admin on your own need to have access to that. So you can select the people who would be able to. And here, you can see that it's all about protecting your data against loss and corruption. You have backup data separate for different orgs and different data types, both production and Sandbox, both data and metadata as well as high frequency, which is a continuous data protection, I might mentioned. So if I flip next, you see that it's all multi-org. As I stated, you can have a bird's eye view on everything that's available, and you'd be able to see where it's at, what was the latest backup date if it's been completed, what it pertains to, what org it's about what's the type of data. You would be able to see full backups as well as other types of backups as well. All right. I mentioned the proactive alerting. This is how it would look like once you configure it. So it's all a matter of configuration of defining what objects it pertains to and what is exactly that you're trying to capture or it can be kind of automated and look at statistical outliers in terms of data movement, and it would give you a bit of word of what happens. So here, the admin would receive a daily summary of what happened in, on the production data of a certain Salesforce org. 816 records were deleted. And that's a bit of a outlier. So it looks like a lot more records have been deleted then on an unusual day. on opportunities, it's even worse. It's like 13,000, quite a few. So your data is your biggest asset. You need to know what's going on. So obviously, you could have reports. You can have dashboards and so on and so forth, but this is really precious for the busy admin. It's proactively letting them know that something is not -- potentially not quite right. So you'd be able to then go back to the backup and recover app and have a bit of an analysis of what happens. So here, you see different objects. You see what's been removed, how much data are we looking at how many of those records have changed, how many have been added and how many calls -- API calls have been involved. So you'd be able to see exactly what went on compared to the previous backup because we're looking at incremental changes here. So it gives you kind of a full picture. And then you can kick off a restored job of a single play. Okay. So this is how the restore configuration screen would look like. You'd be able to select the object, level depth. Obviously, where you've restored from and then you'd be able to select exactly the nature of our costs that are going to be restored. So it can be either broad or you can be quite surgical in what you do. And we obviously restore integrated by maintaining relationship between record. So you'll be able to restore like a graph of data records that are related to each other. It really minimizes the risk of thing incomplete and inconsistent data by doing that. All right. You'd be able to compare backups as well. So you'd have a comparison of what's changed between backups and you see if it requires certain attention, you'd be able to preserve value changes while correcting the core data because it's been modified, likely here was 287 modified records would be part of a security need, right. Precision repair, it's all about inspecting those 297 records that have been modified, and being able to see what's going to go on. So you'd have a cold code like reds being deleted, yellow-ish, orange-ish, amber, whatever you want to call it, is in to be modified and green is going to be added data. So you have like a very visual way of seeing what's going on. And you'll be able to see the all value previous value and the new value as well and decide what you want to do about it. All right. And then the job is complete. It inserts the data back into your org and all the dependencies in the right order which really enables you to get to the quickest recovery time objective as possible. Here we go. So before we enter into the Q&A a bit off to that session, I wanted to share some of the road map items for functionality that we double clicked on. So again, this is our backup and recover, Data Mask & Seed and Discover. So for Winter '26, which is the upcoming version or release in Data Detect is going to be a native app that sits directly in your Salesforce org, not terribly relevant for Australia, but we'll have GovCloud support, data cloud yellow scaling as well. For archive, we'll have improved search to surface Archives more seamlessly, but backup and recover will have view only user roles. So people are able to see what's in the backup and what's the status or backup but they will not be able to change anything. And we will also support aCIM-based user management. For Data Mask & Seed, we'll see generated records in metadata across sandboxes. And for Discover, we'll have agents to curate backup data and we'll have Discover for Data Cloud as well. One version further. And again, all of this is a safe harbor. It's planned, but it might not turn out exactly as stated. So if you make any purchase decision, make it on functionality that's available today. But forward-looking to 2026. We have Shield Data Detect cloud yellow scanning and automated scheduled scans. On Archive, we'll have Archive fully on Salesforce. We've expanded agent force capabilities. For Backup & Recover, ,we will omit all the operations of backing up and recovering from APL limits at the moment. Full disclosure, it consumes the API calls in your org will have even improved scaling with full Kubernetes support for that Backup & Recovery app and all the engine that deals with Backup & Recovery. hyper force of cloud support enhancements. So it really supports Hyperforce, but it's going to run on IP. I think this is what it says. For Data Mask & Seed, we'll rebuild the masking app. So I think runs directly on app or force within UI. That's 1:1 with the rest of the Salesforce app and agentic seeding as well. Like you'll be able to ask an agent to seed using specific instructions for you. And on Discovery, you'll have advanced filters you'll be able to have a look at archived records. You'll be able to use formula fill values and be able to look into more data sources. All right. So I think we reached a point where we can go through the QA. So I'm going to go back to my presenters mode to check the QA if you want to bear with me.

Emmanuel Schweitzer

Executives
#2

All right. There's quite a few QAs. Regarding a session, yes, it will be shared. So definitely, that's going to happen. Another question is around how frequently backups can be scheduled? So we can be run on demand and you have daily, weekly, monthly, and you have also a choice of having continuous data protection. So all of the above good, sir. I have a question on unlimited storage. So what happens on Backup & Recover as well as Archive, you don't -- the metrics for the cost of the capability is not linked to the number of users. It's linked to the actual data shape that you need to back up. So we'll have a look at which data you use on uses of orgs as well as a much file storage you consume. And we -- you will need to contract based on those qualities, knowing that for fall attachment, there's a 1 to 10 ratio. So it's kind of 90% because files are typically cheaper storage category. So this is how this will be completed. And we always encourage customers to contract for a little more than their current use because data tends to grow. So typically, the guidance is shoot for about 30% more as you actually consume today so that you have a bit of buffer for the few months to come. I have a question around archive only solution. Yes, you, there -- those are 2 distinct offerings. You have backup and recover, which is backing the data up and storing that backup, keeping the data in the org, but having it as a backup and being able to restore it. And we have an alternative or complementary capability, which is just archiving, which where the goal is not to keep the die in production is really removed a data from production, either our card in secondary storage because you have a mandate, you need to keep it for legal and compliance reasons or you can also prune the data because it's no longer relevant. Another question on changing the cash policy, such as older day then from 90 days to 70 days and so on and so forth will the agave respond and move them back to primary stage. Don't hate me if I'm wrong, but no, I don't think it does. You would need -- if you reduce the archive, like you say, we are at 75 days going into archive and then we go to 90 days, then the data portion that is in week 75 and 90 days will not be restored automatically. You would need to restore it. annually. I'll never check that. But yes, this is what we have at the moment as far as I know. Can we restore backup at full level? Yes, you can. So you are able to be very surgical. So you can select the fields that are going to be restored as well. All right. Archive backup product. So we have think we answered that. It's a separate offering that everyone needs archiving, I suppose. I would say that everyone does need backup, but yes, archiving is separate. So you don't have to have both at the same time, but you can. Yes, it's separate. Backup automation only available and specific Salesforce licensing? Or is it available for everyone? No, you can have it on any Salesforce org. Own backup, so backup and recovery be deployed of cabo, also part of owner solution. Yes. So yes, as we stated backup and recover is distinct from [ cabo ]. Another question around rolling back to a point in time. So what happens is you can decide which backup you restore data from. So obviously, if you have data backups that let's say, are done daily, you would be able to choose which daily backup you restore from. If you're really insistent that you need any point in time, I would encourage you to look at our continuous data protection option because then it saves -- backup changes just as they happen, which means that you can absolutely define any point in time down to the second and aim to restore the data that was then current. Okay. We support a [indiscernible], for instance, on sales force, yes, we do. And can we compare that in backups point in time with production live data and between 2 data points? Yes, you can. So that's the goal. That's a bold premise. You can compare current dollar versus data in the backup and you can compare to backups with each other and then you can restore just as you'd like. All right. So those are all the questions I had. I'll leave it another seconds just to see if it's more coming. So how is the pricing? Would suggest that you contact your Salesforce account executive around the pricing. But as I stated, the metric is going to be based on the storage space that you use in your org at the moment plus a bit of buffer. So that's the metric. And then there is a price associated with how many gigabytes, let's say, you would need to use. Something I can share is that there's a minimum contract storage point, i.e., you can go below a certain storage space. So something to consider. Usually, it's worthwhile sharing storage across multiple ors if they tend to be on the smaller side, if you can. All right. Thank you so much for all those questions. I think we covered a lot of ground. So let me, at this stage, thank you again for attending. If you feel that there's any question we didn't answer well enough or as a second thought, you think that it's something you'd like to run by us, feel free to reach out. We'll make sure you get all the data on that in to get full clarity and make informed decisions. I also wanted to share certain learning journeys if you wanted to know more on Trailhead. There are a couple of modules, and it could be useful if you wanted to explore a little more. There's a module called Get to know backup archive which I created shortcut for sfdc.co/th-backup-archive. And another one, which is make solutions secure and it's a little more generic. It's content that was initially designed for the education space, but it applies 100% to anyone in the public sector. and that's sfdc.co/th-make-solutions-secure. On the resources as a convenient QR code here. You can learn more about our entire Trusted Services portfolio. at SFDC CEO, Trusted Services 2025. So feel free to make a screen shot at this moment or to use your phone camera to open the link and get that very comprehensive write-up about Trusted Services. So at this stage, let me check if there are more questions that popped. No, there aren't. So I'd like to extend my thank you again for attending. Again, do reach out if you have on, in hindsight, more topics you'd like us to approach on. Any upward questions as well. And that being said, I can only wish you a grade day ahead and hope that you will make the best out of our Trusted Services to get your data protection strategy in motion. Thank you again. Buh-bye.

This call discussed

For developers and AI pipelines

Programmatic access to Salesforce, Inc. earnings transcripts and 32,000+ others is available through the EarningsCalls.dev REST API. Plans from $24.99/month — full transcripts, speaker segments, full-text search, and the recently-added /api/v1/transcripts/recent polling endpoint for ETL pipelines.